The Microsoft approach.
WHAT XAMARIN WAS
A framework building native mobile applications with C# and .NET.
WHAT .NET MAUI IS
Its successor, extending to desktop as well as mobile, with a unified project structure.
WHAT THEY PROVIDE
One language and ecosystem across platforms Native controls, not drawn ones Full access to platform APIs from C# Shared business logic with other .NET systems
WHAT THAT LAST POINT MAKES THEM SUIT
Organisations already invested in .NET, particularly for internal and business applications.
WHAT INTERFACE OPTIONS EXIST
Markup-defined interfaces, with data binding Code-defined interfaces Blazor-based interfaces, reusing web components
WHAT THE ECOSYSTEM IS LIKE
Smaller than the alternatives, with fewer third-party components and fewer developers.
WHAT TO WEIGH
Existing .NET investment and skills against ecosystem size and hiring.
WHAT TO CHECK
Support status and the migration path, since the platform has changed names and structure.
WHO IT SUITS
Enterprises with .NET teams and internal applications.
WHO IT SUITS LESS
Consumer products where the ecosystem matters more.
