[Interest] QtQuick for mobile - any experience to share?

ekke ekke at ekkes-corner.org
Sun May 27 13:26:07 CEST 2018


Am 27.05.18 um 10:13 schrieb Sylvain Pointeau:
> Hello Ekke, Jason, Jérôme, and all
>
> Thank you so much for sharing your experience and tips.
>
> Did you use the v-play components?
v-play components are really great, but I'm not using them because
a) they are not open source - one of my reasons to use Qt is Open Source
b) each v-play release is bound to a specificx Qt version - so could be
problematic if you want to apply a patch
c) v-play license costs exta (Indie license for > 50k and < 100k annual
turnover)
> how did you succeed to match the native look and feel?
QtQuickControls 2 with Material Style give you native look-n-feel on Android
you can customize UI Controls so they fit better iOS, but I'm using
Material Style together with BottomBar Navigation and for my customers
this is ok. Navigation of app is like iOS app. not 100%, but really fast.
>
> My choice is between Qt and React Native.
This was also my question: should I use React Native or Qt ?
As I started, QtQuickControls2 just came out and from my POV Qt mobile
apps are easier to develop as RN.
Now there's also Flutter.io with Dart, but again: Qt Apps are easier
done x-platform.
yes - sometimes I miss a feature and some native code is needed for iOS
or Android. I never did native Android or iOS apps, but (with the help
of other Qt devs) managed to implement things like share-to and
share-from other apps. solutions are always published open source to
help other devs.
BTW: my next example app will be QML Camera Example for Android/iOS with
some real-life complex use-cases
>
> I would have gone with Qt but the price is the real barrier for me. As
> I don't know the success of the app, it is hard to start (and convince
> my partners) knowing the price to pay per year.
>
> Ekke you mention in your blog about the startup plan but as far as I
> know, this is discontinued, the startup plan now let you use the
> "trial" version until you go to the store.
take a look here
https://www1.qt.io/start-up-plan/
and apply, fill out the fomular and wait for feedback
if you match the requirements (less then 100.000 $ revenue p.a.) I'm
sure you'll get your startup license
>
> React Native is fully in javascript, but seems typescript can be used
> (which is much better) (BTW would be great to use typescript in QML). 
>
> The benefit of RN is IMO to do json natively, but the negative aspect
> is that it is not as cross plateform as Qt, so the desktop version is
> likely to be (much) more challenging.
yep - Qt is so powerfull x-platform. per ex. I'm debeloping for Android
and iOS but testing on macOS
>
> I am really puzzled, I think that Qt is better than RN, but the price ...
>
> Am I missing something? is there someone else in the same situation?
>
> ps: I continue to investigate (and to read the blog of Ekke), my
> choice is not done yet.
I really recommend to try out Qt with QtQuickControls2

ekke
>  
> Best regards,
> Sylvain
>
>
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20180527/5fafc3ea/attachment.html>


More information about the Interest mailing list