Mobile Development

Flutter 3.50 and Dart 3.14: Stable Native Interop, Tighter Android Intents, SwiftPM as the New Direction

Flutter 3.50 was released with Dart 3.14 on 11 November 2026. Direct native interop is now stable, Android Intents are tightened, and the move away from CocoaPods begins.

By Oemah Solution Editorial 4 min read

This article was prepared with AI assistance from the official sources listed below, and checked automatically before publication.

The Flutter team released Flutter 3.50 together with Dart 3.14 on 11 November 2026. According to the Flutter Blog, this release makes direct native interoperability stable, tightens Intent security on Android, and begins steering iOS developers away from CocoaPods. For teams managing Flutter apps in Indonesia, the release brings opportunities as well as migration work that needs to be planned.

Direct native interop is now stable

The Flutter Blog explains that FFIgen for Objective-C and JNIgen for Java and Kotlin are now stable, following C support in FFIgen, which had already reached stable status. The native interop mode in Pigeon is still in preview.

With this feature, Dart code can call platform APIs without sending messages through platform channels. Calls can even be made synchronously or from a background isolate. The aim is to remove the serialisation overhead, string-based plumbing and asynchronous latency inherent in platform channels.

For organisations that integrate local SDKs such as payments, eKYC or biometrics, this approach could reduce glue code. However, this value should be tested in real-world cases before it is used as the basis for a decision.

Stronger Intent security on Android

Another important change concerns security. In release builds, Flutter 3.50 now ignores the route, dart_entrypoint and cached_engine_id values that come from external Intent extras. Release builds also reject engine flags at runtime, such as --dart-flags, whether they come from Intent extras or from a previously built release APK (--use-application-binary). Standard deep linking is not affected.

Previously, other apps on the same device could direct the entrypoint of a release app. Teams whose code depends on Intent extras need to review and retest after the update.

Toolchain and build changes

Several changes affect build pipelines and CI machines:

  • Swift Package Manager: because the CocoaPods trunk becomes read-only in December 2026, disabling Swift Package Manager now triggers a warning on every Flutter CLI command from 3.50 onwards. The flag to opt out will be removed in a future release.
  • Apple Silicon: Flutter no longer tests on Intel Mac hardware, and the CLI shows a one-time warning when building on an Intel Mac. A future release will require an Apple Silicon Mac to build for iOS, macOS and Android.
  • Android: new projects use AGP 9.3.1, Gradle 9.5.0, Kotlin Gradle Plugin 2.4.20, and a minimum of Java 17. The defaults are compileSdk API 36, targetSdk API 36 and minSdk API 24.

Design packages and deprecations

The standalone material_ui and cupertino_ui packages are now the default for new projects. As a consequence, the package:flutter/material.dart and cupertino.dart libraries that are still directly tied to the official framework are deprecated. Long-lived codebases should prepare a phased migration plan.

On the web, the Flutter Blog notes that Safari 26.2+ and Firefox 147+ deliver more than twice the frame rate of JavaScript on heavy widget benchmarks when WebAssembly is enabled. Older JS interop libraries such as dart:html and package:js are also deprecated in favour of dart:js_interop and package:web.

The Flutter Blog also mentions that the community has passed one million Flutter apps on Google Play, along with a measured 23% performance improvement on iOS from recycling inline AdMob banners in scrollable lists.

Practical steps for teams in Indonesia

  • Schedule the upgrade to Flutter 3.50 and retest features that read Intent extras.
  • Audit the iOS pipeline and enable Swift Package Manager before the warning becomes a requirement.
  • Check whether build machines, including CI runners, already use Apple Silicon.
  • Make sure the Android environment supports Java 17 and the latest AGP and Gradle versions.
  • Plan the migration away from the old Material and Cupertino libraries and the old JS interop.

This release is more than just new features: it sets deadlines that need to be anticipated from now.

#flutter#dart#mobile development#native interop#android security

Sources & references

This article is a summary and interpretation by the Oemah Solution team of the sources below. Refer to the original sources for full details and context.

  1. What's new in Flutter 3.50 Flutter Blog (flutter.dev) · flutter.dev