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
- Someone Please Build My Open, Interactive, Portable, And Visual API Documentation Toolkit
- Dwolla Using Slate For An Evolved API Documentation Experience
- Crazy Mess Of URLs Across 400 Of The APIs In My Stack
- Reworking My API 101 Content: Consuming APIs
- I Need Help To Make Sure The Dept. of Agriculture Leads With APIs In Their Parks and Recreation RFP
- What Is The Biggest Challenge For Fraud Detection API SiftScience?
- Reworking My API 101 Content: Providing APIs
- What I Spent Ada Lovelace Day Working On
- An Outside-In Approach To Jumpstarting An API Effort At The University of Oklahoma
- Exposing Dictionaries From My API Collections