跪拜 Guibai
← Back to the summary

November Cross-Platform Roundup: Flutter 3.50, .NET 11, and a Certificate Patch That Can't Wait

Hello, I'm Old Liu

It's time for the monthly cross-platform framework roundup again. Some friends have asked why I'm no longer giving cross-platform framework selection advice.

On one hand, technology selection isn't purely a technical issue; it's a comprehensive decision that considers team background, project situation, and even leadership preferences.

On the other hand, with the arrival of the AI era, the original selection logic has changed. Some larger vendors deploy their own post-trained models, and some vendors have knowledge bases based on historical code of a particular framework. These factors further fragment framework selection strategies.

So now I mainly present the progress of each mainstream framework and give brief comments. If a human reads this article, they can get a holistic understanding of the current cross-platform landscape. If AI reads it, it also helps AI make technology selections.

Alright, let's see what changed in the cross-platform world in November.

Flutter 3.50 brings stable native interop, .NET 11 ends RC phase, RN 0.88.1 takes over stable version, Kotlin 2.5.0 also reaches RC. With so many versions, the upgrade order cannot be wrong.

This article is compiled from official release pages as of November 17, giving you an executable upgrade checklist.


1. November Cross-Platform Technology Overview

November's cross-platform keywords are formal version landing and migration verification.

① Flutter

3.50 officially released, major changes in native interop, Web, and design packages

On November 11, Flutter 3.50 was released with Dart 3.14. FFIgen's Objective-C support and JNIgen's Java/Kotlin support reached stable stage, allowing Dart to call native APIs bypassing platform channels. Material and Cupertino continue to be split into packages, and old entry points are officially deprecated. The current stable channel is 3.50.0, and the official changelog hasn't listed 3.50.x hotfixes yet. The 3.47 series also has a 3.47.8 certificate security fix; production projects continue the strategy of observing major versions for two months, while certificate fixes are evaluated separately as security patches.

② React Native

0.88.1 becomes current stable, 0.89 begins cleaning old architecture

RN 0.88.0 was released on October 15, and 0.88.1 followed on October 27. 0.88 switches to Web-style event dispatch by default, supports variable fonts and iOS SceneDelegate. The official release still lists it as a version with no user-facing breaking changes. The 0.89 RC released in November begins removing old architecture APIs, widening the upgrade gap.

③ KMP

2.5.0 RC released, Swift Export enters Beta

Kotlin 2.5.0-Beta2 was released on October 21, and 2.5.0 RC on November 11. The current stable version remains 2.4.21. 2.5.0 turns the unused-return-value checker into a stable default, Swift Export enters Beta, and introduces an experimental multi-platform .kar publishing format.

④ uni-app x

5.33 fills resource hot update and Alipay mini program, 5.34 focuses on fixes

After the previous issue, uni-app x released 5.33.2026102401 and 5.34.2026102909. 5.33 adds wgt resource hot update for Android/iOS steam mode, Alipay mini program, uasm plugin, and CSS animations. uvue scripts default to TypeScript. 5.34 continues to fix compiler, Web, Android, iOS, and HarmonyOS issues.

⑤ .NET MAUI

.NET 11 official version released, CoreCLR becomes default runtime

On November 10, .NET 11 was officially released, an STS version supported for two years. MAUI defaults to CoreCLR, XAML incremental hot reload is provided as preview, Android Shell switches to handler architecture, and Windows defaults to CollectionView2. This upgrade needs more verification than RC2.


2. Flutter 3.50 Officially Released, Native Interop Enters Stable Stage

Flutter 3.50 announcement: https://flutter.dev/blog/whats-new-in-flutter-3-50

Flutter changelog: https://docs.flutter.dev/release/release-notes

On November 11, Flutter 3.50.0 was released, bundling Dart 3.14. This isn't a stack of hotfixes; native interop, Web build, design packages, and mobile toolchain all have substantial changes.

2.1 Dart Can Call Native APIs Directly

FFIgen's Objective-C bindings and JNIgen's Java/Kotlin bindings reach stable. Dart can call platform APIs directly via FFI and JNI, supporting synchronous calls and execution in background Isolates. Pigeon's new native interop mode remains preview.

Teams building plugins can write less platform channel serialization code, but they still must manage native object lifecycle, threading, and binding generation config. The call path is shorter, but engineering requirements don't disappear.

