AI & tech update
Flutter 3.50: what changes for your app and what to do before December
Flutter 3.50 and Dart 3.14 move Material and Cupertino into separate packages, make native interop stable, raise Android defaults and start the clock on CocoaPods. Here is what matters for a business app.
The Flutter team released Flutter 3.50 with Dart 3.14 on 11 November 2026, followed by stable native interop on 12 November and A2UI 1.0 on 17 November. Most of the changes are good news, but a few of them create work you should plan for rather than discover the day a store update is due.
This is a summary for people who own or manage a Flutter app. Your developers will want the full release notes, linked at the end.
The changes that affect almost every app
Material and Cupertino are now separate packages
The built-in material.dart and cupertino.dart libraries are formally deprecated. New projects use the standalone material_ui and cupertino_ui packages instead. Existing apps keep working for now, and there is an automated migration:
dart fix --apply --code=migrate_design_widgets
What to do: schedule the migration in a normal sprint rather than leaving it until the old libraries are removed. It touches a lot of files but should be mostly mechanical.
Android defaults move up
New and upgraded projects now default to compileSdk and targetSdk API 36 (Android 16), minSdk API 24 and Java 17 as the minimum, with newer Gradle and Android Gradle Plugin versions. Google Play already requires new apps and updates to target Android 16, so this mostly brings Flutter's defaults in line with the store.
What to do: check that your build machines and CI use Java 17 or later, and test on an Android 16 device before your next release.
iOS: Swift Package Manager is the path forward
Flutter now warns on every command if Swift Package Manager is turned off, and CocoaPods trunk becomes read-only in December 2026. Plugins that only ship through CocoaPods will stop receiving updates there.
What to do: ask your developers to switch the app to Swift Package Manager and list any plugins that do not support it yet. This is the most time-sensitive item in the release. Flutter 3.50 also adds readiness updates for iOS 27, macOS 27 and Xcode 27.
Improvements you get for free
- Snappier touch on iPhone and iPad: touch input arrives one frame sooner, about 16 ms on 60 Hz screens and 8 ms on 120 Hz ProMotion displays.
- Safer Android deep links: release builds now ignore certain routing extras passed in by other apps, closing a class of unwanted navigation.
- Faster web apps: WebAssembly builds now run in Safari 26.2+ and Firefox 147+ (when opted in), as well as Chrome and Edge. A new
--web-content-hashbuild flag makes cache-busting after a deploy reliable.
Stable native interop
Two code generators are now stable: FFIgen for Objective-C (and C) and JNIgen for Java and Kotlin. They let Flutter code call native platform APIs directly instead of passing messages over platform channels, including synchronous calls and calls from background isolates.
For a business app this mostly means that features which used to need a custom plugin, such as a specific payment terminal SDK or a hardware scanner, are quicker and less fragile to integrate.
AI features: A2UI 1.0 and Genkit Dart
The Flutter team also shipped two AI-related pieces:
- A2UI 1.0 and
a2ui_flutter(previously calledgenui) let an AI agent answer with real, interactive Flutter widgets from a catalogue you control, instead of a block of text. The agent can only choose and arrange approved widgets; it cannot change your data, and invalid layouts are rejected instead of rendered. - Genkit Dart 1.0 is stable, with streaming, tool calling and tracing.
The Flutter team is clear that generative UI is not a replacement for normal screens: forms and lists still work better for predictable tasks. It is most useful where a user asks open questions, such as "compare my last three orders" in a support assistant.
A sensible upgrade plan
- Upgrade a branch to Flutter 3.50 and run the test suite.
- Move iOS builds to Swift Package Manager before December.
- Check CI uses Java 17+ and test on Android 16.
- Run the Material/Cupertino migration when you have a quiet sprint.
- Note native integrations that could be simplified with FFIgen or JNIgen next time you touch them.
If you are not sure which version your app is on, your developers can run flutter --version in the project. Anything more than a few releases behind is worth a conversation.
Sources
- What's new in Flutter 3.50, Flutter ()
- Announcing stable direct native interoperability, Flutter ()
- Announcing A2UI 1.0 and a2ui_flutter, Flutter ()
- What's new in the docs, Flutter documentation ()
- Flutter
Need your Flutter app upgraded?
We handle Flutter upgrades, the Swift Package Manager move and store releases, so your app keeps shipping without surprises.
Keep reading
- How to choose a custom software development companyWhat to look for, what to ask and which warning signs to watch for when choosing a company to build your software.
- MVP development cost: what founders should budgetWhat goes into the cost of an MVP, the line items founders forget, and how to plan a budget that leaves room to improve after launch.
- How much does it cost to build an app?The factors that decide what an app costs to build and run, and how to get an estimate you can compare between developers.