flutter-wonderous-app VS Uno Platform

Wonderous is an app we've pointed people to in the past. I believe the current version on the App Store uses the newer Impeller rendering engine instead of Skia, but I could be wrong.

https://github.com/gskinnerTeam/flutter-wonderous-app

(Disclaimer: I work on Flutter)

Wonderous:

A showcase app for the Flutter SDK.

Built by gskinner in partnership with the Flutter team, Wonderous deliberately pushes visual fidelity, effects and transitions to showcase what Flutter is truly capable of on modern mobile hardware.

https://github.com/gskinnerTeam/flutter-wonderous-app

I’d recommend going all in on Flutter. Instead of going too deep into the weeds on why, I’d suggest reading through this page about the Flutter 3.3 Wonderous showcase app. Make sure to download it from the App/Play Store to get a feel for it, as I think the hands-on experience of Flutter’s capabilities are more convincing than me typing at you. Then, implement your solution using an architecture similar to what they did by reviewing the code in the Wonderous GitHub repo. It sounds like your project is going so some upfront investment of time wouldn’t hurt too much.

Looking here https://m3.material.io/develop/flutter, I saw the Wonderous app which is pretty great. The Google Codelab 'Boring to Beautiful" also gives you a pretty complete, well structured and very responsive app by step 7 too.

And you can see the source code here: https://github.com/gskinnerTeam/flutter-wonderous-app

And Uno Platform (https://platform.uno/) is akin to React Native in terms of native controls usage.

also UNO Platform (C#) which is suitable for simple or complex cross platform business applications : https://platform.uno/

Why is this a problem? At face value, it isn't a problem. Taking a step back at a more global level, what does "uComponents" mean to the rest of the world? Many of the .NET developers who heavily use NuGet may have not even heard of Umbraco CMS, let alone a 3rd party plugin for it. What if people from the Uno Platform community are browsing NuGet for some kind of components extension library? You can see, this could get confusing outside the scope of the Umbraco community/ecosystem. On top of this, uComponents was developed against Umbraco v4, with its last release in 2016, now it's there to be lingering on the NuGet repository until the end of time, set in stone.

Not a fan of XAML after trying to get into it, but there is Uno Platform. It wraps native widgets on mobile, just like React Native (which is good for accessibility), and uses C#. https://platform.uno/

My guess is that it's mainly focused on mobile. On Windows, it has no overhead (behaving like a normal WinUI 3 app), on macOS I think it uses Catalyst by default (which was developed by Apple to make more iOS apps available for Mac desktops) and on Linux it draws its own widgets that the devs try imitating the GTK style with.

On Android and iOS, it just uses the native widgets which I think is a better experience so you can see my reasons for guessing it's mobile-first. That may or may not be what you want.

5- Uno

> ...building UIs with the document/element api

When the whole premise is flawed, JSX or not, does it really matter if there is a better or worse way of misusing a technology not meant for UIs?

Leave HTML and JavaScript to Wikipedia and other hypertext document libraries.

Unfortunately, WASM is not there yet, but people are trying: https://platform.uno.

Uno Platform is fully open source, under Apache 2.0 license. You can see the license here https://github.com/unoplatform/uno/blob/master/License.md