Flutter 3.50 and Dart 3.14 Ship Faster iOS Touch, Stable Native Interop, and Wasm on Safari and Firefox
A free 16ms touch latency cut on iOS and a security fix on Android are concrete reasons to upgrade, and the Material/Cupertino deprecation will force a migration eventually; doing it now via one command is far cheaper than untangling mixed imports later.
Flutter 3.50 and Dart 3.14 land with a clear focus on shedding legacy. The SDK's Material and Cupertino libraries are officially deprecated, with material_ui and cupertino_ui taking over as standalone packages; a single `dart fix` command migrates existing projects. iOS gets a full-frame touch latency reduction by removing outdated buffering layers, and the engine now handles touch events in the same refresh cycle, saving 16ms on 60Hz devices and 8ms on ProMotion displays. Android release builds stop accepting runtime configuration from external Intent extras, closing a security hole, and HCPP expands for hybrid native views.
Native interop goes stable with FFIgen for Objective-C and JNIgen for Java/Kotlin, making direct API calls without platform channels a production option. WebAssembly support extends to Safari and Firefox, with content-hashed builds solving the stale-JS caching problem. Desktop gets a slew of improvements: Impeller's SDF renderer takes over shapes on GPU, Windows handles non-ASCII paths, and Linux gains more window control. The multi-window API is renamed and restructured, though still experimental.
The toolchain adds `dart migrate` for breaking changes and speeds up Analysis Server renames. The article's own advice: upgrade for the iOS latency win, but check a few migration gotchas first—external Intent dependencies, removed `ignoringSemantics`, and SPM settings.
The iOS touch latency fix comes from deleting cross-thread buffering that was left over from when touch events and rendering lived on different threads; it's a textbook example of how architectural debt quietly degrades performance.
Deprecating Material and Cupertino from the SDK is a bigger break than a typical deprecation list; it tells plugin owners and app teams that the design libraries now move at their own pace, outside the engine's release cycle.
Native interop reaching stable is the payoff of a long bet: FFIgen and JNIgen let Flutter apps call platform APIs directly, which for many use cases makes platform channels optional rather than mandatory.
The Wasm expansion to Safari and Firefox closes the last major browser gap for Flutter web, but the allowlist and manual configuration mean it's not yet friction-free.