Android, iOS and Windows Phone support building applications with HTML5 and other web technologies. It sounds great.
- Learn one thing then apply it both on the web and mobile.
- Build it once then run it everywhere.
It really sounds great, but there is something missing. It is all about you, the developer, you as a creator. Yet, the focus of an app should be on the user and solving his problem or need.
Before falling in love with the points above, you should ask yourself two questions.
- What are the benefits of the customer?
- What are the drawbacks for the user?
Could there be specific reasons to use HTML5 in some cases?
Yes, there are. One very specific reason is when your customers don’t want the app to be limited by the App Store rules. You can build an HMTL5 app and distribute it over the internet. Of course, there are other limitations.
Slow & Sluggish
No matter how much you optimize your app, it will always be slower than a native one, and the users will feel the difference.
Limited availability of specific underling technologies of the platform.
Phonegap tries to solves this, but it doesn’t do it completely. Most devices have some capabilities that can enhance the user experience, but you will be missing on those opportunities.
HTML5 does not look and behave like native app, never
There are many frameworks trying to solve it, but none does, even a little. Your app will feel foreign compared to all the native apps they use.
Having in mind all this, you should have some really good reason to make an HTML5 mobile app, and “that’s what I know” is not one. HTML5 is the right technology for a web app, but it is not for a mobile app.