AvaloniaUI has previewed support for .NET MAUI on Linux and WebAssembly using .NET 11. This update extends cross-platform capabilities beyond the reach of Microsofts own framework. Developers can now add Linux and WebAssembly targets to their graphical user interface applications. The initiative aims to fill gaps where the official Microsoft stack currently lacks coverage.
The new backend enables the use of Avalonia controls alongside or in place of standard MAUI controls. This integration is significant because cross-platform frameworks handle rendering in fundamentally different ways. Some systems call native platform APIs to display buttons and switches, while others use custom drawing for consistency. MAUI relies on native APIs whereas Avalonia employs custom drawing methods to maintain uniformity across operating systems.
Steven Kirk created Avalonia in 2013 when Windows Presentation Foundation appeared abandoned by the industry. The framework offered an actively developed environment for developers possessing WPF skills and legacy applications. Community interest has since made it one of the most active projects within the .NET open source ecosystem. It currently targets iOS, Android, WebAssembly, macOS, and Windows for deployment.
According to software engineer Tim Miller, there are still many areas to address within the codebase. These include a version of the Microsoft MAUI APIs for essential platform features such as storage and media access. The team acknowledged that the implementation is not yet production-ready for all scenarios. Developers should expect persistent bugs that may constrain early enterprise adoption rates.
A critical limitation involves the Linux display system architecture within the current preview. The implementation does not yet support Wayland, the modern display system for Linux distributions. Users must rely on X11 or the XWayland compatibility layer to render graphics correctly. This restriction limits the utility of the framework for modern Linux environments requiring Wayland support.
Broader industry context suggests MAUI struggles with significant adoption despite Microsofts backing. Cross-platform applications like Microsoft Teams utilize TypeScript and the Electron framework rather than MAUI. React Native also remains popular within Microsoft Office and other proprietary products. This internal usage pattern raises questions about the frameworks long-term viability among engineers.
Developer feedback regarding the transition from .NET nine to .NET 10 indicates significant instability issues. One respondent noted that the first quarter of 2026 was a time of constant regressions and other bugs. Another developer stated they reverted back to .NET nine after numerous fixes failed to resolve Android and iOS issues. These reports highlight the moving target nature of cross-platform development against frequent mobile OS updates.
The project has brought direct benefits to Avalonia itself through the creation of new controls. These additions for the forthcoming Avalonia 12 close the gap between the control set available in .NET MAUI. However, it is not yet possible to host Avalonia controls within WinUI when running on Windows. This limitation restricts the full integration potential within the Windows ecosystem for now.
Microsoft C# and .NET remain popular for web applications but face hurdles for cross-platform GUI development. The moving target of mobile operating system updates creates a complex environment for framework maintainers. Stability remains the primary concern for developers transitioning legacy .NET applications to modern cross-platform standards.
Avalonia MAUI will remain in preview until .NET 11 reaches general availability in November. Uptake will likely depend on whether the team can resolve the reported stability issues. The broader implications for .NET ecosystem flexibility remain uncertain without broader industry traction.
