Digia Releases Qt 5.1 With Preliminary Support For Android and iOS
An anonymous reader writes "Finnish software and services firm Digia, which bought Qt from Nokia back in August, has released version 5.1 of the cross-platform application framework. Among the changes are 'significant improvements' to Qt Quick and preliminary support for Android and iOS. The latter means Qt on Android and iOS are both considered Technology Previews, letting developers start building for the two mobile operating systems and porting apps from other platforms by reusing the same code base. Although most of the Qt functionality and tool integration is already in place to start developing mobile apps, Digia promises complete ports to Android and iOS will come with the release of Qt 5.2 'later this year.'"
Google released the NDK (Native Development Kit) not long after Android was introduced because they finally clued in that Java simply isn't fast enough on slower processors to do gaming.
It has been possible for some time via necessitas. Now they only added it to the official package. Most Qt apps are written on desktop using QtWidgets. When you are developing for mobile devices, you should use QtQuick. QtWidgets aren't designed for mobile devices.
Not only that, but it allows integration of Web technologies and native code, having the best of both worlds. For example, on the desktop side, you could call Javascript code in Webkit from the C++ side of things, and vice versa. I actually just uploaded a video showing this on the Raspberry Pi (starts at ~50 seconds in): http://youtu.be/JOkks0oVsp8 In case you're wondering what that is, it's a GPS Mapping application for our trackers (for more info, see our Indiegogo page: http://igg.me/p/424464/x/3476322)
This allows for optimized applications on low power devices, while still being able to use web technologies where it makes sense.
My blog, if you're interested: http://www.purp
There was a time in April 2010 when Apple changed the App Store Review Guidelines to ban all languages other than Objective-C and C++ as an effort to keep Adobe from offering AIR, its tool to package Flash applications as iPhone apps. When this policy was in effect, MonoTouch would have been banned, and the developers of Unity 3D were even porting the library to allow writing a game in Objective-C. Such a game would share no code with the same game for other platforms, making it yet another DRY violation induced by a platform gatekeeper. Apple reversed this policy two months later after it became clear that this banned the use of Lua for game logic and dropped all language restrictions the following September.
Yes. There are already Qt based apps on the app store.