HTML5 Mobile Development: 7 Good Ideas (and 3 Bad Ones), February 13, 2013 HTML5 can be a boon to enterprise mobile app development, but you have to identify the right use cases to make it work. Here are 7 scenarios that make sense for HTML5, and 3 you might want to avoid.
Bad Idea #1: When You Need Full Functionality
Apps that need to take advantage of on-device resources like the phone or the accelerometer should be short-listed for native app development, notes Michael King, director of enterprise strategy for Appcelerator, a mobile development platform company.
"HTML5 apps are great when you don't need a lot of interactivity with the device," he says. "But I think any of your interactive apps are still going to need to be native for the foreseeable future." In the same vein, enterprises that want to fully control configuration and data flows may also want to go native within sensitive apps.