HTML5 is for the web, not for mobile apps
Android, iOS, and Windows Phone all support building applications with HTML5 and other web technologies. It all sounds great, right? Let’s take a look at some of the “advantages.”
- Learn one thing then apply it both on the web and mobile
- Build it once then run it everywhere
Sounds great, but there is something missing. Everything stated above is all about you the developer and you the creator. Instead, the focus of an app should be on the user and solving their problems or needs.
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 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’ll be missing on those opportunities.
HTML5 does not look and behave like native app
There are many frameworks trying to solve it, but none does. Your app will feel foreign compared to all the native apps they use.
You should have a really good reason to build an HTML5 mobile app, and saying “that’s what I know” is not a good one. HTML5 is the right technology for a web app, but it’s not the right technology for a mobile app.