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 #3: When Users Need Offline Functionality

Reduced performance isn't the only hit you'll take by using HTML5. There's also the matter of offering application support when the user doesn't have wireless access. Approximately 70 percent of business technology leaders told InformationWeek Reports that native mobile apps offer the best approach to provide offline functionality within an app.


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.