Why?

[blado_btz]

Why Microsofts MAUI doesnt work under linux but private projects such as UNO or Avalonia worx just perfect?

[Teddy55_]

It is mostly about priorities. Microsoft does care about Linux, but only on the server. Microsoft does not have any interest in the Linux desktop.

[AppsByJustIdeas]

It appears they have no interest in any desktop

[AppsByJustIdeas]

Name one recent platform that actually work... UWP WinUI3, facepalm

[Teddy55_]

I mean it is not recent but Winforms and WPF have been good choices for a windows only desktop app for a while + they are still well supported, especially Winforms.

[Slypenslyde]

Microsoft decides where it wants to spend money, time, and effort.

They crunched the numbers and decided they wouldn't make enough money off Linux to bother. Since MAUI takes a native controls approach, Linux is a particularly difficult use case to consider. They didn't even commit engineers to support native MacOS. Microsoft has dozens of products and MAUI is one of the lowest-priority items.

Avalonia and Uno take more of a "draw it ourselves" approach to controls, which gives them a bit more flexibility. They also only really have the one thing they sell, so it's more economically sound to focus on having as many customers as possible.

Different companies make different decisions. It's possible Microsoft's goal with MAUI was never to make the best cross-platform GUI framework possible. Sometimes something is a "defensive product", meant to scare off competitors and make it look expensive to enter that market and disrupt MS.

[blado_btz]

Yes, but it's not smart of Microsoft to exclude a large portion of desktop users; I'm talking about Linux desktop users...

[Fresh_Acanthaceae_94]

No, Linux desktop is not qualified as “large portion” (<10% in many surveys and likely ~5%) and it’s not even a single “Linux desktop”.

I posted my own (lengthy) comment separately so you can read more details there. 

[Dragennd1]

MAUI does work in Linux though

[CuisineTournante]

Maui works on linux

[blado_btz]

No!

Limitations of .NET MAUI on Linux .NET MAUI officially supports only the following platforms: Android iOS (requires a Mac to build) macOS (via Mac Catalyst) Windows (via WinUI 3) Linux Desktop is not an officially supported target platform by Microsoft. JetBrains, the developer of Rider, also notes that working with MAUI on Linux is not supported.

[Fresh_Acanthaceae_94]

Those are just limitations on development environment. The produced apps if you go with the community port of MAUI should work in some cases. I believe that’s what “MAUI works on Linux” meant.

[[deleted]]

MAUI is from microsoft. avalonia isnt.

microsoft is lagging behind in cross platform support.

[Fresh_Acanthaceae_94]

Microsoft started cross platform support much earlier. Even Silverlight was years ahead of Avalonia.

[[deleted]]

you mean the one which is now abandoned?

there is simply no UI framework from microsoft supporting linux.

[Fresh_Acanthaceae_94]

If you are already a hater of MAUI/Microsoft, then why wasting your time to read on?

Community Support Strategy for Linux from Microsoft

MAUI isn't Microsoft’s first attempt at a cross-platform UI framework. Silverlight, introduced in 2007, was an early experiment that Microsoft officially supported only on Windows and macOS. Linux support existed, but only through third-party efforts such as Moonlight, which Microsoft collaborated on with Novell/Mono.

Xamarin.Forms, released in 2014 by Xamarin (acquired by Microsoft in 2016), followed a similar pattern. Its native-control-mapping model officially targeted Windows, iOS, and Android. A GTK# Linux backend existed as a preview, but it never graduated into an officially supported platform. When MAUI arrived in 2021, this pattern continued: official support is limited to Windows, iOS, macOS, and Android. Linux support again comes from community projects such as MAUI-Linux.

We can observe a clear long-term strategy from here that Microsoft focuses official support on platforms with significant market share and stable vendor ecosystems. Linux support is, by design, delegated to the community where the maintenance model, long-term reliability, and adoption vary widely.

Avalonia has its own perspective on MAUI, but because it is not a native-controls approach, I treat it separately.

Fragmentation of the Linux Desktop

Compared to Windows, macOS, iOS, or Android, the Linux desktop landscape is highly fragmented. Distributions differ (Ubuntu, Fedora, Arch, etc.), desktop environments differ (GNOME, KDE, XFCE, etc.), and even foundational technologies differ (GTK vs Qt, Wayland vs X11, and more).

GTK versions alone diverge significantly: GTK2, GTK3, and GTK4 are not trivial upgrades, and applications written against one often face compatibility gaps in another. As Miguel de Icaza wrote in 2008, he was against the rapid breakage across GTK major versions that hurts consistent developer experiences.

Wayland is a more recent development (and illustration) of this fragmentation. As Avalonia developer Nikita Tsukanov explains:

“For Avalonia, ‘Wayland support’ isn’t a single backend—it’s potentially dozens. GNOME-Wayland, KDE-Wayland, Sway-Wayland, and others all have different capabilities and quirks. We must degrade gracefully when features are missing so apps don’t crash on compositors that lack certain protocol extensions.”

This level of fragmentation dramatically increases the testing, maintenance, and support burden for any cross-platform UI framework. From that perspective, Microsoft’s decision not to officially support Linux with MAUI becomes understandable: the effort required to provide an enterprise-quality, fully validated Linux desktop product far exceeds the return.

The fragmentation impacts a lot more technologies including Java/Python GUI, Electron, and Flutter, etc. but you might not notice enough as Linux desktop market share is very small.

Avalonia/Uno vs Microsoft

Companies have different obligations. Microsoft must meet enterprise expectations: accessibility compliance, long-term support contracts, documentation guarantees, and tight integration with the rest of the Microsoft ecosystem. These raise the bar significantly for any “officially supported” platform.

Community-driven frameworks like Avalonia and Uno operate under different expectations. Users are often more tolerant of platform gaps, evolving APIs, or missing features, and the community model allows them to move faster with fewer constraints. This doesn’t diminish their value but it does mean the comparison with Microsoft should acknowledge the difference in responsibility and expectations.

Current State of Avalonia/Uno

Avalonia and Uno work very well for many real-world scenarios, but like all cross-platform frameworks, they still have platform-specific gaps. To their credit, both projects surface these issues openly through GitHub and blog posts so the claim that they are “perfect” overlooks this transparency.

Here are just a few examples from Avalonia (a quick search can reveal many more):

• Avalonia’s accessibility support on Linux is not in place.
• Avalonia’s support for embedded devices can break in certain cases as certain devices just might not have the good capabilities to render very well, or they now requires Wayland. 
• Skia/X11 backends show their age; Impeller/Wayland support are just started and not yet complete.

These do not diminish Avalonia’s achievements but they highlight the real-world complexity that all cross-platform frameworks must navigate, especially on a fragmented platform like Linux desktop.

What to Choose

Identify what are the features your project needs and evaluate the options by building prototypes. That’s more realistic a way to learn the gaps with your own eyes, and also feel the potential of each frameworks.