Flutter 3.47 went stable on 12 August 2026 alongside Dart 3.13, and the change worth flagging for anyone who owns a cross-platform app rather than builds one is structural: Google has pulled the Material and Cupertino design libraries out of the core Flutter SDK and turned them into standalone packages, material_ui and cupertino_ui. An automated migration tool rewrites existing imports and updates pubspec.yaml accordingly, and old bundled imports keep working for now, with formal deprecation expected around November 2026 and removal in 2027.
Why decoupling the UI layer matters
Previously, a bug fix or new component in Flutter’s Android- or iOS-style widgets meant waiting for a full Flutter SDK release, tested and shipped on Google’s schedule. As standalone packages, Material and Cupertino can now ship fixes and new components independently — the plan is weekly releases — without forcing an app through a full SDK upgrade cycle. For a business running a Flutter app, that means UI bugs and platform-look updates can land faster and with a smaller blast radius, instead of being bundled into infrequent, higher-risk SDK bumps. It also lays groundwork for style-neutral custom design systems built on Flutter’s core widgets, without inheriting Google’s opinions about what a button should look like.
So what
This isn’t a reason to rebuild anything — old imports still work today. But if you’re maintaining a Flutter app, it’s worth asking your development team whether the migration to material_ui/cupertino_ui is on the roadmap before the November 2026 deprecation lands, rather than left until the 2027 removal forces the issue. If you’re scoping a new cross-platform build and Flutter is on the shortlist, this kind of modularisation is a point in its favour — it signals a platform investing in faster, lower-risk iteration rather than big-bang releases. See our cross-platform work if you’re weighing Flutter against the alternatives for a new build.