Dev.to WebDev πŸ›  Dev πŸ‘ 0 πŸ“– 2 min read

Flutter 3.50 is out: Material and Cupertino are deprecated - here's the migration path

Flutter 3.50 shipped on 11 November with Dart 3.14. The headline change is not a widget or a performance graph - it is a structural one: the Material and Cupertino libraries bundled with the framework are now formally de

Flutter 3.50 shipped on 11 November with Dart 3.14. The headline change is not a widget or a performance graph - it is a structural one: the Material and Cupertino libraries bundled with the framework are now formally deprecated, and their future lives in standalone packages.

The Material/Cupertino split

Flutter's bundled material and cupertino libraries are deprecated in 3.50. The replacements are the standalone material_ui and cupertino_ui packages, versioned independently of the framework. That decoupling means design-library updates can ship without waiting for a framework release - and the framework team can evolve without carrying them.

The migration is meant to be mostly mechanical: dart fix applies the bulk of the changes, and a MaterialUiCompatibilityBridge exists for code that straddles both worlds during the transition. The official migration guide on docs.flutter.dev walks through it. If you maintain a package that depends on package:flutter/material.dart, expect your users to start asking about this soon.

What else is in the release

Native interop, finally consolidated. A new Native interop documentation section pulls together the guides for calling native code on every platform: Pigeon, package:ffigen for C and Objective-C, package:jnigen for Java and Kotlin, and build hooks for bundling native code. If you have ever hunted these across five different READMEs, this is welcome.

Web keeps maturing. A new --web-content-hash build flag adds cache-busting hashes to web assets, and the Wasm documentation now covers real production concerns: server headers, pre-compression, cold-start latency, CDN asset loading, and profiling Core Web Vitals in Chrome DevTools.

Apple platform readiness. The platform-integration docs now cover iOS 27, macOS 27 and Xcode 27, with expanded Swift Package Manager migration guidance for apps and plugins.

AI tooling docs. The AI section has been reorganized around a unified get-started guide, custom agents, and package:skills_lint.

Should you upgrade now?

As always with Flutter stable releases: run your test suite, read the breaking-changes page, and check your plugin stack first. The Material/Cupertino deprecation is not a removal - your app will keep building - but starting the migration early, while dart fix and the compatibility bridge are fresh and documented, is cheaper than doing it under deadline later.

Have you run dart fix against a real codebase yet? Curious how clean the migration actually is in practice.

Sources:

πŸ“° Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.