Flutter 3.50 landed on November 11 alongside Dart 3.14, and it comes with one change that hits every Flutter project immediately: package:flutter/material.dart is deprecated. Beyond the headline, there’s a lot packed into this release — Skia is gone on Android, native interop reaches stable, WebAssembly performance doubles on Safari and Firefox, and iOS gets a full frame of latency back. This is one of the most consequential Flutter stable releases in a while. Here’s what actually changed and what you need to do about it.
material.dart Is Deprecated — Run This Command
The biggest change isn’t about performance or new widgets — it’s a structural shift in how Flutter ships its design libraries. package:flutter/material.dart and package:flutter/cupertino.dart are now officially deprecated, replaced by standalone packages: material_ui and cupertino_ui on pub.dev. New projects created with flutter create already use material_ui by default.
The migration is one command:
dart fix --apply --code=migrate_design_widgets
This handles the import swap automatically. If your pubspec.yaml needs it, run flutter pub add material_ui first. The import changes from package:flutter/material.dart to package:material_ui/material_ui.dart.
Important clarification: deprecated is not removed. The old packages still compile, they just emit warnings now. The breaking removal is coming in a future major version — you have time, but starting the migration now is the right call. If you maintain Flutter packages, the migration is harder: switching to the standalone packages is a breaking change for your users, which means a major version bump. Plan accordingly.
Skia Is Gone on Android 10+
Flutter 3.50 completes the multi-year Impeller migration. iOS got Impeller as the default renderer in Flutter 3.10 (May 2023). Android 10 and above now joins it — the legacy Skia backend is officially retired.
If you’ve been using --enable-impeller=false as a workaround for rendering issues, that escape hatch is gone on Android 10+. You’ll need to find and fix the root cause. The good news: Impeller’s pre-compiled shaders eliminate the runtime shader compilation jank that made first-run animations stutter — a problem Skia never solved well on Android’s diverse GPU landscape. For most apps, this is a net positive. For apps that relied on the flag, there’s work ahead.
Native Interop Is Stable — Platform Channels Are Now Optional
This doesn’t grab headlines the way a deprecation does, but it’s arguably the most significant architectural change in Flutter 3.50. FFIgen for Objective-C and JNIgen for Java and Kotlin are now stable alongside existing C support. Together, they let Dart call native platform APIs directly — without the serialization overhead, string-based routing, and mandatory async latency of traditional platform channels. The official announcement calls it the completion of Flutter’s native interop story.
The practical difference:
// Platform channel (old) — async, serialized, boilerplate
static const platform = MethodChannel('com.example/battery');
final int result = await platform.invokeMethod('getBatteryLevel');
// Direct JNI (new) — synchronous, no overhead
final batteryLevel = BatteryManager.getIntProperty(
BatteryManager.BATTERY_PROPERTY_CAPACITY
);
Direct interop can run synchronously and from background isolates. The shared_preferences plugin serves as the reference migration example. This closes a gap that made Flutter’s native story weaker than React Native’s New Architecture — platform channels were always a workaround. Now Dart has proper FFI bindings across all major native targets.
WebAssembly: 2x Faster on Safari and Firefox
Flutter web apps built with --wasm now run at over twice the frame rate of their JavaScript counterparts on heavy widget benchmarks in Safari 26.2+ and Firefox 147+. Chromium-based browsers have been running Wasm by default since Chrome/Edge 137. The build produces both Wasm and JS bundles automatically, falling back to JS on older browsers — no manual configuration needed.
WebAssembly lazy loading graduates from experimental to stable in this release. Flutter has explicitly stated that Wasm-by-default is the goal for a future stable release — 3.50 is laying that groundwork. For Flutter web users who’ve been skeptical about web performance, this is the trajectory worth watching.
iOS Touch Latency: One Frame Faster
Touch input latency on iOS drops by one full frame: 16ms on 60Hz devices, 8ms on ProMotion 120Hz displays. This is a rendering pipeline improvement — no code changes needed, it ships automatically on upgrade. The result is touch interactions that feel noticeably snappier, particularly on ProMotion iPhones where 8ms is a meaningful fraction of the frame budget.
One Bug to Watch Before You Ship
A regression landed post-launch: when versionCode is set only in AndroidManifest.xml and you’re using --split-per-abi, all split APKs get the same versionCode. Google Play rejects uploads with duplicate version codes. If you use split APKs, verify your builds before submitting or move versionCode to build.gradle as a workaround. A hotfix is expected.
How to Upgrade
Run flutter upgrade to get Flutter 3.50. Then run dart fix --apply --code=migrate_design_widgets for the material migration. Check the full breaking changes list before upgrading production apps — there are smaller behavioral changes around semantics, text, and RTL layout that may affect specific use cases. The official Flutter 3.50 release notes cover everything in full detail.

