In case you missed it, InfoQ [1] has an interesting analysis regarding hybrid mobile app development frameworks [2]. They are profiling 12 tools and soliciting community feedback so as to make a ThoughtWorks-like technology radar [3]. If you participate in the voting you are entitled to see the voting distribution.
What’s interesting (and not too surprising) about this analysis is that frameworks like PhoneGap [4] or jQuery Mobile [5] (and laughably JQTouch [6]?) are leaning more towards adoption ready when compared to frameworks like Marmelade [7], Coronona [8] or MoSync [9]. But this radar lacks some clarifying dimensions – for example, if you want to produce a mobile website on a lot of different mobile platforms quickly, then PhoneGap is probably the way to go. But if you’re looking to create a mobile app, then the choice to use PhoneGap must be treated with extreme caution.
You cannot create a compelling user experience [10] that works across all platforms consistently [11] with this framework right now. And it isn’t even the fault of PhoneGap entirely – it’s HTML5 [12]. That’s why going with something like JQTouch without viewing the big picture of what you are building is laughable.
Frameworks like Marmelade or Corona might be a bit more difficult to get started with (after all, you code in something other than HTML or JavaScript) but they can produce a native app that offers a compelling user experience capable of generating a wow. Remember, native-ness trumps the browser [13] almost always unless your app is a series of screens that don’t require the user to interact.
Accordingly, the study lacks some needed dimensions – mainly, whether or not you are building a mobile app or mobile website. Don’t fall into the hype trap and jump into PhoneGap development unless you are sure what you are building is a simple mobile website and your audience isn’t expecting something like Flipboard or AngryBirds. Otherwise, you’ll find yourself investigating either pure play native development or frameworks that ultimately produce a native app.
Links:
[1] http://www.infoq.com/
[2] http://www.infoq.com/research/cross-platform-mobile-tools
[3] http://www.thoughtworks.com/insights
[4] http://phonegap.com/
[5] http://jquerymobile.com/
[6] http://jqtjs.com/
[7] http://www.madewithmarmalade.com/
[8] http://www.coronalabs.com/
[9] http://www.mosync.com/
[10] http://thediscoblog.com/blog/2013/03/04/its-a-question-of-wow/
[11] http://thediscoblog.com/blog/2012/09/01/cost-and-the-great-mobile-app-debate/
[12] http://thediscoblog.com/blog/2013/02/17/circumventing-mobile-ux-expectations/
[13] http://thediscoblog.com/blog/2012/09/24/a-tale-of-three-browsers/