November Cross-Platform Roundup: Flutter 3.50, .NET 11, and a Certificate Patch That Can't Wait
An eMudhra CA certificate compromise means any Flutter app on Android, Windows, or Linux that isn't rebuilt with 3.47.8 keeps a Man-in-the-Middle hole open. The same release cycle also raises the verification bar: .NET 11's CoreCLR default and Flutter's stable native interop touch runtime paths that don't show up in a quick build.
Flutter 3.50 ships November 11 with Dart 3.14, making FFIgen Objective-C and JNIgen Java/Kotlin bindings stable so Dart calls native APIs without platform channels. WebAssembly becomes an opt-in for Safari 26.2+ and Firefox 147+ via flutter_bootstrap.js, with measured frame rates more than double the JavaScript mode. The old material/cupertino entry points are deprecated, forcing migration via `dart fix --apply --code=migrate_design_widgets`. A separate security patch, 3.47.8, rejects eMudhra intermediate CA certificates exposed for weak private keys; Android, Windows, and old Linux builds need rebuilding and republishing.
Other frameworks move to stable or RC. .NET 11 releases with CoreCLR as the default MAUI runtime, XAML incremental hot reload as preview, and Android Shell on handler architecture. Kotlin 2.5.0 reaches RC with Swift Export in Beta and the unused-return-value checker on by default. React Native 0.88.1 is stable, and 0.89 RC removes old-architecture APIs. uni-app x 5.33 adds wgt resource hot update and Alipay mini-program support; 5.34 is a bug-fix release. The roundup's policy: production teams observe major versions for two months, but security patches go straight to evaluation and republishing.
The policy of watching a major version for two months while treating security patches as urgent creates a workable risk split: production stays on proven versions while the vulnerability window is closed immediately.
Cross-platform selection advice becomes less useful as companies accumulate custom models and framework-specific knowledge bases; presenting the state of each framework and letting teams decide fits that reality.
Flutter's official AI plugins and package skills put AI-assisted coding into the default toolchain, but the recommendation to try them on test projects first suggests the workflow isn't ready to replace everyone's process.