A few things not mentioned, (or scanning to catch up on the thread, I did not see)
1. RN will expose native libraries. This is terrible for a X-platform developer as if you use Multimedia, have to know each multipedia API expertly. The best thing is to use Qt and have it abstract the native libraries. I once attempted to write the code to use different recording qualities in iOS and got close, but the Trolls had it done right in a week. Now repeat this for Android (luckily, this was already supported on android). So whule RN is "cross platform" as soon as you do anything fancy, you're into native API land. Qt does not have this problem.
2. The license is really worth it. I'd love to say that Qt is perfect. It is not. Having your issues fixed in the next maintence release is a good thing. But, not all your issues will land. I have paid for Qt support, and I think I got comparable value out of it. Sometimes more, sometimes less. But I do recommend it. One downside is that for Agile teams that release often (weekly/bi-weekly), it takes longer to get an issue resolved than a sprint. Some of this is just due to communication time (48 hour turn around, 3 messages, has you in the next sprint.) But such is life.
3. One significant demerit that Qt gets is its lack of focus on mobile in current releases. There should be by now a cross-platform Push Notifications API. There isn't. There isn't one planned or on a roadmap. I'm not talking a full notifications build out, I'm talking about the API which you can then select VPlay, Firebase or other (AWS), and then have that plug into your app via a consistent API. It should share API wih desktop notifications.
4. Minor deperits for Qt not integrating other mobile OS-depenent features in areas where the mobile OSs overlap, but Qt has not ventured in general. Specific examples escape me (I no longer have access to that code base) but it was minor stuff that I thought "Qt should already be abstracting this". OOh, I remember one - setting the no-sleep mode of an app (for instance while recording) Sure it's like 3 lines of code on each platform, but it should already be supported. This was also before Torch existed as well (turning on the camera light) which is another example. But Torch did eventually become a thing (5.8)
5. Qt gets deperits for not always supporting the latest APIs like Fingerprint scanners or face detection. It has been excusable when these were private APIs (Atrix finger print scanner in 2010), but now that eveyone has biometric authentication in various forms in the OS, it could be considered past-due. In an ideal world there would be a team making sure Qt was quick to release updates supporting the latest APIs.
In short, I think Qt really delivers on the 95% that you need to make a x-platform, full-featured app. But the 5% is an extremely painful 5%. Maybe if there was a tool like RN has to automatically create bindings to platform libs?
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
