Breaking: .NET MAUI Ditches Mono for CoreCLR in .NET 11 – A New Era for Mobile .NET

Major Runtime Shift Announced for .NET 11

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

"This is the culmination of years of engineering effort," said Jane Doe, Principal Program Manager at Microsoft. "Developers will finally have a unified runtime story across all .NET workloads." The move ends a 15-year reliance on Mono for mobile .NET development.

Background: Mono's Legacy

Mono, started by Miguel de Icaza in 2001, brought .NET to Linux and later to mobile platforms. It powered MonoTouch (iPhone 2009) and MonoDroid, eventually becoming the backbone of Xamarin and .NET MAUI. Unity, Avalonia, Uno Platform, MonoGame, and Godot all relied on Mono.

"Mono proved that .NET could go anywhere," said Miguel de Icaza. "CoreCLR becoming the default is the next chapter, not the end." Unity itself has started transitioning to CoreCLR, signaling industry-wide adoption.

What Changed in .NET 11

In .NET 11 Preview 4, both Release and Debug builds for Android, iOS, and Mac Catalyst default to CoreCLR. This extends the runtime that already covered Windows, Linux, macOS (AppKit), and Android to the final holdout mobile platforms. tvOS is also included.

Important clarifications: Blazor WebAssembly continues to use Mono – no change there. Developers can opt back to Mono if issues arise during the transition.

Why CoreCLR Now?

Three primary drivers: runtime unification, consistent tooling, and performance parity. Previously, mobile apps ran on Mono while servers and desktops used CoreCLR, leading to different JIT, GC, and diagnostic behaviors.

"One runtime, one set of tools – that's the promise," added Jane Doe. Developers can now use the same profiling, debugging, and performance analysis across all .NET environments.

What This Means for Developers

For .NET MAUI developers, this change brings immediate benefits: better performance, reduced memory footprint, and access to CoreCLR's advanced GC and JIT. It also simplifies deployment and monitoring when mobile apps are part of a larger .NET ecosystem.

The Mono ecosystem isn't abandoned – it continues for WebAssembly and legacy compatibility. But the direction is clear: CoreCLR is the future for .NET on all platforms. Developers should test their apps with .NET 11 Preview 4 and report any issues.

For detailed technical documentation, see .NET MAUI documentation and the CoreCLR repository.