3 ms·
It seems like these cross-platform solutions always sound good on paper but end up not being so great in real life. To anyone who’s used this already: is it be
by cmer 4y ago
It seems like these cross-platform solutions always sound good on paper but end up not being so great in real life.
To anyone who’s used this already: is it better than say Xamarin?
- sdflhasjd 4y agoIt's basically thr successor to Xamarin Forms - the same technology and concepts updated to .net 6 instead of Mono. It's still Xaml, still MVVM, still an abstraction on top of native components. It's only really different in they're supporting more platforms, updating to more modern .net (.net's IServiceProvider instead of Xamarin's DependencyService for DI), and there's some improvements to how the platform specific UI control adapters can be extended. As for whether it's better? The tooling is greatly improved and it eases some of the pain when writing "renderers". We were finding occasional bugs up until recently, and migrating is somewhat involved as you lose a lot of the old Xamarin package ecosystem.
- memsom 4y agoI’m looking at a Xamarin Forms app I develop commercially as I type this. It targets Android, but could have supported iOS and Windows from the same code base. Most of our non UI code is shared with WPF and Web apps. All of the UI uses Xamarin Forms and SkiaSharp to render custom UI elements. It will be ported to Maui this year and we will be making a Windows, iOS and possibly Mac version.