To App or Not to App? The debate between developing lower-cost mobile websites versus higher-cost mobile applications is contentious. A mobile website can render on all devices and mobile operating systems — no need for separate versions or updating for new operating-system releases. Mobile apps, on the other hand, provide an easy user experience and allow access to local device tools (GPS, camera, accelerometers, etc.). Just to confuse things, there are a few HTML5 operators that allow mobile websites to provide a more app-like experience. So which way is the mobile world leaning: app or site?
To App or Not to App? That’s a Good Question.
Well, it depends on how the customer will consume the content.
According to Dave Gwozdz, CEO of Mojiva, in an article for Ad Age Digital:
Content and demographics could range from teenage girls to senior citizens, fashion to travel to technology to food, men’s and women’s. Would building iPhone, iPad and Android apps be the blanket answer? It’s not.
He’s absolutely right, of course. The audiences are not the same, so consumption will be different. An iPad app makes sense for a high-end fashion or travel publication (where users expect the most detailed imagery), but why build an iPad app for a sports site, where 90% of the usage is checking scores or fantasy league standings? In many cases, the question to raise is, why develop an app when a mobile website will do just fine?
As HTML5 comes of age and JavaScript (node.js) goes mobile, the lines between mobile-friendly websites and mobile apps will continue to blur. For the developers out there, the answer to mobile web or app remains dependent on how the content will be consumed and by who.