What's new in Flutter 3.50

Material and Cupertino deprecated, direct calls to native code and changes on iOS, Android and web.

Flutter 3.50 came out on 11 November alongside Dart 3.14. These are the changes we found most interesting as a studio that works with Flutter since 2018, and what they mean for an app that's already published.

Material and Cupertino are now deprecated

Over the summer we covered how Material and Cupertino were moving out of the framework into their own packages, material_ui and cupertino_ui. Flutter 3.50 takes the next step: the usual imports, material.dart and cupertino.dart, are marked as deprecated, and a new project created with flutter create uses material_ui by default.

Deprecated means the code still works and the compiler warns you. Nothing breaks today. The migration is a single dart fix command that rewrites the imports, and for most apps it's a mechanical change. Even so, we recommend doing it in an update planned for that purpose, with time to test, rather than mixed into a feature release.

Calling native code without platform channels

Until now, when a Flutter app needed something specific to iOS or Android (Bluetooth, a manufacturer's SDK, a system API), it went through platform channels, messages passed back and forth between Dart and native code, always asynchronously. It works well, but it means maintaining glue code by hand on both sides.

In 3.50, FFIgen (for C and Objective-C) and JNIgen (for Java and Kotlin) are stable. They generate direct, typed calls to native APIs from Dart, and those calls can be synchronous or made from background isolates. 

It will make the most difference in apps that talk a lot to hardware or native SDKs, like the one we maintain for Hidrasol, which connects over BLE to the controller boards of its moving floors. There, less glue code means less to check every time a new version of iOS or Android comes out.

What changes on iOS and Android with Flutter 3.50

On iOS, the first thing any user will notice is touch response. Touch events are now delivered without waiting for the next frame, which cuts 16 ms on 60 Hz screens and 8 ms on 120 Hz ones, with no changes to the app. Debugging issues on devices running iOS 27 and Xcode 27 are also fixed.

Swift Package Manager does need some work. CocoaPods stops accepting new releases in December 2026, and disabling SwiftPM now shows a warning on every command. We explain what to do about them in our article on SwiftPM and Gradle warnings when building Flutter. 

On Android, tool versions go up (AGP 9.3.1, Gradle 9.5.0 and Java 17 as a minimum), the default compileSdk and targetSdk move to API 36 and the minimum to API 24. If your app still supports Android 6, now is a good time to review that. Plugins that apply the Kotlin plugin manually will get lower pub.dev scores and stop building with AGP 10, so the dependency inventory is once again the first thing to look at. In release builds, the app now ignores certain parameters coming from external intents, such as the initial route. It's a security change, and there's nothing to do if the app didn't rely on them.

Flutter 3 50 news

WebAssembly in Flutter web now runs on Safari and Firefox

Flutter web apps compiled to WebAssembly can now run on Safari 26.2 and Firefox 147 onwards, as well as Chrome and Edge. You have to opt in explicitly, and in the Flutter team's tests with heavy interfaces the frame rate is more than double that of JavaScript.

There are two more changes for anyone running Flutter on the web. An option to add hashes to file names, which stops the browser from serving an old version after you publish, and a preview of a new text engine that cuts the CanvasKit download from 5.46 MB to about 3.75 MB. The old JavaScript interop libraries, such as dart:html and dart:js, are also deprecated.

Dart 3.14 and AI tooling

Dart 3.14 brings dart migrate, a command that updates a package's code and SDK version to the next language version. When you maintain several apps, anything that automates part of the update is welcome.

On the AI side, Flutter publishes official plugins for coding agents, with the Dart and Flutter MCP server configuration plus ready-made rules and skills. Packages can also ship their own skills so the agent knows how to use them. We work with agents every day and find it useful when a package's documentation reaches the agent in a format it understands, because it makes fewer mistakes. The code they generate is still reviewed by someone on the team before it's accepted.

What to do if you have a Flutter app in production

None of these changes means you have to update tomorrow. The one with a date is CocoaPods, in December, and later on AGP 10 and the removal of the Material and Cupertino imports will follow, with no date yet. We usually wait for the first patch releases before updating the apps we maintain, and use that time to check which plugins are up to date.

If an app hasn't been touched for a while, every version that's been skipped adds Xcode, Gradle and plugin changes. Upgrading regularly, as part of your app maintenance, saves you from having to do it all at once.

Flutter
Dart
Android
iOS

Frequently asked questions

There's no need to do it straight away. The sensible approach is to wait for the first patch releases and update once the plugins the app uses are compatible.

For now, yes, although Flutter 3.50 shows a warning the first time. Flutter has stopped testing on Intel Macs, and future releases will require Apple Silicon to build iOS, macOS and Android apps.

The versions already installed keep working. But if the app uses Flutter 3.50's default values, the minimum moves to Android 7 (API 24), so those phones will stop getting updates. If some of your users are on them, it's worth deciding before you update.