.NET 11 Sets CoreCLR as Default Runtime for MAUI Mobile Apps, Ending Mono Era

Breaking: Microsoft has announced that starting with .NET 11 Preview 4, CoreCLR is now the default runtime for .NET MAUI applications on Android, iOS, and Mac Catalyst. This ends a 15-year era where the Mono runtime powered .NET on mobile devices.

Developers will now see their mobile apps run on the same high-performance runtime that already powers ASP.NET Core, Azure, and millions of production servers worldwide. The change applies to both Release and Debug builds for all MAUI target platforms including tvOS.

According to a Microsoft spokesperson, “This unification simplifies the runtime stack and improves performance, diagnostics, and tooling consistency across all .NET workloads.” The company expects full parity and improved startup times in production scenarios.

Background: The Rise and Transition of Mono

For over 15 years, the Mono project—started by Miguel de Icaza in 2001—brought .NET to platforms Microsoft never originally targeted. It began as an effort to run .NET on Linux, then expanded to mobile with MonoTouch (iPhone, 2009) and MonoDroid (Android, 2010). Xamarin commercialized these runtimes, and after Microsoft’s acquisition in 2016, Mono became the foundation for .NET MAUI.

Mono’s influence extends far beyond Microsoft. Unity, the world’s most popular game engine, built its scripting system on Mono. Avalonia, Uno Platform, and MonoGame also depend on Mono for cross-platform .NET apps. Godot uses Mono for its C# backend. “Mono didn’t just enable .NET on mobile—it proved .NET could run anywhere,” said a former Xamarin engineer familiar with the transition.

Now, with CoreCLR taking over the mobile runtime in .NET 11, Mono’s role is shifting. However, Mono remains the runtime for Blazor WebAssembly in .NET 11, and developers can opt back to Mono during the transition if needed.

What This Means for Developers

CoreCLR unification means mobile apps now share the same garbage collector, just-in-time compiler, and debugging infrastructure as cloud and desktop apps. This reduces surface bugs and simplifies tooling. “One runtime, one set of tools—that’s a huge win for mobile developers who also build server-side,” said a Microsoft program manager.

The change also opens the door to future performance improvements and more consistent behavior across platforms. Developers of large MAUI apps may notice faster startup and better memory handling. However, legacy Mono-specific optimizations may need re-evaluation.

Microsoft has provided opt-back capability for those encountering issues, but the company urges migration to CoreCLR. The full documentation is available in the .NET runtime repository.

Why CoreCLR Now?

Three major factors drove the decision: runtime unification, better performance, and reduced fragmentation. Until now, .NET mobile ran on Mono while everything else used CoreCLR. This split meant different JIT behavior, garbage collection patterns, and diagnostic tooling. With CoreCLR across all platforms, Microsoft can deliver a single, optimized runtime that benefits every .NET application.

The transition has been incremental. CoreCLR already supported Android, iOS (via Mac Catalyst), and macOS (AppKit) in previous previews. .NET 11 completes the picture by making it the default for MAUI mobile targets.

Next Steps

Developers should test their .NET MAUI apps with .NET 11 Preview 4 or later. For those facing issues, the transition guide includes steps to revert to Mono. Microsoft expects the migration to be mostly seamless, though some platform-specific code may require adjustments.

“This is the next chapter of the Mono story, not its end,” the company stated. “We thank the Mono community for 15 years of enabling .NET on every device.”