2.2 WebAssembly and Cache Deployment Continue to Strengthen

Safari 26.2+ and Firefox 147+ can now opt-in to WebAssembly via web/flutter_bootstrap.js. The official heavy Widget benchmark shows frame rates over double the JavaScript mode, but it requires manual configuration; later versions will default to it.

flutter build web --web-content-hash adds content hashes to JS, WebAssembly, and asset file names, and updates flutter_bootstrap.js. Hashed static assets can be cached long-term, while entry files use no-cache, making the old-resource problem after releases easier to handle.

Old dart:html, dart:js, dart:js_util, and package:js have entered deprecation. Teams can use --no-deprecated-js-interop to check projects and dependencies early to prepare for WebAssembly.

2.3 Material and Cupertino Old Entry Points Officially Deprecated

package:flutter/material.dart, package:flutter/cupertino.dart, and their localization delegates are officially deprecated. New projects default to the independent material_ui package. Existing projects can run the following command:

dart fix --apply --code=migrate_design_widgets

This change touches many imports. The more business pages, the more you should run automatic migration first, then check custom themes, localization delegates, and dependency package compatibility.

2.4 Mobile Upgrades: Watch These Changes

After iOS touch dispatch adjustments, official measurements show 16ms input latency reduction on 60Hz devices and 8ms on 120Hz ProMotion devices. iOS 27 real-device debugging white screen and occasional startup crashes are fixed. Xcode 27 re-enables CLI screen capture from real devices.

Android release builds now ignore externally provided route, dart_entrypoint, and cached_engine_id in Intents, and block runtime engine parameters. Deep links remain supported, but debugging or integration schemes relying on these internal entry parameters need changes.

New Flutter 3.50 Android projects default to AGP 9.3.1, Gradle 9.5.0, and Java 17, with compileSdk and targetSdk at API 36, minSdk at API 24. Plugins still need to migrate to AGP Built-in Kotlin; old KGP integration won't build with AGP 10.

2.5 Flutter 3.47.8 Alone Handles Certificate Trust Issues

Dart official security advisory: https://github.com/dart-lang/sdk/security/advisories/GHSA-frr6-h895-5pxp

In October 2026, eight intermediate CA certificates issued by eMudhra were publicly disclosed due to insufficient private key generation strength. Attackers who can access the network path between the app and server can use these private keys to forge TLS/HTTPS certificates and perform Man-in-the-Middle attacks.

Affected platforms are Android, Windows, and Linux environments that haven't updated system certificate packages. Web, iOS, and macOS use browser or Apple system security frameworks for certificate validation and are not affected.

Flutter 3.47.8 bundles Dart 3.13.7, which updates BoringSSL to directly reject affected intermediate CA certificates. On Android 14+, dart:io also loads system root certificates from the updatable Conscrypt APEX module, allowing revocation via Google Play system updates.

On Android, Windows, and Linux, package:http and dio typically go through dart:io, so you can't assume the app is safe just because the browser and OS are updated. Upgrade the SDK, rebuild, and republish; old installs on user devices still carry the old network stack. Projects involving accounts, payments, or sensitive data should evaluate handling of old versions along with network exposure and user update rates.

2.6 Old Liu's Comment

My fixed strategy for Flutter major versions hasn't changed: production projects observe for two months before considering upgrades. 3.50 released on November 11; now is the time to create a test branch, check dependencies, and do technical validation. Production environment shouldn't switch yet. Observe until January 2027, then arrange a production upgrade window based on hotfix quality, third-party plugin adaptation, and project regression results. Personal projects and tech enthusiasts can try 3.50 early.

In these two months, focus on three things.

  1. Early user feedback and hotfix status.
  2. Whether third-party plugins used by the project have adapted, especially native interop, old Web JS libraries, and design package dependencies.
  3. Whether test-branch Android, iOS, and Web builds and regressions are stable; don't just check if it runs locally.

Certificate fixes are an exception to the two-month observation policy. Projects still on 3.47 series and covering Android, Windows, or Linux should evaluate 3.47.8 and republish promptly per the official advisory, and don't use the observation period as a reason to delay security fixes. Projects already on 3.50 also include this fix, but still need to rebuild and republish to cover production users.

