SoundCloud Platform Do:s and Don't:s at How To Web 2011
- 1. SoundCloud Platform
Do:s and Don’t:s
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 web’s success
Adam Smith’s wet dream
- 13. Why API?
Allow people to use their own data...
... empower people–everybody loves talking about stuff
that empowers them ...
... which spreads the word about your service
Developer community–the ultimate power users
Extend your application–solve niche use cases
Conceptual clarity–the 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
- 15. Do KISS
http://37signals.com/svn/posts/3018-api-design-for-humans
- 16. “Time to integration”
Effort
in days
Plain vanilla API API Wrapper Great docs Sharekit Time
7 days 4 days 3 days 1 day
- 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
- 24. Don’t change
Inspired by http://www.readwriteweb.com/cloud/2010/08/the-new-api-movement-may.php
- 25. Do engage the community
http://mulqueeny.wordpress.com/2011/06/19/whats-the-point-of-a-hack-day/