QML is slow, you only get the compiler in the commercial version.
Still no proper support for mobile platforms. You basically have to write most of the bindings yourself. Specially a pain in Android, given JNI.
Only QML widgets get some platform theme support, not the C++ ones, so you need to add the QML engine to the set of libraries to pack.
Also you are supposed to code all native UI behaviours yourself, thus having more work than an hybrid development of native mobile OS language (views) + portable C++ libraries (business logic).
If you pack Qt libraries with your application it is around 30 MB for the runtime dependencies. You can also scare the user by asking them to download the libraries as separate app instead.
I got my demo application using Java + C++ and C++/CX + C++ around 5 MB.
Finally if you look at the set of exposed platform APIs across all mobile OSes, they are way behind Xamarin and their commercial licenses are much more expensive.
Still no proper support for mobile platforms. You basically have to write most of the bindings yourself. Specially a pain in Android, given JNI.
Only QML widgets get some platform theme support, not the C++ ones, so you need to add the QML engine to the set of libraries to pack.
Also you are supposed to code all native UI behaviours yourself, thus having more work than an hybrid development of native mobile OS language (views) + portable C++ libraries (business logic).
If you pack Qt libraries with your application it is around 30 MB for the runtime dependencies. You can also scare the user by asking them to download the libraries as separate app instead.
I got my demo application using Java + C++ and C++/CX + C++ around 5 MB.
Finally if you look at the set of exposed platform APIs across all mobile OSes, they are way behind Xamarin and their commercial licenses are much more expensive.