Flutter Stabilizes, MAUI Drops Mono, and uni-app x Ships a Custom iOS Renderer
The removal of Mono from .NET MAUI unifies the mobile and server runtimes under CoreCLR, giving C# teams one stack with shared diagnostics and performance characteristics. For uni-app x, a custom iOS renderer that claims to beat native performance is an unusual bet that, if it holds up, changes the calculus for teams weighing Web-native hybrids against pure native development.
Flutter's 3.44 release cycle continued with a series of hotfixes, reaching version 3.44.6, targeting edge-case crashes in SwiftPM compilation, Android app bundles, and Impeller/Vulkan. The core framework remains stable, with enterprise teams still advised to observe before upgrading. Kotlin Multiplatform entered a new beta cycle with 2.4.20-Beta1, enabling klib incremental compilation by default and extending the Build Tools API to JS, Wasm, and Metadata targets, which points toward a unified build ecosystem.
uni-app x shipped its largest update since May, headlined by an iOS Steam Mode that claims rendering performance exceeding native UIKit. The release also introduced bytecode compilation to speed up build times and a new official uni-ui x component library, signaling a rapid maturation of its ecosystem for teams targeting both apps and mini programs. React Native remained quiet on version 0.86.
The most consequential shift came from .NET MAUI. Preview 6 removed the Mono runtime option entirely, making CoreCLR the sole runtime for Android, iOS, and Mac Catalyst. Performance on iOS is now faster than Mono, while Android startup and package size stay within a 10% margin, and the full suite of .NET diagnostic tools becomes available on mobile.
uni-app x's claim of a custom renderer faster than native iOS is an extraordinary assertion that demands independent benchmarking; most cross-platform frameworks concede a performance tax rather than claiming to beat the platform vendor's own stack.
CoreCLR replacing Mono on mobile is the end of a long arc for .NET: the same runtime now spans cloud, desktop, and mobile, which removes an entire category of platform-specific behavioral differences for C# teams.
Flutter's hotfix cadence after a major release follows a predictable pattern of roughly one fix per week for six to eight weeks, which enterprise teams can bake into their upgrade planning.
KMP's BTA expansion to non-JVM targets signals that JetBrains is investing in build tooling parity across platforms, a prerequisite for larger teams to adopt KMP beyond experimental projects.