HTML5 Vs Native App : Which To Choose ??
Solution 1:
Creating a music player in my app - Both. HTML5 might be tedious.
Accelerometer usage - Native. Html5 won't support it
Camera usage - Native. Html5 won't support it
Using gestures - Native. Html5 can support it, but you'll have to use an external library
Multi-touch capabilities & gestures - I'd say native, for the ease of development
Developing 3D game (or) 2.5D with physics - Both, some great libraries are now available for both systems. However doing what you want in HTML5 is probably not easy at the moment.
More generally, HTML5 gives you the possibility to write you code once for every system and then wonder if it'll work in the same way everywhere. Native apps require a specific development for each platform, with the costs and the problems of maintaining many softwares at different stages of maturity that it leads.
However if you don't need specific features, go for HTML5. It's still a bit tedious to write code on it so far, but the quality and the amount of available libraries is increasing every day. Use CoffeeScript, it'll save you headaches.
If your application is designed with responsive design in mind, you'll also be able to support computers, tablets and smartphones in one application.
Solution 2:
Unless your app is extremely simple then avoid the so-called cross-platform solutions and build native for each platform. If you do, you will be glad.
If you don't then you will be very sorry when something breaks on some devices but not others, or when you get a request to add certain capabilities that some devices won't support.
Basically using a cross-platform solution is lowest common denominator / only suitable for simple apps / false economy in my experience.
Just my humble opinion based upon 12+ years of commercial software development and experience of trying both approaches myself.
Post a Comment for "HTML5 Vs Native App : Which To Choose ??"