3 ms·

What are the possibilities of an Android app. Qt says it works on Android but not sure. A C++ dev here. How much of an effort would it be to port it to Androi

What are the possibilities of an Android app. Qt says it works on Android but not sure. A C++ dev here. How much of an effort would it be to port it to Android or do you see any blockers?

Cryptonic 4y ago
It's not much effort, a few days and it runs if you start from 0. I usually do all my Qt hobby projects for Win, Mac, Linux and Android (have no iPhone so I don't try). Just make sure you leverage QML's power for your GUI. But eventually you have to rethink the user interaction and also deal a bit with layout changes for portray/landscape, manifest, permissions and stuff and stuff. Depends on your app how much work is here. If mobile stuff gets complicated and you need to do a lot of custom things with device hardware maybe Felgo is worth looking at. It's a Framework for mobile development build on top of Qt/QML
pjmlp 4y ago
Depends on what you want to do, note this information is outdated (back when Qt used to sell mobile licenses a couple of years ago). If you are confortable doing the whole UI in QML and eventually creating your own JNI/Java wrappers for APIs not yet wrapped in Qt, it is doable. The Qt Widgets are focused on desktop workloads, so they aren't much usable, you might even get a desktop looking dialog poping up. If you really want to go with native Android UI route, then there isn't much help Qt can provide here. Major blocker is that after all these years Google still doesn't provide any kind of tooling to improve JNI workflows, we only get the basic java -> header file generation tooling, e.g. javah.
rubymamis 4y ago
Hi! I didn't develop for mobile yet, but it seems to me like it will take considerable time since we're not leveraging QML's power, and there seem to be a lot of differences between mobile and desktop. But maybe some mobile/QML developers can show me otherwise.

What are the possibilities of an Android app. Qt says it works on Android but not sure. A C++ dev here. How much of an effort would it be to port it to Android or do you see any blockers?

Cryptonic 4y ago

It's not much effort, a few days and it runs if you start from 0. I usually do all my Qt hobby projects for Win, Mac, Linux and Android (have no iPhone so I don't try). Just make sure you leverage QML's power for your GUI. But eventually you have to rethink the user interaction and also deal a bit with layout changes for portray/landscape, manifest, permissions and stuff and stuff. Depends on your app how much work is here. If mobile stuff gets complicated and you need to do a lot of custom things with device hardware maybe Felgo is worth looking at. It's a Framework for mobile development build on top of Qt/QML

pjmlp 4y ago

Depends on what you want to do, note this information is outdated (back when Qt used to sell mobile licenses a couple of years ago). If you are confortable doing the whole UI in QML and eventually creating your own JNI/Java wrappers for APIs not yet wrapped in Qt, it is doable. The Qt Widgets are focused on desktop workloads, so they aren't much usable, you might even get a desktop looking dialog poping up. If you really want to go with native Android UI route, then there isn't much help Qt can provide here. Major blocker is that after all these years Google still doesn't provide any kind of tooling to improve JNI workflows, we only get the basic java -> header file generation tooling, e.g. javah.

rubymamis 4y ago

Hi! I didn't develop for mobile yet, but it seems to me like it will take considerable time since we're not leveraging QML's power, and there seem to be a lot of differences between mobile and desktop. But maybe some mobile/QML developers can show me otherwise.