3 ms·
Crossplatform will never be "right", always a compromise. I'd consider if you truly need to be crossplatform or not. If I need it, I'd go with a webapp, prefer
by BuckRogers 6y ago
Crossplatform will never be "right", always a compromise. I'd consider if you truly need to be crossplatform or not.
If I need it, I'd go with a webapp, preferably Blazor for wasm. For native, I'd want to use one of my preferred platforms. Windows10 for desktop, iOS for mobile.
I'd work my way down, starting with what I'd prefer to work with most.
1. Blazor WebAssembly (webapp)
2. Blazor Server (webapp)
4. WinUI/UWP (native)
3. ASP.NET MVC (webapp)
5. iOS (native)
- BuckRogers 6y agoMy post is referring to today. It's worth adding that for the future, .NET MAUI[0] may be what people are looking for. It's an evolution and expansion of Xamarin.Forms. I'd have a hard time believing you will be able to do better for a native, crossplatform GUI than .NET MAUI when it's ready. [0]https://devblogs.microsoft.com/dotnet/introducing-net-multi-platform-app-ui/ https://devblogs.microsoft.com/dotnet/introducing-net-multi-...