Flutter 3.50 and Dart 3.14 came out on 11 November 2026. Release posts always read like everything changed. Most of it will not touch your app this week. A few things will, and one of them affects almost every Flutter project ever written: the Material and Cupertino libraries are now formally deprecated inside the framework.
We build and maintain Flutter apps for clients, including our own staff app for Nexvora Workspace, so we read these releases with one question in mind: what do we have to do, and what can wait? This is that list.
The big one: Material and Cupertino are now separate packages
For years every Flutter app started with an import of package:flutter/material.dart. That import still works in 3.50, but it is now deprecated, along with package:flutter/cupertino.dart and their delegates in flutter_localizations. The widgets live in two standalone packages, material_ui and cupertino_ui, which reached 1.0 back in Flutter 3.47. New projects made with flutter create already import material_ui.
Deprecated does not mean broken. Your app builds and runs today. But the warnings will pile up, new Material fixes ship in material_ui first, and sooner or later the old imports will go. Better to move while it is a planned task than when it is an emergency.
The Flutter team has done most of the work for you. Running “dart fix --apply --code=migrate_design_widgets” rewrites the imports. If it does not add the dependencies, run “flutter pub add material_ui” (and cupertino_ui if you use it), then run dart fix once more to tidy imports. For localizations, the delegate list becomes GlobalMaterialLocalizations.delegates, which also covers the Cupertino and Widgets delegates.
Things to watch while migrating:
- Third-party packages that still use the old imports. Wrapping the app with MaterialUiCompatibilityBridge in MaterialApp.builder keeps their Theme.of(context) and MaterialLocalizations.of(context) calls working.
- The bridge cannot fix type mismatches. If a package takes a ColorScheme or a similar type in its own API, that package has to be updated first.
- If you publish a package, switching it to material_ui is a breaking change for the people who use it. The migration guide says to treat it as a major version bump.
Flutter on the web: Wasm reaches Safari and Firefox
Building with “flutter build web --wasm” now runs as WebAssembly in Safari 26.2+ and Firefox 147+, not only Chrome, and falls back to JavaScript in older browsers. On heavy widget benchmarks the Flutter team reports more than twice the frame rate of the JavaScript build in those browsers. You choose which browsers get Wasm with wasmAllowList in web/flutter_bootstrap.js.
There is also a new --web-content-hash flag for release builds. It adds content hashes to file names and writes a precache_manifest.json, which makes caching after a new release far less fiddly. It replaces the old flutter_service_worker.js tokens, which are now deprecated.
Two smaller notes. The old JavaScript interop libraries (dart:html, dart:js, dart:js_util and package:js) are deprecated in favour of dart:js_interop and package:web; the --no-deprecated-js-interop flag shows you where you still use them. And a preview of native browser text layout shrinks the CanvasKit download from about 5.46 MB to about 3.75 MB, which helps first load on slower mobile connections.
Android: tighter defaults to check before release
Release builds now ignore the route, dart_entrypoint and cached_engine_id values when another app passes them in an Intent, and they reject engine flags such as --dart-flags at runtime. This closes a door that should not have been open. If your app relied on opening a specific route through Intent extras, test that path before you ship 3.50.
New projects default to AGP 9.3.1, Gradle 9.5.0, Kotlin Gradle Plugin 2.4.20 and Java 17, with compile and target SDK 36 and a minimum SDK of 24. The minimum AGP for builds is now 9.1.1. Plugins are expected to move to built-in Kotlin instead of applying the Kotlin Gradle plugin themselves.
If you embed native Android views, Hybrid Composition++ gets unbuffered touch dispatch. It needs Android 14 (API 34) or newer and Impeller on Vulkan, and you switch it on with flutter config --enable-hcpp.
iOS and macOS: lower touch latency and a CocoaPods deadline
Touches now reach your app a frame sooner: the Flutter team reports 16 ms faster on 60 Hz iPhones and 8 ms on 120 Hz ProMotion screens. You get this without changing any code, and it makes scrolling and dragging feel more direct.
The date to put in the calendar is December 2026, when the CocoaPods trunk becomes read-only. Swift Package Manager is the way forward, and turning it off now prints a warning on every Flutter command. If your iOS build still depends on pods, plan the move now rather than in the week a release is due.
Intel Mac users also get a warning. A future Flutter release will need Apple Silicon to build for iOS, macOS and Android, so if your build machine or CI runner is an Intel Mac, it is time to budget for a replacement.
Desktop and native code
Calling native code without a plugin layer is now stable on both sides: FFIgen for Objective-C and JNIgen for Java and Kotlin join FFIgen for C. Pigeon gets a native interop mode in preview. For business apps this matters when you need a vendor SDK for a printer, a scanner or a payment terminal and do not want to maintain a hand-written plugin for it.
On desktop the multi-window APIs keep maturing on Windows, macOS and Linux. Linux gains custom title bars and transparent windows, and macOS windows can size to their content before they appear. If you used the earlier API, note the renames: RegularWindow is now Window, and sizedToContent became shrinkWrap.
Dart 3.14: no new syntax, but a tool that does the upgrading
Dart 3.14 adds no new language features. That is fine, because 3.12 and 3.13 brought plenty: private named parameters in 3.12, and primary constructors in 3.13, which let you write a small class in one line, such as class Point(var int x, var int y);.
The headline is dart migrate. It moves a package forward one Dart version at a time. For each step it applies the fixes needed before the upgrade, raises the SDK lower bound in pubspec.yaml, and can then tidy the code to use the newer features. Start with “dart migrate --dry-run” to see what it would change, then “dart migrate --apply”. To jump several versions at once, add --target-sdk=3.14.0. It only works on packages that already require Dart 3.0 or later.
One behaviour change to know about: a fix to flow analysis means a subpattern in a list, map or record pattern no longer promotes the whole matched property to the subpattern’s type. Most code will not notice. If a pattern match that compiled before now shows a type error, this is the likely reason.
Other Dart 3.14 changes worth knowing:
- SIMD types such as Int32x4 and Float32x4 now use real 128-bit hardware instructions, with up to 4x speedups in the Dart team’s benchmarks.
- dart pub get, upgrade and add now cache version listings; on a project with 144 dependencies that saves about 1.5 MB of repeated downloads.
- A new DartPad in beta compiles and analyses code in the browser, supports several files and can use packages from pub.dev.
- The analysis server starts faster, and Find References is quicker in large workspaces.
How we would upgrade an existing app
Do it on a branch, in this order, and test after each step. Mixing all of it into one change makes it hard to see what broke.
A sensible order:
- Upgrade Flutter to 3.50, change nothing else, and run the app and its tests. Fix only what fails.
- Run dart migrate --dry-run, read the changes, then apply them.
- Move to material_ui and cupertino_ui with dart fix, and add MaterialUiCompatibilityBridge only if a dependency still needs it.
- Android: check the Gradle and AGP versions, and test any screen you open from an Intent or a notification.
- iOS: move from CocoaPods to Swift Package Manager before December.
- Web: try a Wasm build in Safari and Firefox, and add --web-content-hash to the release build.
Do you need to upgrade right now?
If your app is stable and you are not shipping this month, there is no rush to change it on day one. Wait for the first patch release, then upgrade in the order above. If you are starting a new app, start on 3.50 with material_ui from the first line.
If you have a Flutter app that needs this upgrade, or one that has fallen several versions behind, we can take it on as a fixed piece of work with a test build at the end. See our mobile app development service, or read how Flutter works for field teams and customer apps.
Sources
Flutter blog, “What’s new in Flutter 3.50” (11 November 2026); Flutter docs: What’s new, the 3.50.0 release notes, the breaking-changes index and the guide to migrating to the standalone material_ui and cupertino_ui packages; Dart blog, “Announcing Dart 3.14” (11 November 2026); dart.dev What’s new and Language evolution pages. Benchmark figures are the Flutter and Dart teams’ own; read the full release notes before you upgrade.
Next article
DeepSeek V4.1, Gemini 4 Argon and GPT-6.1 Sol: The October 2026 AI Update for Business →