Hacker News new | ask | show | jobs
by pjmlp 3503 days ago
I second FlyingSnake.

It is easier to use straight C++, using a MVVM approach than Qt.

QML doesn't provide enough support for native UIs, so you end up spending time redoing native widgets on it.

Similarly Qt doesn't provide any bindings for the majority of mobile OS APIs, so you end up writing your own wrappers anyway.

In the end it is a bigger effort than using C++ libraries plus your own integration code.

Additionally in iOS and UWP, you get C++ extensions, Objective-C++ and C++/CX respectively, that make it quite easy to integrate with native APIs. Android is the outlier here with the JNI pain. Still Djinni and SafeJNI help to reduce the pain.