Eric Wahlforss, CTO of SoundCloud, discusses dos and don'ts for building an API platform. He emphasizes keeping APIs simple (KISS), prioritizing developer experience through great documentation and communication, engaging the developer community, and being willing to fail and iterate. APIs should empower users by allowing them to use and share their own data, extend applications, and drive the network economy through a hyper division of labor.
1 of 29
Download to read offline
More Related Content
SoundCloud Platform Do:s and Don't:s at How To Web 2011
1. SoundCloud Platform
Do:s and 禽看稼t:壊
Eric Wahlforss CTO/SoundCloud
How To Web Bucharest 2011
5. What is an API?
Application Programming Interface Platform
Computers talking to each other
Exchange and manipulation of data
Essential part of the webs success
Adam Smiths wet dream
6. Hyper division of labour...
... and a network economy
Adam Smith (1723-1790)
13. Why API?
Allow people to use their own data...
... empower peopleeverybody loves talking about stuff
that empowers them ...
... which spreads the word about your service
Developer communitythe ultimate power users
Extend your applicationsolve niche use cases
Conceptual claritythe essence of your service
Inspired by http://strange.corante.com/2006/02/08/fowa-ten-reasons-why-you-need-to-build-an-api-shaun-inman
and http://www.readwriteweb.com/cloud/2010/08/the-new-api-movement-may.php
19. Do communicate
MOST IMPORTANT STEP FOR BUILD PRODUCT IS BUILD PRODUCT.
SECOND MOST IMPORTANT IS BUILD PERSONALITY FOR PRODUCT.
http://www.avc.com/a_vc/2011/09/minimum-viable-personality.html