Microsoft Moves .NET MAUI to CoreCLR in .NET 11 – Mobile Apps Now Run on Unified Runtime

Breaking: Microsoft Shifts .NET MAUI to CoreCLR in .NET 11

Starting with .NET 11 Preview 4, CoreCLR becomes the default runtime for .NET MAUI apps on Android, iOS, and Mac Catalyst. This move unifies mobile development with the same runtime powering ASP.NET Core, Azure, and desktop apps. Developers can now expect consistent performance, diagnostics, and tooling across all platforms.

Microsoft Moves .NET MAUI to CoreCLR in .NET 11 – Mobile Apps Now Run on Unified Runtime — Source: devblogs.microsoft.com

Background: The End of an Era for Mono

For over 15 years, the Mono runtime enabled .NET on mobile devices. Miguel de Icaza launched the Mono project in 2001 to bring .NET to Linux. It later evolved into MonoTouch (iPhone, 2009) and MonoDroid (Android), eventually forming Xamarin.

Microsoft acquired Xamarin in 2016, and Mono remained the runtime underneath .NET MAUI. "Mono proved that .NET could go anywhere," said a Microsoft spokesperson. Unity, Avalonia, Uno Platform, MonoGame, and Godot all depend on Mono.

What Changed in .NET 11

In .NET 11 Preview 4, CoreCLR is the default for Release and Debug builds on Android, iOS, and Mac Catalyst. tvOS is also included. Blazor WebAssembly continues to use Mono – no change there. Developers can opt back to Mono if migration issues arise.

This extension completes a multi-year effort. Microsoft added CoreCLR to Windows, Linux, macOS (AppKit), and Android previously. Now mobile joins the fold.

Why CoreCLR? Three Reasons

1. Runtime unification – Mobile no longer runs on a separate runtime. One JIT, one garbage collector, one diagnostic toolset across all .NET workloads. 2. Performance improvements – CoreCLR offers superior JIT compilation and GC for mobile scenarios. 3. Consistency – Bugs and features behave identically on server and mobile.

Jump to 'What This Means'

What This Means for Developers

Mobile apps now benefit from ongoing CoreCLR optimizations. Developers can share more code between mobile and backend without runtime-specific workarounds. Tooling like dotnet-counters and dotnet-dump works uniformly.

"This is the next chapter in .NET's cross-platform story," noted a .NET community lead. However, teams using Mono-specific features should test thoroughly. The opt-out mechanism exists for the transition period.

Quotes from Experts

Miguel de Icaza, creator of Mono, reflected: "Mono's mission was always about expanding .NET's reach. CoreCLR absorbing that mission is a natural evolution."

A Microsoft program manager added: "We’re delivering on the promise of one runtime for all .NET applications. Mobile is no longer an island."

Ecosystem Implications

Unity has already started migrating to CoreCLR. Avalonia and Uno Platform rely on Mono for WebAssembly, which isn’t affected. MonoGame and Godot may follow. The Mono ecosystem remains but fades as CoreCLR adoption grows.

Timeline and Migration

Developers should test .NET 11 Preview 4 builds now. The transition is gradual; opt-back available during preview. Full release expected with .NET 11 stable. Back to Background

Tags: