Thank you very much for this information!
I guess many of us are very happy about any information and may desire more of this frequent updates about major development steps. Especially if set dates will be delayed.
One additional question about the new design: As accessibility gets more and more important in Europe, do you consider this while designing the new UI?
So should we postpone any development on frappe UI based apps if it will have breaking changes in version 16?
This is excellent news. Itās already possible to create some pretty amazing custom interactivity by hooking into HTML fields, dashboards, and blocks, but it sometimes gets a bit messy.
Having a single design language that can work across the desk, standalone applications, pages, portals, etc. would boost power and minimize complexity at the same time.
Iād be very happy to be corrected if Iām wrong about this, but I wouldnāt think that Frappe UIās integration into the framework would have any impact on standalone applications. Those have an entirely separate build step and could continue compiling against arbitrary versions of the library.
What does seem likely to happen, though, is that many things currently being built as standalone applications would suddenly become much easier to make in Desk directly.
That is a great news. All apps must have the same design language.
This is very important and a great decision.
@mohamed-ameer with the new UI capabilities and integration possibilities we will have a lot of new areas to cover in your tutorials 
With the very high bar set, the doc will thus be amazing.
First step probably being to be and stay in sync with any new code, lest the doc-linter refuses to merge.
like literally
Hi, different from what is seen in the develop branch?
100%! Iāve been closely watching the client-rework branch and experimenting with it. Iām new here, but experienced in the field, and I canāt see myself using javascript and jquery to customize the framework (let alone simple client scripts) 
So canāt wait for the typescript + vue rewrite!
Not sure what would that mean for Frappe desk Page that have been build using lots of extra js libraries and css components? What would the impact be there? Need to redo everything using Vue? At the moment frappe-ui and Vue were not part of the frappe desk at all. Is that what is changing?
Vue calls itself an āincrementalā framework. You can add it to an existing page, give it control of only a tiny part, and leave everything else about the page working exactly the way it was before. It is designed from the start to play nicely with other libraries.
I have no idea whatās planned for future versions of Frappe beyond whatās been shared, but I canāt think of any technical reason for the addition of Vue/Frappe-UI to break anything thatās already existing without them.
Does the addition of Vue/Frappe-UI means the removal of dependency on Bootstrap 4? Do you know if is it getting removed, bumped to Bootstrap 5 or will remain untouched?
AmƩn to that
Thanks @peterg ā¦ I refrained from learning Vue so far and install the whole frappe-ui libraries and dependcies. It seems like I would need to go that road. I hope it would be all now natively installed in Frappe.
I was just talking about the warranty that comes with Frappe Cloud. I believe itās the $50/month plan, actually. That may have changed, or I may have just misspoken before. Either way, Iāve used it and can say itās a great deal.
I canāt think of any reason that you would need to use Vue or Frappe-UI, but I definitely recommend it. Vueās declarative binding is ideal for the kinds of things we would usually want to do in an ERP, and it just makes coding interactive reports/dashboards/etc so, so, so much simpler.
That said, pretty much everything Vue does is opt-in. If youād prefer to keep using vanilla javascript and roll your own widgets, I really canāt imagine why that would stop being possible.
Which python version is V16 on? 3.13 or?
Kindly consider this feature too. I already raised the issue on GitHub.