Breaking: .NET MAUI Adopts CoreCLR for Mobile Apps Starting .NET 11 Preview 4
In a strategic move to unify its runtime ecosystem, Microsoft has announced that .NET MAUI applications will now default to the CoreCLR runtime on Android, iOS, and Mac Catalyst starting with .NET 11 Preview 4. This change brings mobile apps onto the same high-performance engine that powers ASP.NET Core, Azure services, and millions of production workloads globally.
“This is a pivotal moment for .NET on mobile,” said Richard Lander, Program Manager at Microsoft. “By moving to CoreCLR, we eliminate the runtime split that has long complicated development and diagnostics. Developers can now enjoy a single runtime across their entire stack.”
Background
For over 15 years, the Mono project—started by Miguel de Icaza in 2001—was the backbone of .NET on non-Windows platforms. It began as an ambitious effort to bring .NET to Linux and quickly evolved into a mobile powerhouse. MonoTouch (2009) and MonoDroid (2011) enabled C# on iPhone and Android, later consolidated into Xamarin. When Microsoft acquired Xamarin in 2016, Mono became the default runtime for .NET MAUI.
Mono’s impact extends far beyond Microsoft. Unity Technologies built its scripting engine on Mono, powering millions of games. Avalonia and Uno Platform use Mono for WebAssembly and mobile. MonoGame and Godot also rely on it. “Mono didn’t just enable .NET on mobile—it proved .NET could go anywhere,” Lander added.
What Changed
Starting with .NET 11, CoreCLR is now the default runtime for both Release and Debug builds on Android, iOS, Mac Catalyst, and tvOS. This is an extension of Microsoft’s ongoing effort to bring CoreCLR to more platforms—previously Windows, Linux, macOS (AppKit), and Android. The last holdouts—iOS and Mac Catalyst—have now transitioned.
Key clarifications:
- Blazor WebAssembly remains on Mono; no change in .NET 11.
- Developers can opt back to Mono if they encounter issues during the transition.
Why CoreCLR
Three drivers prompted the shift. First, runtime unification eliminates the split between Mono (mobile) and CoreCLR (server/desktop), ensuring consistent JIT, GC, diagnostics, and behavior. Second, performance improvements from CoreCLR’s optimized JIT and GC benefit mobile apps. Third, tooling alignment means developers use the same profilers, debuggers, and analyzers across all .NET projects.
What This Means
For developers, the move to CoreCLR promises a more consistent development experience. Mobile apps will behave similarly to their server counterparts, reducing runtime-specific bugs and simplifying optimization. The change applies to all new .NET MAUI projects targeting .NET 11; existing projects can migrate gradually.
While Mono’s legacy is honored, this transition marks a new chapter. “CoreCLR becoming the default for .NET MAUI is the next chapter of that story, not its ending,” Lander concluded. The full documentation is available in the Runtimes and compilation documentation.
Related Articles
- Inside Google's 'Book' Revolution: Premium Chromebooks and Upgrade Options
- 10 Key Insights into Apple's App Store Strategy for AI
- .NET MAUI Embraces CoreCLR: A Unified Runtime for Mobile and Beyond
- Apple and Google Enable Encrypted RCS Texting: What iPhone and Android Users Need to Know
- What .NET MAUI's Shift to CoreCLR Means for Your Mobile Apps
- Data Normalization: Use Cases, Pitfalls, and Strategic Trade-offs
- Google's Desktop Android: Aluminium OS Leak Reveals Key Features and Early Design
- Snapseed 4.0 Arrives on Android: A Major Overhaul After Years of Silence