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

Use Case #5: You're Prototyping Native Apps

Sometimes you can plan on replacing HTML5 apps later, by using Web-based mobile apps as a proving ground for a particular app that would cost a lot to push native right off the bat.

"Designing a mobile application for the enterprise sector requires a significant amount of UX planning, reviewing, and testing, especially if the app is bringing functionality to a mobile device that users are already familiar with via the enterprise's large scale applications," says Lorinda Brandon, director of solutions strategy at SmartBear, a vendor specializing in code testing and website monitoring software.

It's much easier to develop a proof-of-concept app on the HTML5 framework prior to investing in native app development because, as this chart shows, business technology pros noted that browser-based mobile apps are easier and faster to develop and deploy.

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.