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.
  • E-mail

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.

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | Please read our commenting policy.