Posted on 06-29-2012
I’m on a roll tonight, writing about tension between API owners and consumers. After some driving around California this week, I’ve had time to ponder three recent episodes with Netflix, LinkedIn and Craigslist. This is my last post tonight, and was inspired by a Tweet from James Watters (@wattersjames):
I thought about his Tweet for the last week and he’s right. While it’s easy to run and get our pitchforks in these situations and demonize API owners, or bitch about how much API developers suck, this all is just the beginning of something greater--the API economy.
Trade wars are an active part of our global economy, and with the growth in the number of APIs, the tension between API owners and consumers is only going to grow. We can’t see them as black or white, we will have to evaluate them on a case by case basis.
I think my three posts tonight reflect the potential diversity in issues.
- Netflix - The movie industry isn’t quite ready for public APIs, other change required first, sorry developers
- LinkedIn - A little communication can go a long ways in how we approach terms of service violations
- Craigslist - Sometimes the market just demands that you need an API, allowing you to tame scrapers
James Watters Tweet definitely made me look at this issues in a different light. And that is what I love about this space, it is constantly changing, forcing me to constantly reevaluate how I see things and tell stories in the space. And even before I can finish this post John Sheehan (@johnsheehan) has got me thinking about another angle all three of these stories share:
@kinlane all 3 posts hit on one thing: API use has to drive value for the company providing it not just the consumer. Not the case for these— John Sheehan (@johnsheehan) June 29, 2012
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