One of the inside baseball debates about mobile is whether it will be driven by apps or web browsing and HTML5. At first blush it would seem that the cost of developing, certifying, and maintaining apps across mobile platforms would give a clear edge to HTML5 with its enhanced offline browsing and (forgive me) flash-like functionality. 
But of course, the pace of full implementation of HTML5 and the final feature set (even the full specification is two to three years away) could change all that. This article suggests some likely disappointments with HTML5, some of which may prove problematic for the more complex mobile apps currently being talked about. We probably should not write off apps just yet.
Comments
3 responses to “Mobile apps or HTML5?”
Seems like I haven’t heard anytyhing about HTML5 for a while…not sure why. Has interest died off, or is it just so widley implemented now that it’s no big deal?
My guess, Mike, is the latter.
I would add that the choice of technology depends largely on the type of app. For games and utility apps, go native(usually).For content-driven apps,HTML5 and hybrid models are perfectly acceptable and provide the most reach.