Posted on 03-27-2011
I just finished reading two more posts on the recent changes to the Twitter API terms of service. There are a lot of opinions on whether Twitter was right or wrong in their approach to reign in their developer community. I understand Twitter wanting to take back some control over its ecosystem and monetize its world. I do not understand why people are demonizing Open APIs or the developer community. Both made Twitter what it is today. I wanted to put some thoughts down on how I'd engineer a more sensible approach to the Twitter API ecosystem. Brand Control: Twitter needs to keep expanding its branding resource area where users can come to get CSS, HTML, images, widgets, borders and many other higher quality assets that can be used by the community and maintain a quality level of brand control for Twitter. API access and usage. Let's create some free and paid access levels:
- Developer - A free low volume access level that allows developers to play with the API, but only allows a minimum number of API calls per day.
- Professional - A slightly higher level of access meant for API consumer that may be building an application, but probably used just for professional purposes.
- Business - API access for businesses that use Twitter for their own brand, and require a higher level of API requests, but are willing to pay for it.
- Commercial - A pay-for-what-you-use model, in true cloud computing fashion, with the possibility of volume discounts.
- Academic - A free research-based access account for scholars to use in their academic projects.
- Rethinking the NPR API Ecosystem (apievangelist.com)
- The API is Dead. Long Live the Protocol. (buddycloud.com)
- Twitter, Lendle and the State of the Open API Ecosystem (apievangelist.com)
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Swagger Visualization Layer Using D3.js
- Establishing Common Dictionaries That Industries Can Use In Their API Design
- Top 5 Most Popular Themes On API Evangelist In 2014
- Query Parameter Determining Which Fields Are Queried For API Call
- Now Our Development Environment Is Now Containerized And Scalable Like Our Production Environment
- Guest Post: Let Our Sponsors Blow A Little Smoke Up Your Ass
- API Discovery Continues Its Move Into The IDE With Eclipse Che
- Evolving Beyond Just Resources Towards A More Experience Based API Design
- Another View of The API vs. Data Download Model
- If You Have A Publicly Available Mobile App You Have a Public API