Sep 25, 2012 - HTML5, mobile, web    No Comments

HTML5 vs Native…

Really nice event from the Mobile Monday guys last night with the theme being the hottest topic in Tech and Mobile industry: “HTML5 vs Native”.

Big debate about from the two teams, which was fantastically moderated by Ewan Macleod.

HTML5 devices

I have for a long time been keeping an eye on the evolution of the HTML5 technology as you can see in my presentation HTML5: the mobile challenge. I am a big fan of HTML5 and firmly believe that it destined for great things in the future.

Until the technology matures, HTML5 can’t fully replace native apps.

Some people think that because HTML has been defined as a markup language and not a programming, it cannot compete with native apps. I disagree because this applies to old HTML. Nowadays, when we speak of HTML, it is understood that JavaScript and CSS is involved.

Here are my views on when to use the HTML5, native or the hybrid approach based on my experience:

When to use HTML5:

  • cross-platform ideology (PC, tablet, mobile)
  • light content distribution e.g. news
  • discovery in app store not key
  • security/speed not key
  • No DRM involved
  • No APIs involved
  • Engaging with customers not key via push notifications

When to use native apps:

  • Speed is key (e.g. photo/video upload)
  • Security is key (e.g banking)
  • DRM support (e.g. spotify, netflix)
  • API availaibility
  • Push notifications (engage users)
  • discovery route is App Store (with Marketing budget)

When to use hybrid:

  • cross-platform ideology (PC, tablet, mobile)
  • light content distribution e.g. news
  • bypass approval process for tiny content updates
  • discovery route is App Store (with Marketing budget)
  • Push notifications (engage users)