Open Distribution Platforms

Open APIs are a no-brainer in the IT landscape of 2010. I have been talking myself to hundreds of people over the last years, trying to convince everybody to build and publish an API. However I’d like to share some thoughts on what I believe is next. Will we still be talking about APIs, API management, etc in a few years from now? What role do APIs play in a multi-channel distribution play?

Not having an API today is like not having a website in the 90s. There are tons of great use cases out there: e.g. ebay – $7bn worth of items on ebay were added through APIs (Mark Carges, CTO ebay). Twitter, Amazon, Salesforce.com and many other best practices. However, we have also learned that building an API is relatively easy, but its distribution is not. Not everybody is as successful as Amazon Web Services with over 300,000 customers using their API, or Google’s APIs which are in the millions. The key topic of this article is therefore to look into how the distribution issue can be solved.

First, I’d like to look at Web Service Business Models and their evolution:

  1. We initially had websites which added an API to their system, however the website remained the core traffic driver.
  2. In some successful cases, the API traffic has actually overtaken the website traffic. A good example is Twitter or Amazon WS.
  3. Recently we have seen that websites have become web services, meaning the API is the product. The website serves as no more than a marketing tool, all value add is delivered through the API. Examples are Twilio, Zemanta, Strikeiron or Xignite.
  4. But the newest trend is when Web Services become Open Platforms, when applications turn into platforms.

Open Platforms are the lever that allows to create a network effect which is required to succeed in the new distributed ecosystem.

Why should enterprises care about?

  1. Because it is critical to be indispensable in this new ecosystem
  2. New business models can be adopted and especially business opportunities shall be exploited
  3. They foster innovation
  4. And they are a new (future) model for software acquisition
  5. Last but not least, they increase customer engagement.

An overview of this new system shows the graphic below. I call it the “Open Computing Value Chain“. The sourcing part can be seen on the left where direct access to APIs and indirect generation of additional value add is derived from a developer community. On the right side I split between direct channels, such as the website or open APIs, and multi-channel platforms, such as Enterprise Platforms (Enterprise App Stores) and Consumer (mobile) App Stores which serve B2B as well as B2C customers respectively. In the end we are talking about multi-channel management represented in multi-channel platforms which will leapfrog pure API strategies in its ability to distribute to the market and increase its reach dramatically.

At Booz & Company we also call this phenomenon Social Apponomics, in which a Social OS allows the convergence of cloud functionality. The big trend is expected towards monetization. Expect only 2 to 3 social networks dominating the social landscape and a strong commercialization of social sites. While the social networks were mainly focusing on brand building today, within the next 18 months social sites will become commercial portals and e-commerce will be hosted on social sites.

Expect a “gold rush” just as we have seen it in consumer app stores where Apple has been the game changer beginning of 2009. After some early pioneers like Handango or Pocketgear, we are seeing hundreds and thousands of App Stores today, asking themselves the question “how to get a place in the game”. Almost every of the over 700+ mobile operator worldwide are thinking of launching an App Stores. This might not make sense for most of them, but it shows the upcoming abundance of players to come:

  1. Software OS vendors like Microsoft, Google but also smaller vendors like Splunk have an app store
  2. Vertical players like Apple or Nokia
  3. Mobile OEMs like RIM/Blackberry, LG, Samsung, Motorola
  4. PC OEMs like acer, Dell or IBM
  5. ISVs and fixed / mobile carriers from T-Mobile to Vodafone and Orange
  6. Independent Stores like GetApp or Mobango

In the end, all of the above have different agendas but they are competing for the same audiences – developers and customers.

On the Enterprise Platform site we have a similar picture, with Enterprise Platform Enablers like Jive Software, IBM Enterprise Application Integration or Jackbe. But also full scale Enterprise “App Stores” like IBM Smart Market, Intuit and more developer platforms and PaaS-plays like the Alcatel-Lucent Open API service, Google App Engine, Salesforce/Force.com or Windows Azure. The common goal of all is to generate competitive advantages.

With such an abundance of players it is critical to ask what the key success factors to attract both developers and customers are.

  • For attract developers, the quality of technical support, high reach and exposure (through the platform) and a generous/fair business model are important.
  • Customers are seeking powerful brands and marketing, broad and diverse offerings, a quality storefront and an easy payments engine.

The “right to win”, will have these companies that leverage their exisiting capabilities and assets in a coherent way to determine their best strategic play.

