Unifying .NET: Why .NET MAUI's Shift to CoreCLR in .NET 11 Matters

Introduction

Starting with .NET 11 Preview 4, .NET MAUI applications on Android, iOS, and Mac Catalyst now run on CoreCLR by default. This marks a significant milestone: mobile apps share the same runtime as ASP.NET Core, Azure services, and countless production workloads. The move unifies the .NET ecosystem and signals the next chapter in a long journey that began with the Mono project over two decades ago.

The Legacy of Mono: Enabling .NET Everywhere

For more than fifteen years, Mono served as the runtime that took .NET to places it was never designed to go. Miguel de Icaza launched the Mono project in 2001 with the ambition to bring .NET to Linux. What followed was an unexpected expansion:

• MonoTouch (2009) brought C# to the iPhone.
• MonoDroid extended .NET to Android.
• Xamarin turned these experiments into a production-grade platform used by millions of developers.

When Microsoft acquired Xamarin in 2016 and started building .NET MAUI, Mono remained the runtime underneath it all. But Mono's impact goes far beyond Microsoft's own products. Unity built its scripting engine on Mono, powering millions of games. Avalonia and Uno Platform use Mono on WebAssembly. MonoGame keeps the XNA legacy alive. Mono didn't just enable mobile—it proved that .NET could run anywhere. CoreCLR becoming the default for .NET MAUI is the next chapter, not the end of that story.

What's Changing 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 (including tvOS). This is not an entirely new direction: CoreCLR already supported Windows, Linux, macOS (AppKit), and Android. The key change in .NET 11 is extending the same unified runtime to the remaining mobile platforms that were still on Mono.

Important Clarifications

• This applies to Android, iOS, Mac Catalyst, and tvOS.
• Blazor WebAssembly is not affected—it continues to use Mono in .NET 11.
• Developers can opt back to Mono if issues arise during the transition period.

For deeper technical details, see the official runtimes and compilation documentation.

Why CoreCLR? The Driving Factors

Three main reasons drove this change:

Runtime Unification

Until now, .NET mobile apps ran on Mono while server, desktop, and cloud workloads used CoreCLR. This split led to differences in JIT behavior, garbage collection characteristics, diagnostic tooling, and bug surfaces. With CoreCLR across all platforms, mobile apps now run on the same runtime as your backend—one runtime, one set of tools, one ecosystem.

Performance and Innovation

CoreCLR has received years of optimization for modern hardware and workloads. By moving mobile to CoreCLR, .NET MAUI apps benefit from continuous performance improvements, better memory management, and access to advanced diagnostic capabilities like dotnet counters and EventPipe.

Simplified Development and Maintenance

Having a single runtime reduces complexity for the .NET team and for developers. Bug fixes, performance patches, and features flow to all platforms simultaneously. This consistency simplifies cross-platform development and testing.

Impact and Transition Guidance

For most existing .NET MAUI applications, the switch to CoreCLR should be transparent. However, developers relying on Mono-specific behaviors or obscure APIs may encounter minor differences. The team recommends thorough testing on Preview builds and provides an opt-out mechanism to fall back to Mono if needed. In the long term, the unification will streamline your development experience and ensure your mobile apps stay aligned with the broader .NET ecosystem.

Conclusion

Mono's legacy is profound—it brought .NET to mobile, WebAssembly, and games. But the future lies in a single, high-performance runtime. By making CoreCLR the default for .NET MAUI, Microsoft is delivering on the promise of a truly unified .NET platform. Whether you're building a mobile app or a cloud service, you'll benefit from the same runtime, the same tools, and the same continuously improving foundation.

Start exploring .NET 11 Preview 4 today to experience the change firsthand.

Compilation Documentation

This is an anchor target for internal linking. For official docs, refer to Microsoft's documentation on runtimes and compilation.