Posted on 05-25-2012
Here we are going into June, and I still don’t see a publicly available Pinterest API. Jay Yarow wrote in Business Insider back in February, "Pinterest's API Is Coming Soon, And VCs Are Super Excited" and Adam Duvander wrote in ProgrammableWeb, "Pinterest API: Coming Soon or Already Here?".
There is also a reply to a Quora thread by Yashh Nelapati, Lead Engineer at Pinterest from May 2011, saying the API is 2-3 weeks away. It’s now a year later and there is no official API (there is a Rogue API).
Business Insider says, Pinterest fears having a "Twitter problem”. Meaning that when Twitter released its API, it was still an immature company, allowing developers to build applications with features that it was missing--then Twitter matured, and it wanted to control its platform, it began adding building its own features and poaching from the Twitter API ecosystem.
So why not learn from Twitter and other APIs, and use the appropriate API building blocks to address this:
- Branding Guidelines - Establish branding guidelines that clearly lays out what apps that use Pinterest API should look like
- UI / UX Toolkit - Provide a UI / UX toolkit like Twitter Bootstrap that sets the tone for applications built on the API
- Roadmap - Provide a real-time and transparent roadmap that developers can use to help keep their development efforts in line with Pinterest
- Developer Framework - Establish a developer framework outlining opportunities for developers to become stronger members of API community, also introducing possible investment and incubation of most success or important features
- Events / Meetups - Establish a roadshow or network of meetups that brings developers together and makes them part of the Pinterest API community
These are just a few of the ways Pinterest could establish a solid business strategy for their API that would not only protect developer interests, it would establish the Pinterest API as an external research & development department, with a built in incubation component.
Pinterest has already missed out on a year of developers innovating on their platform. Why continue holding back innovation? Establish a flexible API business strategy that allows for you to learn from the mistakes made by Twitter, and become the platform VC’s are looking for you to become.
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