There are many cross-platform mobile development platforms. The main platforms, all mutually exclusive:
- iOS (iPhone, iPad, and iPod Touch)
- Android
- Blackberry
- Windows mobile
- Windows Phone 7
- Symbian
- MeeGo (a merger of Maemo and Moblin)
- WebOS
There are also many different infrastructures for mobile applications that support various arrays of smartphone platforms, including, but not limited to:
- Rhodes
- ELIPS
- RAMP
- Titanium
- Phonegap
- MoSync
- rotation
- Bedrock
- Qt
Qt is an excellent platform for developing cross-platform desktop applications, and also takes care of several mobile platforms - Windows Mobile, Symbian, MeeGo. There are community ports for iOS and Android (and webOS?). Blackberry and WP7 are now at your own peril and risk.
MoSync also looks good, supporting a large number of platforms, including Java-based, from C ++. However, this is not well known by AFAIK and has its problems.
So my question is: is it really worth using a cross-platform platform for mobile development? Everyone I found has one flaw or another that makes it unusable.
At least if Qt supports iOS and Android, you will need no more than three versions of the application to support all platforms (Qt, Blackberry and WP7). The community ports that are around are not well supported, although they are far from complete. In addition, even if they are completed, will they ever support them anyway or will this be considered a bad business strategy?
Should I just bite the bullet and write the native ports for each smartphone platform? Qt + iOS + Android + WP7 + Blackberry + webOS? 5-6 versions of the application are quite a lot to support, but solutions for cross-platform development on smartphones do not look great right now.
cross-platform qt smartphone
Jake Petroules Nov 08 '10 at 20:22 2010-11-08 20:22
source share