Introduction
Starting with .NET 11 Preview 4, .NET MAUI applications on Android, iOS, and Mac Catalyst now run on the CoreCLR runtime by default. This marks a pivotal shift: the same high-performance runtime powering ASP.NET Core, Azure services, and desktop applications becomes the foundation for mobile development. For developers, this means a unified runtime experience across all .NET workloads, from cloud to phone.
The Legacy of Mono: How It Paved the Way
For over 15 years, the Mono project served as the runtime that brought .NET to platforms it was never originally designed for. It all began in 2001 when Miguel de Icaza launched Mono with the ambitious goal of enabling .NET on Linux. From that seed grew an ecosystem that nobody could have predicted.
From Linux to iPhone and Beyond
Mono’s mobile journey took off in 2009 with MonoTouch, which brought C# to the iPhone. MonoDroid followed for Android, and together they formed the core of Xamarin — a platform that let millions of developers ship production mobile apps using C#. When Microsoft acquired Xamarin in 2016 and began shaping .NET MAUI, Mono remained the underlying runtime for mobile and other non-desktop platforms.
Mono’s Broader Ecosystem
Mono’s influence extends far beyond Microsoft’s own products. Unity built its entire scripting runtime on Mono, powering one of the world’s most popular game engines — and it too has started transitioning to CoreCLR. Cross-platform UI frameworks such as Avalonia and Uno Platform leverage Mono on WebAssembly to deliver apps in the browser and on mobile. MonoGame carries forward the XNA legacy for .NET game development across every platform, and Godot uses a C# scripting backend powered by Mono. This vast ecosystem traces back to the same foundation: Mono proved that .NET could run anywhere.
Now, CoreCLR becoming the default for .NET MAUI is the next chapter of that story — not its ending. Mono’s pioneering work made this unification possible.
What Changed in .NET 11
When you build a .NET MAUI app targeting .NET 11, CoreCLR is now the default runtime for both Release and Debug builds on Android, iOS, and Mac Catalyst. This isn’t entirely new ground: Microsoft had already added CoreCLR support for Windows, Linux, macOS (AppKit), and some Android scenarios. What’s new is that the last MAUI platforms still running on Mono — namely Android, iOS, and Mac Catalyst — now default to CoreCLR.
A few important clarifications:
- This change applies to Android, iOS, Mac Catalyst, and tvOS. All of these platforms move to CoreCLR.
- Blazor WebAssembly is not affected. WASM continues to use the Mono runtime and that is not changing in .NET 11.
- During the transition period, you can opt back to Mono if you encounter issues.
For a deeper dive into runtime and compilation details, see the official Runtimes and Compilation documentation (internal reference).
Why CoreCLR? The Benefits of a Unified Runtime
The decision to unify .NET MAUI under CoreCLR was driven by three key factors:
Runtime Unification
Until now, mobile apps ran on Mono while server, desktop, and cloud workloads used CoreCLR. This split meant different JIT behavior, different garbage collection (GC) characteristics, different diagnostics tooling, and different bug surfaces. With CoreCLR across all platforms, your mobile app now runs on the same runtime as your backend. One runtime, one set of tools — consistency from client to cloud.
Performance and Diagnostics
CoreCLR brings years of performance optimizations to the mobile space. The same modern JIT and tunable GC that power high-scale Azure services now work in your pocket. Diagnostic tools like dotnet-counters, dotnet-dump, and dotnet-trace all work uniformly, making it easier to profile and debug mobile applications without learning platform-specific quirks.
Future-Proofing the Ecosystem
Unifying on CoreCLR aligns .NET MAUI with the rest of the .NET ecosystem. As Microsoft invests in performance, security, and new features for CoreCLR, mobile apps benefit immediately. The open-source community can contribute to one runtime instead of supporting two diverging codebases. This change also mirrors what many in the ecosystem (like Unity) are already doing, smoothing the path for cross-platform collaboration.
Conclusion
Mono enabled .NET to go places it was never meant to go. Now, CoreCLR’s adoption in .NET MAUI represents the natural evolution of that vision: a single, powerful runtime that spans mobile, desktop, web, and cloud. Starting with .NET 11 Preview 4, developers can build MAUI apps with the confidence that they’re using the same tried-and-tested engine that runs millions of production workloads worldwide.