Well, yes and no 
The main concern is add-on breakages - replacing the three webviews with one is something we’ll definitely want to do at one point, but it’s going to break a lot of add-ons. Updating the deck list and reviewer screens separately would be logical steps towards that goal, and if it’s done by creating a new code path that can be opted into with a feature flag, then it could be started right now. I’d prefer not to remove/replace the existing code at the moment however - I want to get the import/export changes done first so that the libanki refactor can be declared done, and I think we need to give some time for all the recent churn to settle a bit.
2 Likes