This is where I express my opinions when they're longer than 140 characters.

You can see examples of my short attention span on Twitter: @kerskine

You can also send me an email

12th July 2011

Post

HTML5 v. Mobile Apps - again

A mobile web site will get you 80% of the feature set you’d get with an application, but is faster and easier to develop.

I recently talked with a local city manager wanting to promote activities and wondered if a mobile app for iOS and Android would make sense to do. After listening to her requirements, I recommended against a native phone application and suggested creating a mobile web site because:

  • They were primarily providing event information (example, places to eat) with little need for interaction
  • They didn’t have a budget to fund an application
  • The information was going to change quickly, their timeframe was short (5-6 weeks), and it had little value after the event
Lots of bytes have been streamed (ok, trying to come up with a 21st Century answer to the old saw: “a lot of ink has been spilled.” For this, I apologize.) discussing whether applications, or the mobile web will rule the future.
  • Facebook Project Spartan is rumored to be an HTML5 application store, but more likely is a way for Facebook and their development partners to more quickly create services.
  • Baidu in China is developing a mobile OS that works by sending keywords in a search box to activate ‘apps’. An OS providing a clear channel to mobile web services would easy to deploy and maintain.
Google just announced mobile friendly features for their Sites service. Since I was already using Sites for two other projects, I took an hour and created this site.

Bottom line; while some people think that mobile apps are the only way to deliver service, mobile web sites can deliver solutions faster, getting feedback quicker, and giving your venture a leg up on in moving towards the next killer company.