.NET MAUI Finally Migrates to CoreCLR: Mobile Apps Now Share Runtime with Cloud and Desktop

Breaking: .NET MAUI Moves to CoreCLR in .NET 11

Starting with .NET 11 Preview 4, Microsoft has made CoreCLR the default runtime for .NET MAUI applications on Android, iOS, and Mac Catalyst. This means mobile apps will now run on the same powerful runtime that powers ASP.NET Core, Azure services, and countless desktop applications worldwide.

The shift marks the end of a long-standing split, where mobile development relied on the Mono runtime while server and desktop environments used CoreCLR. Developers can now expect unified performance, diagnostics, and tooling across all platforms.

Background

Mono, an open-source implementation of .NET, has been the backbone of mobile .NET development for over 15 years. Founded by Miguel de Icaza in 2001, Mono brought .NET to Linux and later to iPhones via MonoTouch in 2009, and to Android with MonoDroid. Xamarin, acquired by Microsoft in 2016, packaged these efforts into a platform used by millions.

Beyond Microsoft, Mono powers Unity’s scripting engine, Avalonia, Uno Platform, MonoGame, and Godot’s C# support. “Mono didn’t just enable .NET on mobile. It proved that .NET could go anywhere,” said a Microsoft spokesperson. “CoreCLR becoming the default for .NET MAUI is the next chapter of that story, not its ending.”

What Changed in .NET 11

When building a .NET MAUI app targeting .NET 11, CoreCLR is now the default runtime for Release and Debug builds on Android, iOS, Mac Catalyst, and tvOS. This applies to all these platforms—effectively the last holdouts still using Mono.

Blazor WebAssembly is explicitly excluded; it will continue to use Mono and remains unchanged in .NET 11. If developers encounter issues during the transition, they can opt back to Mono temporarily.

• Key platforms affected: Android, iOS, Mac Catalyst, tvOS.
• Not affected: Blazor WebAssembly.
• Opt-out available during the transition period.

For detailed technical guidance, see the Runtimes and compilation documentation.

Why CoreCLR?

Three primary reasons drove the change, according to Microsoft. First, runtime unification: mobile, server, desktop, and cloud now share one runtime, eliminating differences in JIT behavior, garbage collection, and diagnostic tooling. Second, performance improvements—CoreCLR brings years of optimization from the cloud and desktop environments. Third, ecosystem simplification for developers who no longer need to juggle two separate runtimes.

What This Means

For developers, this is a major simplification. The same runtime that handles millions of Azure workloads now powers your mobile app. This means better performance, lower memory usage, and access to the latest .NET features that were previously unavailable on Mono.

Unity and other engine developers are also watching closely. Unity has already begun its own transition to CoreCLR, which could further unify the gaming ecosystem. The move signals that Microsoft is serious about making .NET a truly cross-platform, one-runtime-to-rule-them-all solution.

As the Mono era fades into history, its legacy remains. But starting today, the future of mobile .NET development runs on CoreCLR.