<p>AvaloniaUI has released a preview backend that lets .NET MAUI applications run on Linux and WebAssembly without changing application code. Microsoft’s own MAUI framework doesn’t cover either platform, so this fills a real gap — though it comes with caveats worth understanding before you get excited.</p>
<h2>How it works</h2>
<p>The backend maps MAUI’s control abstractions to Avalonia’s own controls, which are drawn via Skia rather than native platform APIs. That distinction matters: you’re not getting native Linux widgets, you’re getting Skia-rendered controls that look and behave consistently across platforms. Most core MAUI controls are supported, including layouts, CollectionView, Shell, gestures, animations, and graphics (including SkiaSharp).</p>
<p>Integration is straightforward — add the NuGet packages and call <code>UseAvalonia()</code> in your app setup. The All-in-One .NET MAUI Templates Pack (v9.0+) has also been updated to support it, with a <code>--avalonia</code> flag for CLI and Visual Studio project creation, plus new Linux and Wasm target options.</p>
<p>Several real-world MAUI apps have already been ported to Linux successfully, which is a decent sign for early-stage software.</p>
<h2>What’s missing</h2>
<p>This is a preview, and the gaps are real:</p>
<ul>
<li>CarouselView isn’t implemented yet</li>
<li>Most MAUI Essentials APIs (storage, media, etc.) are missing</li>
<li>No Wayland support — only X11/XWayland</li>
<li>PushModal navigation is broken on WebAssembly</li>
<li>Hybrid app support for Drawn UI isn’t available</li>
<li>Avalonia controls can’t be hosted inside WinUI on Windows</li>
</ul>
<h2>The .NET 11 dependency</h2>
<p>The backend requires .NET 11, which is itself in preview. General availability won’t come until November, so this isn’t something you’d ship to production today.</p>
<h2>The broader context</h2>
<p>It’s worth being honest about where MAUI stands. Adoption has been slow, bugs persist across releases, and there are regressions between .NET versions. Microsoft itself uses Electron and React Native for its own cross-platform apps rather than MAUI, which tells you something about internal confidence in the framework.</p>
<p>Avalonia’s approach here is interesting precisely because it sidesteps MAUI’s native-control model entirely. Whether that’s a feature or a limitation depends on what you’re building — consistent cross-platform rendering is genuinely useful for some apps, but you lose platform-native feel in the process.</p>
<p>The project is open source and actively iterating. If you’re already invested in a MAUI codebase and need Linux or WebAssembly support, this is worth watching closely as .NET 11 approaches release.</p>


Collections

AvaloniaUI has released a preview backend that enables .NET MAUI applications to run on Linux and WebAssembly without code changes, filling a gap left by Microsoft's own MAUI framework. The backend maps MAUI controls to Avalonia's Skia-rendered equivalents, meaning you get consistent cross-platform rendering rather than native platform widgets. Integration requires adding NuGet packages and calling UseAvalonia() in app setup. Notable limitations include missing CarouselView, most MAUI Essentials APIs, no Wayland support (X11/XWayland only), broken PushModal navigation on WebAssembly, and a dependency on .NET 11 (still in preview, GA in November). MAUI's broader adoption challenges are also noted, with Microsoft itself favoring Electron and React Native for its own cross-platform apps.

Avalonia adds Linux and WebAssembly support to .NET MAUI