☂️ Move the material and cupertino packages outside of Flutter #101479
Description
This issue tracks the work to formally decouple the material and cupertino libraries from the core Flutter framework and establish them as standalone, first-party packages on pub.dev.
➡️ 📄 Read more about our plan. ⬅️
This strategic transition will make Flutter's core lighter and more flexible, accelerate design library updates, and give developers more control over their app's dependencies.
The work will be managed through a deliberate, three-phased approach to ensure a stable and predictable migration for the entire ecosystem.
The sub-issues listed below track the specific tasks for each phase of this project.
📣 To provide feedback:
- Generally? Here.
- On critical refactoring of code out of material/cupertino before decoupling:
- On net-new additions of core components:
- On the new packages:
- On future deprecation and removal:
OP
Use case
- Long update cycle
- To get the new version - you need to update the version of Flutter
- Random imports
- Components for other platforms are separate from Flutter (fluent, macos_ui, yaru, ...)
Proposal
Move material and cupertino packages from Flutter
It can be done along with this issue (#91605)
Update 04/18/25
Link to proposal by @MaherSafadii with examples.