Citymapper

With API’s Good Things Can Happen

Posted on Updated on

I’ve been banging on for some time about how APIs are the future for brand apps. The idea is simple. If brands created APIs for their activities, other people would take that information and create far better apps (and at no cost to the business). Strangely, it’s something that government bodies, such as Transport for London seem to understand.  Two of the best apps currently, are API-based, combining open data with a great user experience:

Citymapper

It seems like everyone in London is using this app, and no one has a bad word to say about it. Citymapper has so many functions, in a simple UX, they are impossible to list here.  Even as a life-long Londoner, Citymapper has suggeseted transport routes that I have never considered (and often faster ones). The app achieves its goal through accessing a number of APIs from TfL as well as Foursquare data and delivered via their own algorithm. It’s a great example of how open data can be used to deliver an excellent user experience.

Whisk

Although it hasn’t achieved the success of Citymapper, Whisk is another example of a great, frictionless experience. After selecting a recipe, and the number of diners, it lists the price of the ingredients across a range of supermarkets. They use APIs from Tesco, Ocado, Waitrose and Asda. You then select which you want to buy, and the supermarket. The best part is that the app allows you to add these items directly to the shopping basket of your chosen supermarket’s app.

Given these examples, why doesn’t every brand create an API for their data and simply open it up to developers? The results will be a far better experience than they could ever create (not to mention many more users).