Application developers are the customers of a Web API. Success is measured by how quickly app developers enjoy success using your API in their applications. And rapid adoption of a Web API is all about design.

A customer of ours once said it best - “...most open APIs start out as little more than raw, naked, features exposed to developers, and there is a big gap between a feature and a full-fledged service.” This e-book is about the capabilities ‘around the API’ that might be needed to ‘productize’, ‘monetize’, or ‘operationalize’ an API-based service.

As the API and apps economy continues to evolve, a design problem arises for API designers when internal systems are too complex to expose directly to app developers. The goal of an API Facade Pattern is to articulate those internal systems and make them useful and consumable by app developers.

Developers hate marketing. How do you bring your API to market and attract developers?

In April 2012, O'Reilly hosted a webinar by the authors of the O'Reilly book "APIs: A Strategy Guide." Video and slides are below. The book is an overview of API strategy for business executives and this webinar dives into both public and private API strategies. Thanks to O'Reilly, @daniel_jacobson, @gbrail and @danwoodscito. Courtesy of O'Reilly, a free chapter is posted here.

Telco Innovation with APIs - Need for Speed (Webcast)

Learn how Telcos need to change their business models and innovate beyond connectivity to remain relevant in a world changed by the exploding apps and API economy and the shift from voice-enabled to IP networks.

The video and slides for the webcast are below.

In 1995, Clayton Christenson coined the term Disruptive Innovations in his article titled "Disruptive Technologies: Catching the Wave."  His contention was that some new products or services that appear in the marketplace are so revolutionary that they render existing technologies obsolete.

Pages