Making an API Developers Love

1,777 views

Published on

Talk at the Business of APIs on Developer needs in APIs

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,777
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
14
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Making an API Developers Love

    1. 1. Making an API DevelopersLoveBy Frank Denbow@frankdenbow
    2. 2. Who I AmDeveloper, CarnegieMellonPicsicle iOS AppStartupThreadsStartup Weekend,Startup Digest15+ hackathons
    3. 3. Why An API MattersDeveloper community can bring Creativity New Markets Evangelists
    4. 4. Netflix: 20 Billion API calls/monthhttp://techblog.netflix.com/2011/02/redesigning-netflix-api.html
    5. 5. Twitter: 75% of calls in APIDeveloper community vital to the reachhttp://blog.programmableweb.com/2010/04/15/
    6. 6. High Level TopicsSolve Developer PainIncentivesCommitmentReliability
    7. 7. Solve Developer PainHelping developers build things faster, better
    8. 8. Example: CelebrityTwin.meFace.com: Facial recognition API, used inCelebrityTwin.me
    9. 9. Example: CelebrityTwin.meFace.com: Facial recognition API, used inCelebrityTwin.me
    10. 10. 66% Facial SimilarityExample: CelebrityTwin.meFace.com: Facial recognition API, used inCelebrityTwin.me
    11. 11. IncentivesAre your business goals in line with thedeveloper’s?
    12. 12. CommitmentIs your API a high priority? Can I count on you tomaintain and support the API as needed?
    13. 13. ReliableCan I count on your API to be available at alltimes?
    14. 14. Granular Topics of Interest Simplicity Standards (JSON, REST) Documentation Support
    15. 15. SimpleEasy to understand, predictable resources,speed to hello world
    16. 16. Example: FoursquarePredictable endpoints, versioning
    17. 17. StandardsUse common standards to make adoption easierand consistent. REST, JSON
    18. 18. DocumentationExample Code, API Explorer (Mashery), MultipleLanguages
    19. 19. Example: Mashery Explorer
    20. 20. Documentation: StripePayments APICode samples inmultiple languagesCopiable sample codeSupplement with livechat
    21. 21. Example: StripeGet started page has copiable code
    22. 22. Example: StripeCode in multiple languages
    23. 23. SupportBe available whenever you are needed
    24. 24. Support Example: TwilioSMS and TelephonyAPIWeekend SupportFulltime Evangelists
    25. 25. Thanks!@frankdenbow

    ×