I love the convenience of mobile applications but hate the way they re-invent the wheel and are killing the Web. What can be done about it?
I’m in love with the mobile Web
I’ve been smitten with the Web since first venturing out on the information superhighway back in the nineties. This love affair is taken to a new level with the advent of the mobile Web. As an incurable information junkie, having access to news is on the move is great. Using location based services like Google Maps is fantastic, on foot, bike or in the car. I love nerdily scanning barcodes to read Amazon book reviews while browsing the shelves in bookshops, much to Tim Waterstone’s annoyance. And it can be great to have wikipedia in your pocket to settle arguments down the pub.
I hate the mobile Web too
But there’s a big problem with all this appy clappy mobile fun, it’s killing the Web through fragmentation, both for producers and consumers of information. Let me explain.
One of the great things about the Web is that you there is one app to rule them all; a “killer app” called a Web browser. There are several flavours, but they all basically do the same thing using similar technology: they let you surf the Web. One software application (a browser), gives you access to an almost infinite number of Web applications. Wonderfully simple, wonderfully powerful – we’ve got so used to it we sometimes take it for granted.
Now compare this to the mobile Web where each page you visit on a mobile suggests that you download an app to read it. Where there used to be just one application, now there are thousands of glorified “me too” Web browsers apps many of which have re-invented the Web, badly.
Consider the applications in the table below and illustrated on the right. They are all accessible from a Web browser on one of the “four screens ”: desktop, mobile, tablet and smart-TV:
|Native mobile app||Purpose||Web app|
|Amazon mobile||Online retailer||Amazon.com|
|BBC News mobile||News and propaganda||news.bbc.co.uk|
|The Economist mobile||More news and propaganda||economist.com|
|eBay mobile||online garage sale||ebay.com|
|Flickr mobile||photo sharing||flickr.com|
|Guardian mobile||Even more news and propaganda||guardian.co.uk|
|Google Reader mobile||Feed reader||reader.google.com|
|Google Maps mobile||Maps and navigation||maps.google.com|
|MetOffice mobile||UK Weather||metoffice.gov.uk|
|PostOffice mobile||Postcode / Address finder||royalmail.com/postcode-finder|
|Google Search mobile||Search engine||google.com|
|Google Translate mobile||Language translator||translate.google.com|
|Twitter mobile||Entertaining time-wasting application||twitter.com|
|WordPress mobile||Blogging tool||wordpress.com|
As you can see, users are encouraged to download, install, understand and maintain sixteen different apps to enjoy this small part of the mobile Web. And this is just the tip of the iceberg, there’s bucket-loads more apps like this in Google Play and the App Store. As a user, you could just use a mobile Web browser on your phone, but you’ll be discouraged from doing so. We’ll return to this later.
Producers and consumers both suffer
As well as being a pain for users who have to manage hundreds of apps on their phones and tablets, the pain is magnified for producers of data too. Instead of designing, building and maintaining one Web application to work across a range of different screens (a challenging but not impossible task), many have chosen to develop lots of different apps. Take twitter for example, in addition to the desktop and Web apps, twitter currently makes no fewer than five different applications just for tablets and phones:
So a challenging task of delivering content onto a range of different devices has now been transformed into an almost impossible task of building and managing many different apps. It’s not just Twitter, Inc. that chooses to play this game. Potentially any company or organisation putting data on the mobile Web might consider doing this by employing an army of android, blackberry, iPhone and windows developers on top of the existing Web developers already on the payroll. That’s good news for software engineers, but bad news for the organisations that have to pay them. Managing all this complexity isn’t cheap.
Not Appy: How do we get out of this mess?
In the rush to get mobile, many seem to have forgotten why the Web is so successful and turned their back on it. We’ve re-invented the wheel and the Web browser. I’m not the first  and certainly not the last  to notice this. Jonathan Zittrain even predicted it would happen [3,4] with what he calls “tethered devices”. One solution to this problem, as suggested at last months International World Wide Web conference in Lyon by some bloke called Tim, is to develop mobile Web apps rather than native mobile apps:
There are lots of examples of this. Sites like trains.im provide train times via a simple Web-based interface, no app required. Many Web sites have two versions, a desktop one and a mobile one. Wikipedia has a mobile site at en.m.wikipedia.org/wiki, Flickr at m.flickr.com, The Economist at m.economist.com, BBC at m.bbc.co.uk/news and so on. But in many cases these sites are poor cousins of the native mobile apps that software developers have focused their efforts on, diluting their work across multiple apps and platforms.
- everything that’s already in the world when you’re born is just normal;
- anything that gets invented between then and before you turn thirty is incredibly exciting and creative and with any luck you can make a career out of it;
- anything that gets invented after you’re thirty is against the natural order of things and the beginning of the end of civilisation as we know it until it’s been around for about ten years when it gradually turns out to be alright really.
The mobile Web makes me suspicous because many apps re-invent the wheel. I’ve argued here that it is against the natural order of the Web, we’ve waved goodbye to the good old Web  and its the beginning of the end. I really hope not, it would be a tragedy to carry on killing the Web as it’s given us so much and was designed specifically to solve the problems described above. Let’s hope native mobile apps gradually turn out to be alright really.
- Gary Marshall (2011). Could smartphone apps be taking us back to the days of “best viewed with … ”? Net Magazine
- Jason Pontin (2012). Why Publishers Don’t Like Apps: The future of media on mobile devices isn’t with Apps but with the Web Technology Review
- Jonathan Zittrain (2007). Saving the internet. Harvard Business Review, 85 (6) PMID: 17580647
- Jonathan Zittrain (2009). The Future of the Internet: And How to Stop It Penguin, ISBN:014103159X
- Hamish MacKenzie (2012) Web 2.0 Is Over, All Hail the Age of Mobile, Pandodaily