Hey Mobile, Thanks for All the APIs

Adam DuVander
Feb. 01 2011, 12:00AM EST

There are a number of factors coming together to fuel the growth of APIs. Without a doubt, one is the corresponding growth of mobile devices and the distribution of services across multiple platforms. An API is often required to create one native mobile application and becomes incredibly important when supporting many devices. Sometimes these private APIs are made public, sometimes they aren't.

If a mobile application, such as a native iPhone app, provides content or shares data, there's a good chance it connects to a web API for exchanging data. For example, popular photo sharing app Instagram maintains its own contact network and has to let users know when there are new photos to see. Also, whenever a photo is added, Instagram stores it on its servers, tied to the appropriate account. This exchange of data requires the Instagram API, which we reported is meant to be private. But its mere existence was thanks to the app that required it.

Similarly, book recommendation service Alibris recently launched its iPhone app and opened its API the same day. Why? The Alibris API essentially came free with the app because it was required to send search queries and results between its servers and the iPhone.

But don't mistake an API for a developer community. That's the message Instagram sent when it squelched some app using its private API. Though it is technically possible to use the API, the company was wary of setting an interface that it wouldn't be able to change once third party apps count upon it.

Of course, there are often several developer audiences for an API. As Daniel Jacobson explained when he worked for NPR (Jacobson later moved on to Netflix), the public radio company used its API to create a mobile site and apps for Android, iPhone and iPad. The multiple platforms were coded by different teams, but all of them used the NPR API. The outcome for NPR is it doubled its traffic in a year. Mobile users--and the multiple platforms--created a need perfectly addressed by an API.

A flagship app isn't required to see the impact mobile has had on APIs. Over the last 18 months, geo-related services have moved from pure JavaScript interfaces to those that provide raw data. MapQuest led the way when it shared its driving directions in 2009. With its MapQuest Directions API, developers can provide driving directions to their users on any platform--iPhone, Android, Blackberry, or any other, including the plain ol' web.

Google also provides its Google Directions API after a number of years of only offering the service via JavaScript. Google also has its Google Maps Elevation API and other services that separate the data from the technology upon which it is used.

Whether in support of an official mobile application, or in support of any developer's app, APIs are fueling mobile--and mobile is playing a huge role in the growth of APIs.

Adam DuVander Hi! I'm Developer Communications Director for SendGrid and former Executive Editor of ProgrammableWeb. I currently serve as a Contributing Editor. If you have API news, or are interested in writing for ProgrammableWeb, please contact editor@programmableweb.com Though I'm a fan of anything API-related, my particular interest is in mapping. I've published a how-to book, Map Scripting 101, to get anyone started making maps on websites. In a not-so-distant past life I wrote for Wired and Webmonkey.

Comments

Comments(13)

[...] Remember as you brainstorm that API’s aren’t a one-way thing. It came up last night, and again (in my head) when I was reading an article on my favorite API web site, ProgrammableWeb, about the mobile drivers behind the explosion of APIs. [...]

[...] Similarly, the NPR API is used by several of the public radio organization’s websites and applications. Internal use is large enough that it’s a major audience consideration. Further, we’re seeing many launch APIs at the same time as mobile apps, because the API essentially comes along with the app. We looked more at this in Hey Mobile, Thanks for All the APIs. [...]

[...] Even though Alaska Airlines was one of the first airlines to offer an iPhone application, allowing travelers to check-in and use their phone as mobile boarding pass, early efforts were essentially just “screen-scraped” from the companies website, providing a very poor user experience, not really delivering on the process of the mobile web. Since you’re a ProgrammableWeb reader, you can probably guess what the company needed. After all, mobile has fueled API growth. [...]