It seems like somewhere between the 9,000 and 10,000 mark, API providers shifted their strategies even further toward providing a strong, sophisticated and appealing developer experience from initial contact on. In this four-part series, ProgrammableWeb looks at current practices in B2D from pre-release, through private beta, to API documentation and to ongoing developer engagement. Each article surveys current practitioners and includes a resource list for those wanting to step up their B2D game.
There has been so much talk about APIs and how they add additional revenue channels, create brand new partnerships, allow business partners to integrate with ease, and how they help with promoting your brand. But an important and underlooked aspect, which happens to be a byproduct of this new paradigm shift, is the faster innovation channel they provide.
An emerging trend is taking place where platforms are increasingly letting developers interact with their APIs through SDKs. Layer 7’s Scott Morrison comments on why this is happening and when it makes sense, noting that “SDKs make the service subordinate to the client, thus inverting a hierarchy that goes back to the early days of distributed computing.”
This guest post comes from Lorinda Brandon, Director, Customer Community at Mashery. You can follow her on Twitter or at Mashery.
This week’s Business of APIs conference in New York City brought together an agenda that highlighted some of the biggest trendsetters in the API industry today. As the industry continues to mature, trends are beginning to emerge as [...]
It’s a natural part of the API lifecycle for some to no longer be available. According to the ProgrammableWeb directory, about 13% of those that were once alive are now considered “deadpooled.” Of the companies tracked in the directory, Google tops the list with 33 discontinued APIs. However, it also has the most APIs. Percentage-wise, a handful of phone carriers seem most apt to kill APIs.
At the API Craft un-conference this week in Detroit, some of the best minds in the API business gathered to talk over the problems that plague us most. It was a unique event in that the agenda was set and run by the attendees in true meet-up fashion. Quakers will recognize the format – for the conference kick-off, the group sits in silence until someone is moved to suggest a session. You suggest it, you run it and anyone who attends your session also participates in it. The sessions are true whiteboard brainstorming activities, with the outcomes posted into Github for future reading.
What if you wanted to tackle a really big issue. How about freeing the 27 million people caught in “modern day slavery” through human trafficking (statistic from Wikipedia). Would you: A) Figure out the answer and build the biggest organization you could to solve the problem by yourself, or, B) Work with other organizations already working on this issue because cooperation is essential to solving this, or C) Build an API so the smart people who chose B could have an even bigger impact? Freedom Registry, founded by a group called Chad Dai (which stands for “joining hands” in Khmer) is already doing B, has just chosen C. They do just what their name says, provide a registry of organizations working on the issue. The Freedom Registry REST API allows developers to retrieve data from the registry.
It should be solely a good thing when APIs get mentioned in a popular business magazine. After all, APIs mean business, we wrote over a year ago. When the term, as geeky as it is, turned up in my Inc Magazine, it was the context and the wording that kept it from being entirely exciting.
Many APIs eventually find their way to the ProgrammableWeb deadpool. They end up there for various reasons: no business model, replaced by a newer service or ceased being useful. The most popular of these dead APIs are predominantly from two big tech firms: Google and Yahoo. Search and mapping make up the bulk of the functionality behind these 12 popular–but no longer available–APIs.
For those of us paying attention to APIs for awhile, we’re used to the question: what is an API? When I felt my answer wasn’t good enough, I made up a new acronym and started telling people that API stands for Apps, Partners, Income. Recently I cornered five API experts to ask them the same question. The video below shows how they answered the question.