Why Native Technology Rules in Mobile Apps

“It’s an artificial dichotomy,” says Adam Blum, CEO of Rhomobile, on the question of whether you should create mobile apps in HTML5 or natively. Rhomobile is an open source framework that lets developers quickly generate native smartphone apps that run across all devices.

Blum agrees that HTML5 is a fabulous tool for creating mobile interfaces (it’s integrated into his company’s platform). But he doesn’t believe it’s the best solution for creating mobile Web apps. “If you do that, you won’t get device capabilities. You won’t get to have local data on your device,” he observes. “The solution is not being HTML5 or native. It’s being both.”

Comments

  1. BY David says:

    End users don’t care about languages. What matters is that the app offers meaningful functionality, is user friendly and performs well.

  2. BY David Spark says:

    David, you’re right. But what Adam was saying is that you simply can’t get the functionality you want on a mobile phone if you’re just relying on HTML5. You need native apps for transactional data and actions.

  3. BY &E; says:

    Meh, disagree to some extent, Adam.

    It largely depends on what the “app” is for. If you don’t need GPS data, photo uploading integration, contact info from the phone, etc. a web app is the most flexible solution. But the way Apple keeps reinventing their implementation of HTML5, whether you do native apps or web apps, you’ll always have to do a one-off for the iPhone. Blech.

Post a Comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>