Understanding .NET MAUI's Shift to CoreCLR in .NET 11

The transition of .NET MAUI from Mono to CoreCLR marks a significant milestone for mobile development. Starting with .NET 11 Preview 4, CoreCLR becomes the default runtime for .NET MAUI apps on Android, iOS, Mac Catalyst, and tvOS. This change unifies the runtime across all .NET workloads—from mobile to cloud—bringing consistent performance, tooling, and debugging. Below, we answer key questions about this shift, its history, and what it means for developers.

What exactly is changing in .NET MAUI with .NET 11?

Starting in .NET 11 Preview 4, the default runtime for .NET MAUI applications on Android, iOS, Mac Catalyst, and tvOS shifts from Mono to CoreCLR. This applies to both Release and Debug builds. Previously, only Windows, Linux, and macOS (AppKit) ran on CoreCLR; mobile and tvOS platforms were still using Mono. Now your mobile apps run on the same runtime that powers ASP.NET Core, Azure services, and millions of desktop applications—providing unified JIT behavior, garbage collection, and diagnostic tooling. You can still opt back to Mono during this transition period if you encounter any issues.

Why is Microsoft moving MAUI to CoreCLR?

The primary motivation is runtime unification. Until now, .NET mobile apps ran on Mono while server, desktop, and cloud workloads used CoreCLR. This split created inconsistencies: different JIT compilers, distinct garbage collector characteristics, varied diagnostic tooling, and divergent bug surfaces. By moving MAUI to CoreCLR, every .NET application—whether mobile, web, or backend—shares one runtime. This means simpler development, consistent behavior across platforms, and a single set of tools for monitoring and debugging. It also eliminates the need to maintain two separate runtime codebases, reducing complexity for Microsoft and improving performance for developers.

How did Mono enable .NET on mobile in the first place?

Mono has been the backbone of .NET on non-Windows platforms for over 15 years. It started in 2001 when Miguel de Icaza aimed to bring .NET to Linux. From there, it expanded: MonoTouch (2009) brought C# to the iPhone, MonoDroid extended it to Android, and Xamarin turned these experiments into a production-grade platform. When Microsoft acquired Xamarin in 2016, Mono became the runtime for what evolved into .NET MAUI. But Mono’s influence reaches far beyond Microsoft—Unity built its entire scripting engine on it, powering millions of games; Avalonia and Uno Platform use it for cross-platform apps on WebAssembly and mobile; MonoGame continues the XNA legacy; and Godot uses Mono for its C# scripting. This vast ecosystem traces back to Mono’s success in taking .NET wherever it needed to go.

Which platforms are affected by the move to CoreCLR?

All .NET MAUI target platforms that were previously on Mono are now moving to CoreCLR: Android, iOS, Mac Catalyst, and tvOS. Windows and macOS (AppKit) were already on CoreCLR, so no change there. One important exception: Blazor WebAssembly continues to use Mono and is not affected by this change in .NET 11. For developers working on mobile, tablet, or Apple TV apps with .NET MAUI, your builds will now default to CoreCLR.

Can developers opt back to Mono if they face issues?

Yes. During the transition period—starting with .NET 11 Preview 4—Microsoft provides a way to revert to Mono if your app encounters problems with CoreCLR. This is intended as a safety net to ensure you can continue shipping while working through any compatibility issues. To opt back, you would set a specific build flag or property in your project file. This fallback is temporary; once CoreCLR is fully validated for all scenarios, the option may be removed. Microsoft recommends testing your MAUI apps early in the preview cycle to identify and report any regressions, helping improve the runtime for everyone.

What parts of the .NET ecosystem remain on Mono?

While .NET MAUI mobile targets move to CoreCLR, several other scenarios still rely on Mono. The most notable is Blazor WebAssembly, which runs interpreted .NET code in the browser—Mono remains the runtime for that workload in .NET 11 and is not changing. Additionally, legacy Xamarin.Forms projects (if still maintained) continue to use Mono. However, any new .NET MAUI app targeting Android, iOS, Mac Catalyst, or tvOS will default to CoreCLR. The Mono runtime will continue to be supported for these remaining use cases, but its role is now specialized rather than the default for mobile.

What should .NET MAUI developers do to prepare for this change?

First, ensure you are using .NET 11 Preview 4 or later. Then rebuild your existing MAUI apps and test them thoroughly on all target platforms—especially Android, iOS, and tvOS. Pay attention to performance benchmarks, garbage collection behavior, and native interop code (P/Invoke, bindings). While CoreCLR is largely compatible, subtle differences in JIT, GC, or diagnostic APIs may surface. Take advantage of the opt-back mechanism if you hit blockers, but report issues to Microsoft so they can be resolved before the final release. Also, review the official Runtimes and compilation documentation for detailed guidance on compilation modes and runtime options.