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 #6: You've Got Limited Staff To Tap Back-End Systems

Use HTML5 "when you need to mobile a process or back-end system and simply don't have the native development skills or budget to go native," SAP’s Wargo says. Back-of-the-house enterprise functions need to work, but they don't necessarily need the slick branding and polished image required of consumer apps. This compromise in look and feel lets organizations quickly deliver these functions across the user base without getting bogged down by a lack of internal talent for native app development. This could be huge for the 33 percent of organizations that told InformationWeek Reports they don't develop custom mobile applications due to skills deficiencies.

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.