2 ms·
It'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 abstr
by sdflhasjd 5y ago
It'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.