Avalonia’s Bold Play: Giving .NET MAUI Apps a Second Life Across Every Desktop Platform

="">

A small but ambitious open-source company just made a move that could reshape how enterprise developers think about cross-platform .NET applications. Avalonia UI, the company behind the popular open-source UI framework of the same name, has released a preview tool that lets developers take existing .NET MAUI applications and run them on platforms Microsoft never intended to support — Linux, macOS without the Mac App Store, and even embedded systems.

The product is called Avalonia.MAUI, and its first preview dropped on July 10, 2025. The pitch is straightforward: write your app in MAUI, Microsoft’s official cross-platform UI framework, and then deploy it to any platform Avalonia supports. No rewrite. No second codebase. Just a compatibility layer that translates MAUI controls into Avalonia’s rendering engine.

That’s a big promise. And if it works as advertised, it addresses one of the most persistent frustrations in the .NET development community.

Microsoft’s MAUI Gap — and Who’s Filling It

When Microsoft launched .NET MAUI (Multi-platform App UI) as the successor to Xamarin.Forms, it positioned the framework as the answer for developers who wanted to build apps for iOS, Android, macOS, and Windows from a single C# codebase. But there was a conspicuous absence. Linux. The world’s most popular server operating system, and an increasingly common desktop choice in enterprise environments, government agencies, and developing markets, was left out entirely.

Microsoft had its reasons — or at least its priorities. MAUI targets platforms where Microsoft has commercial relationships and where its developer tooling (Visual Studio, Azure DevOps) has the deepest integration. Linux desktop, from Redmond’s perspective, apparently didn’t make the cut.

This created a real problem for organizations running mixed environments. A hospital system with Linux workstations. A manufacturing floor running embedded Linux on its terminals. A European government agency mandating open-source operating systems. For these customers, MAUI was a non-starter — unless they were willing to maintain separate codebases or abandon the framework altogether.

Avalonia UI has been quietly building toward this moment for years. The framework, which draws heavy inspiration from WPF (Windows Presentation Foundation), already runs on Windows, macOS, Linux, iOS, Android, WebAssembly, and even embedded devices via framebuffer rendering. It’s been gaining traction among .NET developers who need true cross-platform reach, particularly in industrial, financial, and scientific applications. According to the Avalonia UI blog post announcing the preview, the company saw an opportunity to bridge the gap rather than compete head-on.

“We’re not asking developers to choose between MAUI and Avalonia,” the announcement states. “We’re giving them a way to use both.”

The technical approach is layered. Avalonia.MAUI implements MAUI’s handler architecture — the abstraction layer that maps logical controls to platform-specific renderers — using Avalonia’s own rendering pipeline. When a MAUI app requests a Button, a ListView, or a NavigationPage, Avalonia.MAUI intercepts that request and draws the control using Avalonia’s Skia-based rendering engine instead of the native platform controls that MAUI would normally use on iOS or Android.

This means the visual appearance of controls will match Avalonia’s styling rather than native platform conventions. That’s a trade-off. Apps won’t look pixel-identical to their MAUI counterparts on iOS or Android. But they will look consistent across every platform Avalonia supports — a property many enterprise developers actually prefer.

The preview supports a significant subset of MAUI’s control library. Basic layouts, buttons, labels, entry fields, list views, navigation patterns, and shell-based apps all work. More complex controls — maps, WebView, platform-specific integrations — are not yet supported. The Avalonia team has been transparent about these limitations, publishing a compatibility matrix alongside the release.

Getting started requires minimal code changes. Developers add the Avalonia.MAUI NuGet package, swap out the MAUI app builder configuration, and run. The Avalonia blog post includes a step-by-step walkthrough showing the process takes roughly five minutes for a basic application.

Five minutes. That’s the kind of migration story that gets enterprise architects’ attention.

The Competitive and Strategic Calculus

