"Why did the FT decide to create an HTML5 web app?
(...) There are clear benefits. Firstly, the HTML5 FT Web App means users can see new changes and features immediately. There is no extended release process through an app store and users are always on the latest version.
Secondly, developing multiple ‘native’ apps for various products is logistically and financially unmanageable. By having one core codebase, we can roll the FT app onto multiple platforms at once.
We believe that in many cases, native apps are simply a bridging solution while web technologies catch up and are able to provide the rich user experience demanded on new platforms. As these improve we expect to see more HTML5 apps and fewer native apps, but there is always likely to be a market for native apps for specific brands or when deeper integration with the hardware or super fast performance are required (games are the most obvious example)."
HTML5 vs Native App
-Cross Platform solution
-Saves money (Easier to manage, maintain solution)
-No AppStore approval process, you maintain full control over your app.
-User experience: usability and performance.
-AppStore ecosystem is lost, you don't get marketing, distribution, consumer user base of the AppStore ecosystem.
-Need to run in a web browser, unless you wrap your web app using PhoneGap or similar tools
-Unable to access hardware API, unless you wrap your web app using PhoneGap or similar tools.
Buttom line: if your app is a simple app that can be implemented in html and you dont need high performance or do not need to do anything fancy with the UI then build your app in HTML. But you need to think about how you will market your app without the AppStore ecosystem. Otherwise your next best choose would be to build a very thin mobile client and perform all your business logic via a web service.