The official release also includes AI programming plugins and package skills. Plugins include Dart/Flutter MCP configuration, dedicated Agents, and hot-reload rules. pub.dev packages can also include skills in a top-level skills/ directory. AI-assisted development is entering Flutter's official toolchain. Teams can try it on test projects, but don't change everyone's workflow yet.


3. KMP 2.5.0 RC Released, Swift Export Enters Beta

Kotlin 2.5.0 RC docs: https://kotlinlang.org/docs/whatsnew-eap.html

Kotlin release page: https://github.com/JetBrains/kotlin/releases

The 2.5.0-Beta2 released on October 21 and 2.5.0 RC on November 11 complete the outline for 2.5.0. The current stable remains Kotlin 2.4.21, and 2.5.0 continues the pre-release process.

3.1 Return Value Checker Enabled by Default

The unused-return-value checker enters stable in 2.5.0 and is on by default. Previously, ignoring return values from function calls often only got caught by Code Review; now the compiler can check directly.

Experimental full value classes allow a value class to contain multiple properties, enabled via -Xfull-value-classes. It auto-generates equals(), hashCode(), and toString(), but currently doesn't provide componentN() and copy(), so it's still a ways from widespread business use.

3.2 Swift Export Changed Gradle DSL

Swift Export enters Beta in 2.5.0. The configuration entry changes from swiftExport {} to export { swift {} }. Declared dependencies are auto-exported, no longer requiring explicit export() calls for each.

The RC also fixes Swift package linking failures in Release builds. Teams building iOS shared libraries can use RC to validate export and linking flows; production projects should wait for the final release.

3.3 Multi-platform Library Adds .kar Publishing Format

Besides JVM and Android, multi-platform artifacts can be packaged into a single .kar file. It's a ZIP archive with extra XZ compression, reducing the number of published files as new targets are added.

The official docs' cryptography-kotlin example shows the whole multi-module project shrinking from 7539 files, 91MB to 1036 files, 23MB. Publishing .kar is still experimental, but all projects can consume these artifacts; it mainly affects library authors.

3.4 Old Liu's Comment

2.4.21 remains the stable choice for production; 2.5.0 RC is suitable for test branches. Focus on validating new warnings from the return value checker, Swift Export DSL, and iOS linking, not just Gradle sync.

Toolchain also needs early checks. Beta2 logs raised minimum Gradle to 8.14.x and minimum AGP to 8.8.2. RC docs also clarify higher compiler runtime requirements; JDK below 17 will error, with a temporary opt-out planned for removal in 2.5.20 or 2.6.0.

Regarding BTA defaulting from last issue, RC docs didn't explicitly state it this time, so I won't infer. Monthly roundups stick to what's in official docs; unconfirmed content doesn't guide upgrades.


4. React Native 0.88.1 Enters Stable Maintenance, 0.89 Begins Cleaning Old Architecture

React Native 0.88 announcement: https://reactnative.dev/blog/2026/10/19/react-native-0.88

React Native release page: https://github.com/react/react-native/releases

RN 0.88.0 was released on October 15, and the official introduction on October 19. On October 27, 0.88.1 was released, becoming the current stable. On November 4 and November 10, 0.89.0-rc.0 and rc.1 were released.

4.1 Event Dispatch Switches to Web Model

0.88 dispatches events via the W3C EventTarget API by default, where events travel down the capture path to the target, then bubble up. Public APIs like onPress, onLayout remain unchanged, and the touch response system is unchanged.

The official release states 0.88 has no user-facing breaking changes. However, libraries that read event internals directly or use old plugin registries need focused regression testing; such code bypasses public APIs and can't be verified by compile success alone.

4.2 Variable Fonts, ArrayBuffer, and SceneDelegate Land Together

Text and TextInput support fontVariationSettings on both Android and iOS, with both string and object syntax. Java TurboModules can now receive and return ArrayBuffer directly, so binary data doesn't need to be encoded as strings or number arrays.

The iOS 27 SDK requires UIKit apps to adopt the UIScene lifecycle. RN 0.88 adds a SceneDelegate entry while keeping AppDelegate compatibility. Support is currently limited to a single Scene; migration also needs to handle Info.plist, URL context, and user activity forwarding.

4.3 0.88.1 Continues Fixing Build and Platform Details

