coingaming
V2？
We are still working on it. But in all honesty future proofing to account for new Material Expressive and what can be gleaned from leaks about the new iOS design system has created a bit of a moving target for us, especially with AI generative UI concerns thrown into the mix. So the original deadline has shifted somewhat. We really hope to release v2 by the end of Q2 but there's also a chance it will happen early Q3.
got it. those are valid concerns, good call. look forward to trying it (testing if you want/need)
how's progress? does decoupling Material & Cupertino from the core framework help or is it going to delay the release? https://www.reddit.com/r/FlutterDev/comments/1md1t9f/flutter_team_is_making_a_muchneeded_architectural/
We have settled on releasing end of Q3, as we have more or less locked down the core "Lego" blocks. While there's always more things we would like to add we also have to be aware that v2 has already gotten scope creeped quite a lot.
We have settled on releasing end of Q3, as we have more or less locked down the core "Lego" blocks. While there's always more things we would like to add we also have to be aware that v2 has already gotten scope creeped quite a lot.
Will it be easy to migrate from v1 to v2?
V2 is such a substantial change that it will be in its own mono-repo. You would be justified to ask why even call it moon_flutter then. The reasons for this are twofold. First and foremost we need to serve the needs of our own products as main priority. Secondly, in the design systems world it is not uncommon for a new major version to be wholly isolated separate project with its own separate design resources, tooling, styling/theming artifacts and their code representations due to burgeoning backwards compatibility concerns.
More simply one can view it like a product. V1 will remain as its own product with its own versioning and v2 will be a whole new product.