In addition, the Flutter Material Cupertino libraries — the building blocks for platform-adaptive UI — have hit a significant milestone. On April 7th, the Flutter team froze all contributions to these libraries inside the main framework repository. This marks the first step in a planned transition to decouple them from the core framework and re-release them as independent packages — material_ui and cupertino_ui — on pub.dev.
As a result, For most Flutter developers, this change brings no immediate disruption. However, contributors and those deeply involved in library development will need to adapt to a new workflow. Below is everything you need to know about the transition, why it is happening, and what comes next.
Why the Flutter Material Cupertino Code Freeze?
However, the Flutter team decided to freeze contributions to the Material and Cupertino libraries as part of a broader effort to modularize the framework. By separating these libraries into standalone packages, the team aims to achieve three key goals:
- Improve maintainability – Smaller, focused packages are easier to update and test.
- Enable faster iterations – Independent releases allow more frequent updates without requiring full SDK releases.
- Reduce framework bloat – Developers can opt into only the UI components they actually need.
The freeze keeps the code in the main Flutter repository stable while the new packages take shape. This approach cuts the risk of discrepancies between old and new implementations, making migration smoother for everyone involved.
Flutter Material Cupertino and what Does This Mean for Flutter Developers?
For example, If you build Flutter apps with Material or Cupertino widgets today, nothing changes for now. Both libraries continue to work as usual until the new packages reach pub.dev. Once Flutter 3.44 hits stable, though, developers will need to migrate from the built-in libraries to the new material_ui and cupertino_ui packages.
Key Milestones in the Transition
- Code Freeze (April 7th) – No further changes to Material or Cupertino in
flutter/flutter. - Flutter 3.44 Stable Release – The new packages publish on pub.dev.
- Post-3.44 Deprecation – The old libraries receive a deprecated label in the next stable release.
- Eventual Removal – The original implementations disappear in a future Flutter version.
The Flutter team will publish detailed migration guides when the time comes, so the broader community can move over without friction.
Handling Open PRs and Issues
Meanwhile, If you have pending pull requests that touch the Material or Cupertino libraries, reviewers will not abandon them. They will keep providing feedback, and once the new packages go live, contributors will get clear instructions on how to port their changes to the flutter/packages repository.
Overall, For issue tracking, all Material and Cupertino-related bugs and feature requests stay in flutter/flutter for now. This follows the same centralized approach the team uses for other Flutter packages. Check the official Flutter breaking changes documentation for the latest guidance on upcoming deprecations.
The Road Ahead
With the freeze in place, the Flutter team’s next steps include:
- Porting the libraries – Moving the frozen code into the new
material_uiandcupertino_uipackages. - Setting up CI/CD – Making sure automated testing and deployment pipelines are ready before launch.
- Documentation updates – Giving developers clear guidance for switching to the new packages.
This effort builds on months of collaboration with the Flutter community, drawing contributions from both newcomers and experienced developers. The team has expressed gratitude for the support so far and encourages continued feedback as the project moves forward.
Final Thoughts
Decoupling these UI libraries from the core Flutter framework is a major step toward a more modular and flexible ecosystem. The immediate impact on most developers is minimal, but staying informed will help you transition smoothly when the new packages go live.
For broader context on Flutter’s evolving ecosystem, visit Metaelement for more developer insights and guides.
The Flutter team welcomes community involvement — whether through bug reports, feature suggestions, or direct contributions to the new packages. Watch official announcements for further updates.