0.88.1 adjusts iOS Release build C/C++/Objective-C optimization from -Os to -O2, and Yoga and glog also use -O2. SwiftPM generation config moves to the ReactNativeSPM directory, so version upgrades no longer repeatedly modify project.pbxproj.

This patch also handles iOS 27 status bar, images showing stale images after reuse, SafeArea offsets, and Android text decoration and measurement issues when reusing Paint. Teams already on 0.88.0 can evaluate 0.88.1 directly.

4.4 0.89 RC Migration Costs Start to Increase

0.89 RC enables Bridgeless by default in Android and iOS new architecture, removing a batch of old-architecture entry points and deprecated APIs. @react-native/community-cli-plugin needs to be explicitly added to devDependencies. Community CLI requires 21.x.

Android TurboModule libraries carrying pre-generated JNI codegen need to regenerate with 0.89. iOS libraries have adjustments to CocoaPods header search paths and Swift nullability annotations. rc.1 mainly fixes WebSocket debugging, Metro caching, and Android view crashes; the scope is shrinking.

4.5 Old Liu's Comment

Business projects still on 0.87 can set 0.88.1 as this cycle's upgrade target. First check direct dependencies on RN event internals, then verify iOS SceneDelegate and common third-party libraries. Public API stability doesn't mean the whole dependency chain has no adaptation cost.

0.89 RC is better for framework, native module, and third-party library maintainers to validate early. Ordinary business projects don't need to rush for this RC; waiting for the final release and dependency adaptation notes makes upgrade costs easier to estimate.


5. uni-app x 5.33 Adds Resource Hot Update, 5.34 Focuses on Fixes

uni-app x changelog: https://doc.dcloud.net.cn/uni-app-x/release.html

After the previous issue, uni-app x released 5.33.2026102401 and 5.34.2026102909 in succession. As of November 17, the official log still shows 5.34 at the top, with no new builds this month.

5.1 Steam Mode Supports wgt Resource Hot Update

5.33 adds wgt resource hot update for Android and iOS steam mode. Teams needing quick updates to in-app resources now have an official implementation path.

uvue scripts now support both lang="ts" and lang="js", defaulting to TypeScript on Web, App steam mode, and mini-program platforms. Note: ts/js no longer support uts-specific objects; existing pages need to check types and compiled output when upgrading.

5.2 Alipay Mini Program and uasm Plugin Added

5.33 adds Alipay mini-program support, uasm plugin for Web, App steam mode, and mini-program platforms, and Node API support on App platform. Cross-end coverage expands another notch.

Steam mode's CSS capabilities are also filling in; animation, @keyframes, and calc() are now in the official changelog. Android-side Tencent Maps, Gexin push, and Alibaba Real-name Authentication SDK have completed 16KB memory page size adaptation.

5.3 5.34 Fixes Compilation and Multi-end Display Issues

5.34 lists no new features, focusing on fixing match-media release errors and Web attribute failures, Android steam mode textarea long-press selection, iOS tab bar layout after landscape/portrait return, and HarmonyOS rich-text and SVG image display.

iOS VDOM and HarmonyOS VDOM also fixed a problem introduced in 5.31 where uvue TypeScript files weren't compiled as uts. 5.33 had already fixed uts plugin compilation failure after upgrading Xcode 27, but the log doesn't state that cloud build environments have switched to Xcode 27; those two things shouldn't be conflated.

5.4 Old Liu's Comment

Teams already on 5.33 should follow up to 5.34; fixes cover compiler and multiple platforms, so the upgrade target is clear.

Projects coming from 5.26 should set aside validation time. wgt hot update, Alipay mini program, and CSS animations are worth trying; uvue default TypeScript directly affects existing code. Run a complete compile first, then check uts-specific objects, lists, rich text, and theme switching, not just whether the homepage opens.


6. .NET MAUI Lands with .NET 11, CoreCLR Becomes Default Runtime

.NET 11 announcement: https://devblogs.microsoft.com/dotnet/announcing-dotnet-11/

.NET MAUI 11 docs: https://learn.microsoft.com/en-us/dotnet/maui/whats-new/dotnet-11?view=net-maui-11.0

On November 10, .NET 11 official version was released, with C# 15 landing together. .NET 11 is an STS version supported for two years. MAUI has its own support policy, so you can't equate those two years with MAUI support duration.

