"Itβs important to note that these styles are not claiming to be native, but instead a 100% cross-platform implementation of the Material and Universal design guidelines. For example, the Material style does not adapt to any Sony or Samsung theme on Android. You can run these styles on any platform and they will look more or less identical."
I still have to do style all the standard widgets myself or build them from scratch. I don't want them to be more or less identical, they should be what the user has on their handset.
For example where is the toast, FAB, file picker, recycler view, notification..?
iOS support is still not a thing, apparently from the comments.
Also where are the OS bindings for resources, background services, IPC between apps, OS state notifications?
Currently on the mobile space, Qt adds little value over using C++ with boost and similar libraries for the portable business logic and using the platform's main language for the UI.
At least with Xamarin I have a very good coverage for the wrapped APIs and mobile widgets per platform, updated quickly after each new OS release.
And I agree with your comments btw. React native is another good candidate for native controls, for some types of applications
It was less work to use Java, C++/CX and plain C++ than having to mimic native widgets with QML and having do my own OS wrappers. Plus the additional 30 MB.
Also the C++ widgets either didn't work on mobile or were 1:1 like the desktop version, e.g. file selector.
From the documentation, it doesn't seem it has improved much.