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
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API
- Relationship Between APIs And Containers
- Real-time and Visualizations Will Be Key in Financial API Deployments
- Notification Focused Startups Within Leading API Ecosystems