.NET MAUI lets you ship native mobile and desktop apps from a single shared project. Write UI in XAML or C#, run it on Android, iOS, macOS (via Mac Catalyst), and Windows, then brag that you didn’t copy-paste from Xamarin days.
Multi-targeting wraps Android, iOS, Mac Catalyst, and Windows into one SDK-style project. Shared resources, one app manifest, one entry point. Drop in platform folders only when you absolutely must touch a status bar.
MAUI sits atop the unified .NET runtime, so your business logic, tests, and dependency injection run the same from Pixel to Surface. No more juggling .NET Framework ghosts or Xamarin support tables.
Compose interfaces with XAML, code-only C#, or mix both. Build handlers if you want to poke the native renderers, or stay high-level with layouts that translate to the matching platform controls.
Change markup, hit save, watch simulators update without restarting. Hot reload works across platforms, so you can tweak your Grid padding while the iOS sim and Windows window clap politely.
Essentials APIs expose sensors, GPS, clipboard, biometrics, secure storage, and more with a single call. Want platform-specific flair? Use partial classes or conditional compilation without spiral-bound documentation.
Bundle the runtime and your bits into one self-contained package, toss it on a device, and run with dotnet run app.
It’s like bundling Electron, except smaller, native, and not 300 MB of Chromium.
Xamarin.Forms fans will feel at home, but MAUI rebuilt the control stack for performance and gave you desktop power-ups. Shell navigation, handlers, graphics, and the single project system mean less csproj spelunking.
Publish Android APK/AAB, iOS IPA via Xcode, Windows MSIX, or Mac .app with one solution. CI/CD it with dotnet publish
and act smug when your JavaScript friends ask how you got native notifications working.