Flutter Streamlines UI Libraries: Material and Cupertino Decouple from Core Framework

Introduction: A New Chapter for Flutter's UI Libraries

Flutter's development team has announced a significant milestone in the evolution of its UI toolkits. As of April 7th, the Material and Cupertino libraries within the flutter/flutter repository have entered a code freeze. This marks the first major step toward decoupling these libraries from the core Flutter framework and transitioning them into independent packages on pub.dev. The new packages, tentatively named material_ui and cupertino_ui, will eventually house all future development of these design systems.

Flutter Streamlines UI Libraries: Material and Cupertino Decouple from Core Framework

What the Code Freeze Means for Developers

The freeze means that no further contributions or changes to the Material and Cupertino code inside flutter/flutter will be accepted. However, this change is designed to be transparent for most developers. If you build Flutter apps or plugins without directly contributing to the Material or Cupertino source code, your workflow remains unaffected – for now. The immediate impact is negligible; the libraries continue to function exactly as before.

Timeline and Future Migration

After the release of Flutter 3.44 stable, the new material_ui and cupertino_ui packages will be published on pub.dev. At that point, developers will eventually need to migrate their dependencies. Specifically, the old libraries will be deprecated in the stable release immediately following 3.44 and removed entirely a few releases later. The Flutter team has promised detailed migration guides when the time comes, so you need not worry about the transition today.

For Contributors: What You Need to Know

Active contributors to Material or Cupertino should be aware of a few important details to ensure minimal disruption.

Open Pull Requests (PRs)

Existing PRs that touch the frozen libraries will remain open. Reviewers will continue to provide feedback as usual. Once the new packages are released, instructions will be provided to help port these PRs to the flutter/packages repository. Ultimately, your changes will be included in a future release of material_ui or cupertino_ui.

Issues Reporting

Issues related to Material or Cupertino will continue to be tracked in the flutter/flutter issue tracker. This unified approach is consistent with how other packages in the flutter/packages repo are handled, so familiar workflows remain unchanged.

Why Freeze the Code Now?

The decision to freeze the code a full stable release cycle before the new packages ship is deliberate. The primary goal is to ensure a seamless migration for all Flutter developers, regardless of which release channel they are using (stable, beta, dev, or master). By freezing the code, the team can copy that exact state into the new packages, guaranteeing that the libraries in flutter/flutter and in flutter/packages are identical. This minimizes the risk of breaking changes during the migration window.

The First Step for Developers

When the migration period begins, the initial step for any Flutter developer will be to upgrade their SDK to version 3.44 or above. Once that upgrade is complete, they will have a stable, frozen copy of Material and Cupertino. Even if they later upgrade their SDK again, that frozen snapshot remains unchanged until they choose to adopt the new packages.

Conclusion: A Smooth Path Forward

This code freeze is a calculated move to decouple Flutter’s UI libraries from the core framework without causing disruption. While active contributors should watch for porting instructions, the vast majority of developers can continue building apps as usual. The unification of issue tracking and the careful rollout plan underscore Flutter’s commitment to a stable, developer-friendly ecosystem. Stay tuned for the 3.44 release and the subsequent announcement of material_ui and cupertino_ui.