Or... Just make your app LGPL compliant and use Qt anyway.
/René On Mon, 28 May 2018 at 15:57 ekke <e...@ekkes-corner.org> wrote: > Am 28.05.18 um 11:25 schrieb Christoph Keller: > > You are correct, in my opinion the price for Qt is way too high if you > only need the mobile platforms. > > that's right > there should be a 30$ or so per Dev per month license for mobile platforms > really don't understand why Qt isn't pushing mobile Apps with a cheap > Indie Developer License > > That's the reason we're thinking about phasing out Qt in the next project. > > sorry to hear > Qt is so GREAT on mobile platforms w QQC2 > > You'll likely reach the $100k revenue with a 2-man project soon. > > yep - with 2 or more devs you'll reach the limits soon > > I'm a single developer working from my home office and it works for me > with StartUp License > @Sylvain: if you fit into the 100.000$ maximum I recommend to fill out the > formular and wait for answer from sales. I'm pretty sure you'll get the > license. I'm using this license with 99 $ / month and know that there are > some otherd evs out there using this license > > Don't forget there's also Google's Flutter in the game which is written in > dart and renders all by itself like Qt does. > > Flutter does a great work and is pushed by Google. > but: try to develop a x-platform project with Camera, BluetoothLE, ... and > compare with Qt ;-) > > React Native will give you all the joy of dependency management > (cocoapods, gradle) and 3rdparty libraries available for mobile which will > be hell to integrate with Qt (think of lottie animations and google maps > for example). Also they support the nice "hot reload" (flutter also has > this feature). > > Regards, > Christoph > > On 27.05.18 10:13, Sylvain Pointeau wrote: > > 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? how did you succeed to match the native > look and feel? > > My choice is between Qt and React Native. > > 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. > > 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. > > 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. > > Best regards, > Sylvain > > > _______________________________________________ > Interest mailing > listInterest@qt-project.orghttp://lists.qt-project.org/mailman/listinfo/interest > > > > > _______________________________________________ > Interest mailing > listInterest@qt-project.orghttp://lists.qt-project.org/mailman/listinfo/interest > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest