Linked by Thom Holwerda on Wed 13th Mar 2013 22:02 UTC, submitted by JRepin
Qt "For this preliminary release, we are focusing on the developer experience, working to enable Qt developers to easily run and test their applications on Android devices. While there's nothing preventing you from deploying your app to an app store with Qt 5.1, we're recommending that people wait until Qt 5.2 before they do that, as we'd like to put some more work into improving that experience: making more options for how your app is deployed, adding more polish in general, and adding more support for Android APIs, both by allowing you to extend your app with Java code or by mapping them in C++ APIs, whichever makes the most sense."
Permalink for comment 555402
To read all comments associated with this story, please click here.
RE[2]: Hmmm ....
by leos on Thu 14th Mar 2013 06:58 UTC in reply to "RE: Hmmm ...."
leos
Member since:
2005-09-21


Ideally you get a high degree of code sharing of the back end code, some code sharing of the middle glue layer, and you get technology and paradigm similarity at the view level.

This is all achievable today with Windows 8 and Windows Phone 8 and the new Windows 8 Twitter app actually shares a huge amount of code between WP8 and Windows 8. The snapped view on Windows 8 is identical to the Windows Phone 8 UI.

Can it be easier? Hell yes it can, but its getting better. I'm sure the same is the case with Qt once you get down into the nitty gritty of porting across N platforms.


The Win8 dev platform is pretty nice, but a bit of a dead end for anyone that cares about tablets (or phones for that matter). The promise of Qt ports to Android and iOS (coming in Qt 5.2) is that we might actually for the first time ever have an effective way to target desktop and mobile platforms with one toolkit (different UI layers of course if you're doing it right). In this day and age, you can't get away with going microsoft only.

Reply Parent Score: 4