Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

.NET MAUI review

.NET MAUI suits C# teams that want shared native mobile and desktop code.

7.1/10Editor score
.NET MAUI7.1 Visit .NET MAUI

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

.NET Multi-platform App UI (.NET MAUI) is an open-source framework for building native mobile and desktop applications from a shared .NET codebase. It is aimed at small, mid-market, and enterprise teams that want to target Android, iOS, macOS through Mac Catalyst, and Windows while working primarily in C# and XAML. The framework uses an MIT license and supports desktop and mobile deployment, with additional Tizen support provided by Samsung.

Its ecosystem fit is a central strength. .NET MAUI connects with Visual Studio and Visual Studio Code, uses the broader .NET platform, and supports Blazor through .NET MAUI Blazor. A unified project system helps organize shared code, while native controls and platform-specific APIs let applications follow each target platform’s capabilities. That combination makes it suitable for teams already invested in Microsoft development tools or maintaining related .NET and Blazor components.

The framework’s breadth is useful when one codebase must serve both mobile and desktop, but that scope also brings platform considerations. Teams still need to account for differences among Android, iOS, macOS, Windows, and potentially Tizen when using platform-specific APIs or controls. Its shared model is most natural for developers comfortable with C# and XAML; teams centered on other languages or a single platform may prefer a narrower framework. Choose .NET MAUI for native cross-platform applications with substantial shared .NET code, and look elsewhere when a project does not fit that ecosystem or needs a different language model.

.NET MAUI pros and cons

  • Where it wins
    • Shares C# and XAML across Android, iOS, macOS, and Windows
    • Provides native controls and platform-specific APIs
    • Integrates with Visual Studio, .NET, Visual Studio Code, and Blazor
  • Where it doesn't
    • Requires C# and XAML for its shared development model
    • Platform-specific APIs still require platform-aware implementation
    • Support is centered on documentation and community channels

.NET MAUI fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update