3 ms·
I've worked with the NDK/JNI and totally agree on the "poor soul" comment. If you're someone like Spotify who has enough money, supported platforms, and a compl
by bschwindHN 10y ago
I've worked with the NDK/JNI and totally agree on the "poor soul" comment. If you're someone like Spotify who has enough money, supported platforms, and a complex enough app, then that method is likely a win.
But if you're only targeting Android and iOS, you'll likely get to market faster with something like React Native while still retaining native UIs. It'll certainly be better than Phonegap/Cordova/Ionic.
- Capt-RogerOver 10y agoWhat is your opinion on Qt mobile?
- bschwindHN 10y agoI haven't personally used it so I don't have much to say. It looks like it requires a commercial license so that doesn't get me particularly excited about it. I'm also not sure how hard Qt actually tries to give you UI components that look like what you would find in a typical app. If you have Qt experience then I'm sure you can make it work, I've heard good things from people who have used it. I'm also guessing it has much more consistent and robust UI behavior compared to running things in a web view. You'll have to find someone who has actually used it though to get a real opinion, I'm just speculating here.