6.1 CoreCLR Becomes Default Runtime

.NET 11 MAUI defaults to CoreCLR on all platforms; Mono remains. Apple platforms don't allow JIT compilation, so the runtime uses precompiled code and interpreters. Native AOT remains an optional publishing mode, with Android support still experimental.

This affects debugging, profiling, hot reload, trimming, and app publishing. Projects using native dependencies or custom publishing flows need to retest with the actual publishing mode.

6.2 XAML and Native Controls Continue to Adjust

XAML Incremental Hot Reload remains a preview feature in .NET 11, enabled by default in Debug builds. It supports updating running pages and control instances, and handles some structural modifications.

Implicit XAML namespaces reduce repeated declarations, Windows defaults to the new CollectionView2 handler, and Android Shell switches to handler architecture. Navigation, custom handlers, and collection controls should all be in the upgrade regression checklist.

6.3 Test Templates Enter CLI Workflow

New test project templates for Android, iOS, tvOS, macOS, and Mac Catalyst can run via dotnet test on devices, simulators, or desktop targets. Templates use Microsoft.Testing.Platform, bringing device tests into a unified CLI flow.

The optional Microsoft.Maui.Controls.Compatibility package is no longer shipped with .NET 11; projects still referencing it need to migrate. When upgrading from RC, also switch SDK, runtime, NuGet packages, and workloads to the final version.

6.4 Old Liu's Comment

Final release doesn't mean you can skip migration validation. CoreCLR default, Android Shell handler, and Windows CollectionView2 all touch running paths; regression scope is larger than a typical patch.

Use the final SDK to create an upgrade branch, and get navigation, custom handlers, trimming, and native dependencies working. Teams that evaluated based on RC2 should re-check final package versions, and don't keep a mixed environment of RC SDK with final projects.


7. November Cross-Platform Technology Changes Summary

Framework October Status November Status Key Changes
Flutter 3.47.7 3.50.0, 3.47.8 security fix Native interop stable, WebAssembly expansion, design package old entries deprecated, certificate trust fix
KMP 2.4.21, 2.5.0 Beta1 2.4.21, 2.5.0 RC Return value checker default, Swift Export Beta, experimental .kar publishing format
React Native 0.87, 0.88 RC5 0.88.1, 0.89 RC1 Web-style event dispatch, variable fonts, SceneDelegate, 0.89 continues removing old architecture APIs
uni-app x 5.26 5.34.2026102909 wgt resource hot update, TypeScript default, Alipay mini program, uasm and CSS animations
.NET MAUI .NET 11 RC2 .NET 11 final CoreCLR default runtime, XAML incremental hot reload preview, handler adjustments, CLI test templates

Old Liu's Suggestions

  1. Flutter users Production projects continue the two-month observation strategy; use test branches for 3.50 now, observe until January 2027 before deciding production upgrade window. Projects still on 3.47 series on Android, Windows, and Linux should evaluate the 3.47.8 certificate fix separately, rebuild and release after upgrade; security fixes don't wait for the observation period.

  2. KMP users Production continues with 2.4.21. 2.5.0 RC focuses on validating Swift Export, return value checks, and JDK 17 environment. Library authors can additionally evaluate .kar publishing.

  3. RN users 0.87 projects can evaluate 0.88.1, focusing on event-related third-party libraries and iOS SceneDelegate. Leave 0.89 RC to test branches and native library maintainers.

  4. uni-app x users 5.33 projects can follow up to 5.34. Cross-version upgrades should check the impact of uvue default TypeScript and fully validate uts plugins and multi-end pages.

  5. MAUI users Re-run upgrade evaluation based on .NET 11 final. Cover CoreCLR, navigation, custom handlers, trimming, and native dependencies; don't carry RC-stage conclusions directly to production.

This month's upgrade tasks are clear. Pick a test branch, run the framework upgrades the project actually depends on, then decide when production follows. Which framework are you most concerned about, and where are you stuck in the upgrade? Feel free to share your situation.


Old Liu has been doing client development for a long time and is also continuously practicing AI programming and workflow transformation. This records experiences, judgments, and pitfalls from real projects and daily use, trying to clearly explain applicable scenarios, costs, and boundaries.

📂 Old Liu's historical articles are also organized in a GitHub repo for easy reference.

🔗 https://github.com/lzt-code/blog