Avalonia’s move is strategically shrewd for several reasons. First, it dramatically expands the company’s addressable market. Instead of asking developers to learn a new framework from scratch, Avalonia is meeting them where they already are — inside MAUI — and offering an upgrade path. Developers who’ve invested months or years in MAUI applications can now extend those investments to new platforms without starting over.

Second, it positions Avalonia as complementary to Microsoft’s tooling rather than adversarial. This matters. The .NET community is tightly coupled to Microsoft’s direction, and frameworks that position themselves as replacements for Microsoft technologies often struggle with adoption. By framing Avalonia.MAUI as an extension of MAUI rather than an alternative, the company sidesteps the tribal loyalty that can kill open-source projects.

Third — and this is the part that should interest CTOs — it provides a hedge against Microsoft’s platform decisions. MAUI’s development pace has been a source of frustration in the .NET community. Bug fixes have been slow. Feature requests languish. The framework’s GitHub repository is littered with issues that have been open for years. If Microsoft decides to deprioritize MAUI (as it did with Xamarin, and before that, Silverlight, and before that, Windows Phone), organizations using Avalonia.MAUI have an escape route that doesn’t require a full rewrite.

That’s not hypothetical anxiety. It’s institutional memory. .NET developers have been burned before.

The timing of this release also coincides with broader industry trends. Linux desktop adoption continues to grow in enterprise settings, driven by cost, security, and regulatory considerations. The European Union’s push toward digital sovereignty has accelerated government adoption of Linux-based systems. And in embedded and industrial contexts — kiosks, medical devices, point-of-sale terminals — Linux has long been dominant.

Meanwhile, the cross-platform UI space is getting more competitive. Flutter, backed by Google, continues to gain ground. Kotlin Multiplatform is maturing. React Native remains entrenched in the JavaScript world. For .NET developers who want to stay in C# and XAML, the realistic options have been MAUI (with its platform limitations) or Avalonia (with its smaller community and different API surface). Avalonia.MAUI collapses that choice into a both/and proposition.

There are risks, of course. Compatibility layers introduce complexity. Performance characteristics may differ from native MAUI rendering. And maintaining parity with MAUI’s evolving API surface is a moving target — one that depends on Microsoft’s release cadence and willingness to keep MAUI’s handler architecture stable.

The Avalonia team acknowledges this directly. The preview is explicitly labeled as not production-ready. The company is soliciting feedback from early adopters and plans to iterate quickly based on real-world usage patterns. A public GitHub repository tracks known issues and missing controls.

But the ambition is clear. And the execution, even at this early stage, suggests the team understands both the technical challenges and the market opportunity.

For enterprise development teams evaluating their cross-platform strategy, Avalonia.MAUI represents something genuinely useful: optionality. The ability to write in MAUI today, deploy to Microsoft’s supported platforms immediately, and extend to Linux and embedded targets when the business requires it — without maintaining two separate UI frameworks or rewriting application logic.

That’s not a theoretical benefit. That’s a line item on a project budget.

What Comes Next

The Avalonia team has outlined an aggressive roadmap. Preview 2 is expected to expand control coverage significantly, with particular focus on CollectionView, WebView, and platform-specific APIs that many production apps depend on. The company is also working on tooling integration — ensuring that Visual Studio and JetBrains Rider provide first-class development experiences for Avalonia.MAUI projects.

Longer term, the company has hinted at commercial support tiers for enterprises that need SLAs and dedicated engineering assistance. Avalonia already offers a commercial product called Avalonia XPF, which provides a compatibility layer for WPF applications. Avalonia.MAUI follows the same strategic playbook: build an open-source bridge, then monetize through enterprise support and tooling.

It’s a proven model. And in a market where .NET developers are hungry for cross-platform solutions that actually work, the demand side of the equation looks favorable.

Whether Avalonia.MAUI becomes a standard part of the .NET developer’s toolkit depends on execution over the next six to twelve months. The preview is promising. The architecture is sound. The market need is real. Now comes the hard part — shipping production-quality software and convincing enterprise buyers that a small open-source company can deliver what Microsoft chose not to.

The .NET community will be watching closely. So will Microsoft.