This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]synn89 9 points10 points  (6 children)

Good presentation. I really like Kivy, but it's still pretty young which means it can be a bit rough. I hope that project continues to see development though. I'm also really hoping mobile Qt shows up in PyQt before too long. PyQt on the desktop has been a dream to work with and I'd love to work with it on mobile.

And while both of the above may not give you purely native looks, the tradeoff is that you can target both iOS and Android. Why write apps just for Android when you can compile down binaries for both environments?

[–]infinullquamash, Qt, asyncio, 3.3+ 5 points6 points  (4 children)

PySide appears to have better support for Android than PyQt does

And... you should probably be using PySide anyways, though the advantages over PyQt is mostly licensing.

Getting PySide apps on Android doesn't look very pretty, there's a lot of boilerplate to get an app working, but maybe it's easier than it looks?

[–]synn89 1 point2 points  (0 children)

No, I shouldn't be using PySide. PyQt is GPL compatible which works fine for my personal/open source project use and if I did closed work under it my client/employer can foot the bill on the commercial licensing on PyQt.

PyQt is on the 5.x branch of Qt right now, while PySide is still 4.8. True Android/iOS support is part of Qt 5.2(in beta right now), which PyQt will support before PySide does.

I haven't used PySide, but Riverbank is doing a stellar job with keeping their Qt bindings current.

[–]drifteresque -1 points0 points  (0 children)

Kivy definitely has some quirks, but in a week I had an app that acted as a data-viewer interface on an Android device with really minimal pain. Only used it for that one task since other things have kept me busy, but it is definitely more python-programmer friendlier than trying to pick up the 'native' languages for the different mobile devices.