{
  "id": 21050251,
  "title": "Flutter 3.50 is out: Material and Cupertino are deprecated - here's the migration path",
  "url": "https://urgent.news/2026/11/21/flutter-3-50-is-out-material-and-cupertino-are-deprecated-heres-the",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-21T13:30:12.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/frpboy/flutter-350-is-out-material-and-cupertino-are-deprecated-heres-the-migration-path-43k6"
  },
  "original_language": "en",
  "account": "Flutter 3.50, released on November 11th, brings a significant structural change to the framework: the Material and Cupertino libraries are now formally deprecated. These libraries, previously bundled within the framework, will now exist in standalone packages named material_ui and cupertino_ui, versioned independently of Flutter. The move aims to simplify design library updates, allowing them to be shipped without waiting for a framework release, and give the framework team more flexibility in evolving without carrying deprecated libraries.\n\nTo facilitate the transition, a MaterialUiCompatibilityBridge is available for code that straddles both worlds during the migration. Dart fix, a tool, applies the majority of the changes required for the migration, making the process largely mechanical. The official migration guide, found on docs.flutter.dev, provides comprehensive instructions for the transition.\n\nIn addition to the Material/Cupertino deprecation, Flutter 3.50 introduces several enhancements. Native interop, or the ability to call native code on various platforms, has been consolidated in a new section of the documentation. This includes guides for Pigeon, package:ffigen (for C and Objective-C), package:jnigen (for Java and Kotlin), and build hooks for bundling native code.\n\nWeb development in Flutter continues to improve with new features. A --web-content-hash build flag has been added to add cache-busting hashes to web assets, improving cache control. The WebAssembly (Wasm) documentation now covers critical production concerns such as server headers, pre-compression, cold-start latency, CDN asset loading, and profiling Core Web Vitals in Chrome DevTools.\n\nFinally, the platform-integration docs have been updated to cover iOS 27, macOS 27, and Xcode 27. Expanded Swift Package Manager migration guidance for apps and plugins is now available, ensuring Apple platform readiness.\n\nBefore upgrading to Flutter 3.50, it is recommended to run your test suite, review the breaking changes listed, and assess your plugin stack. While the Material/Cupertino deprecation does not remove these libraries from your app, starting the migration early with the provided tools and documentation is less costly than attempting it during a time-sensitive deadline later.",
  "summary": "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…",
  "key_points": [
    "Flutter 3.50 released on November 11th deprecates Material and Cupertino libraries",
    "MaterialUiCompatibilityBridge aids transition for code straddling both worlds",
    "Dart fix tool applies majority of migration changes, official guide available"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}