Is anyone here using this in production and if so does it deliver a good developer and user experience?
Xamarin/Maui try to allow people to build cross-platform apps in a single codebase. Uno tries to allow people who are familiar with and/or prefer UWP to develop on other platforms than just windows.
with 34 comments
The approach is different where instead of creating an entirely new API, we aligned with WinUI's api (and UWP previously), making it source-code compatible with WinUI so you can leverage the WinUI's ecosytem (CommunityToolkit, 3rd party controls, ...).
By aligning with WinUI, you also get access to all the trained LLMs that already know about UWP/WinUI and therefore also work on Uno.
Uno sits on top of .NET for iOS/Android, aka Xamarin "Classic".
Single Project/Single Codebase with your choice of XAML or C# Markup, choice of Native or Skia-based rendering, works with VS/Code/Rider on Windows/macOS/Linux.
Have you seen https://skip.tools/?
Why does the Community Toolkit -> DataGrid perform poorly in the Web demo? Sorting the columns is very slow: https://gallery.platform.uno/
Will Uno move to a model of rendering the UI to canvas for better performance?