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
- On Being An API Broker For Hackathons
- Are You A Hypermedia Pragmatist?
- Do You Know That Hypermedia Is A Better Solution For Discovery Than APIs.json?
- API Service Idea: API Via Excel From Within Corporate Email
- With Number Of APIs Continuing To Grow Account Automation Will Be Key
- History Of APIs: NOAA APIs Have Been RESTful For Over 20 Years
- Understanding More About The Web Communications Platform Respoke
- Swagger Definition Driven Sandbox And Simulation Data Templates For APIs
- Swagger API Definition Mapper
- Moving Beyond Just The PDF With A Single Page Report (SPR)