Avoid Cross-Platform Mobile Frameworks
Posted Jul 22, 2012 1:56 UTC (Sun) by robla
In reply to: Avoid Cross-Platform Mobile Frameworks
Parent article: PhoneGap 2.0 released
Which consensus? I think it pretty much depends on the app you're creating and which framework you're using.
The Wikimedia Foundation (where I work) is using PhoneGap for building the official Wikipedia app for Android, iOS, Blackberry Playbook, and Windows 8.
The nice thing about PhoneGap (from what I understand) is that you build the core of your UI in HTML, and then it's simple enough to replace portions of the app with native portions where necessary. Using PhoneGap, we're able to share a lot of work not only between the apps, but also with the mobile version of the website.
Since many platforms have HTML as a core component of their UI (e.g. WebOS, Boot2Gecko, Metro, Playbook, Chrome), and there's so much work going on to optimize HTML on all platforms, and no matter what, you almost certainly need to at least have a mobile web interface in addition to your app if you have any significant web presence, it's not dumb at all to invest the bulk of your work on HTML.
For some applications, it makes sense to invest heavily in native iOS and Android development. However, there are plenty of cases where it doesn't make sense at all.
to post comments)