# Anatomy of a Self-Service Application Platform

**Author:** kinlane  
**Canonical:** https://apievangelist.com/2011/04/08/anatomy-of-a-selfservice-application-platform/

In addition to the [growth in number of APIs](http://apievangelist.com/2011/03/08/programmable-web-3000-apis-and-growing/ "Growth in Number of APIs"), and the evolution of[BizDev 2.0](http://apievangelist.com/2010/10/07/biz-dev-2-0/ "BizDev 2.0"), there is a rise in self-service application platforms accompanying APIs, within many cloud platforms.

Platforms such as [Google Apps](http://apievangelist.com/2011/04/08/google-apps-marketplace/ "Google Apps") and Box.net are adding these self-service application development environments within their API ecosystem.

Each platform has its own approach to this type of self-service architecture, but there are many similar characteristics:![](https://kinlane-images.s3.amazonaws.com/apievangelist/self-service.jpg)

*   **Applications** - Interface for defining new application characteristics.
*   **OpenID / OAuth / User Resource Access** - Secure and granular access to users profile and resources.
*   **Development Environment** - Controlled, secure environment for developers to build applications in.
*   **Application Branding** - Branding of application and its profile on a platform.
*   **Application Approval Process** - Approval process for bringing applications live.
*   **Marketplace Environment** \- Public or private marketplaces for developers to publish applications and platform users to browse / add applications.

[Salesforce](http://www.salesforce.com "Salesforce") is building in-roads into the enterprise using this model, and [Facebook](http://www.kinlane.com/category/facebook/ "Facebook") has found success with social gaming using a similar approach.

APis have opened up new business development opportunities, self-service application platforms takes this development to a new level.