app-center VS Uno Platform

I don't think the snap-store client itself is proprietary. It's a fork of an old version of GNOME Software, which is being replaced by a new rewrite using Flutter.

There's a dedicated snap store replacement in the works. You can try it today! See: https://github.com/ubuntu-flutter-community/software

I have read about this new version of Ubuntu store that canonical may adopt, that is said to be responsive and is written in flutter: https://github.com/ubuntu-flutter-community/software Also the mint store is known to be quite responsive but I don’t know what the name is or if it can be installed on others. Has anyone done either??

I haven't really built anything large from scratch by myself yet, but I do contribute to the new Flutter based Ubuntu software centre, which should hopefully be released in the new Ubuntu release. https://github.com/ubuntu-flutter-community/software

I mean right now the devs' official stance is that they do not want to add Flatpak support. Not that they can't, not that they'd welcome someone else doing it/helping out with the work, just that they straight up do not want Flatpak support. Source

Recently a new front-end store for Ubuntu has been making headlines.

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