Posted on 05-08-2013
Does anyone else notice the evolution of the Twitter developer area? The site has taken a page from the LinkedIn playbook and become more about embeddable buttons, badges and widgets than about APIs.
Granted, you can click on documentation and get at the REST API v 1.1. I'm not saying this is a good or bad thing. I'm a big supporter of embeddable strategies for API providers. I think that evolution is very telling of Twitter's API strategy and what type of "developer" they want to support with the API.
Whether or not you agree with Twitter's overall API strategy, there is a lot to learn from their approach to API driven embeddable tools. I will produce more pieces aobut their approach to cards, timelines, buttons and other embeddable tools.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Adding The OpenEd API To The API Commons
- PR People For APIs
- I Will Be At API Days in Paris This Week, Will You Be There?
- Government Services Schemas With JSON-LD
- University of California Student Senate Submits Bill Stating Student Information Systems Must Have API
- Generating The Utility APIs I Need For Each Developer Portal
- An API For Your Github GeoJSON Stores
- Server Side API Templates On AWS Cloud Formation And OpenShift
- Hypermedia In The Wild: Amazon AppStream API
- API Search Endpoint Using Solr