Key messages I wanted to bring across:

  • We’ve understood that APIs are important
  • APIs are easy to build but distribution is key
  • Enterprises need to engage in social networks
  • Open platforms deliver the network effect which is critical to succeed
  • B2C and B2B app stores are a preferred digital distribution model
  • Enterprises need to leverage their existing assets and capabilities

Thanks to Sam Ramji from Apigee/Sonoa who organized the API Open Mic Night where I presented these ideas first.

Enhanced by Zemanta

Cloud Market Sizing – AWS

How big is Amazon’s cloud computing business? To determine an estimate on the cloud computing market size it certainly helps to look at Amazon’s financials for their web services businesses. AWS is one of the leading players in cloud computing. Although still a relatively small division of Amazon’s business, AWS had a net income of $58.2 million in 2010 and will make $100.7 million in 2011. By 2014, AWS expects $393 million, or 83 cents a share. Om Malik wrote an interesting analysis about the report that was conducted by UBS Investment Research analysts Brian Pitz and Brian Fitzgerald.

Earlier market sizing efforts by IDC came to the following conclusions:

  • The total global cloud market in 2010 will be $22 billion and $55 billion in 2014.
  • The total servers and storage account for $5 billion-to-$6 billion in 2010 and $15-to-$20 billion in 2015.
Enhanced by Zemanta

API Marketing

Not a day goes by that a major Internet business is releasing or updating their (Web) API. Web Services have become one of the key strategies for Internet businesses these days. This is not only happening in 2009, API technology and its standards like SOAP and later REST have been used for years. However what is new is that this technology is not only seen as a technical enabler but as a commercial enabler for new business opportunities.

Caterina Fake, co-founder of Flickr, called it BusDev 2.0 already in 2006 (http://bit.ly/K0eJk). Kipp Bodnar just wrote a very good blog post on APIs as the new marketing platform (http://bit.ly/9wg4d): “If I was a CMO, I would take some of my marketing budget from traditional media buys and creative work and use it to hire a small group of extremely talented web developers that have experience using API’s to develop simple and easy to use web applications.” I couldn’t agree more. Providing access to their services via APIs has been a major winner for several companies: Salesforce, Twitter, Flickr, NPR, just to name a few. These companies have managed to gain platform leadership – and their API plays a crucial role in that. And many other companies are following: from e-commerce over content & media, business services to the government (for the latter one I hope that European governments are at least watching closely what is happening in the US in terms of government 2.0).

What larger Internet companies have been doing for some time now, many mid-tier and smaller companies are following. Launching an API has not only become a core part of the IT strategy, new developer tools and the rise of RESTful Web Services have made it easier and faster to build an API in the first place. Many Internet businesses however still haven’t done the switch from an open API (without access control) to a managed API (with access control). The provisioning of key management systems, monitoring, analytics and billing systems is not easy, but it is the key to exploiting this technology as a revenue driver. My company 3scale enables companies to leverage their API through a SaaS based API management solution that can be implemented in just a few hours, allowing any kind of Internet business to manage their API.

What are the key benefits of providing a managed API:

  1. Reach & Relevance: With the size of the web reaching 1 trillion unique URLs, there are good and bad news: although there are every day more possibilities to promote products & services, it is also always more difficult to get noticed. APIs provide a key enabler that allows Internet businesses to go beyond their own website and try to be visible on every other website.
  2. New distribution channel: APIs can simply be seen as a new distribution channel. While the original website is usually the main channel, APIs allow to reach, promote and sell the company’s content or functionality to other websites. The main difference to RSS however is that the content user (the mashup) can be identified, monitored and charged for their usage.
  3. New business model: APIs allow a new way to create new business opportunities. I usually differentiate between a direct or indirect business model, meaning an either direct way to monetize the content or functionality usage of a user (by hit or flat rate) or simply an indirect way of commercialization, meaning not being charged for the actual usage, but leveraging traditional business models through increase of reach.
  4. Innovation & Synergies: Due to flexible integration and re-usage of content & functionality on the web, APIs foster innovation. The next major evolution cycle of the Internet will be a web, mashed-up from various sources of raw data, exploiting synergies to create something new with additional value add.

Looking at data from Programmableweb.com shows a strong increase of available APIs (1278 at the time of writing and doubling every 12 months) and even more Mashups (3905), however the real amount of APIs is likely to be much higher and the growth rate is accelerating. At 3scale, we are looking at these trends very closely and believe that we can contribute to the thriving ecosystem of the programmable web.

Further reading:

 

Reblog this post [with Zemanta]