Your SlideShare is downloading. ×
Your API Sucks! Why developers hang up and how to stop that.
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Your API Sucks! Why developers hang up and how to stop that.

7,208
views

Published on

Part 6 in our series of API Best Practices Webinars - on Developer Adoption- by @landlessness and @earth2marsh

Part 6 in our series of API Best Practices Webinars - on Developer Adoption- by @landlessness and @earth2marsh

Published in: Technology, Business

1 Comment
3 Likes
Statistics
Notes
  • <br /><iframe width="350" height="288" src="http://www.youtube.com/embed/twWnGnQG_1s" frameborder="0"></iframe>
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
7,208
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
54
Comments
1
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Your  API  Sucks  Why  developers  hang  up  and  how  to  stop  that.  Rapid  API  Workshop  Marsh  Gardiner      Brian  Mulloy  @earth2marsh      @landlessness    
  • 2. @earth2marsh @landlessness
  • 3. Rapid API Workshop Webinar SeriesMapping  out  your  API  Strategy    PragmaAc  REST:  API  Design  Fu  10  PaJerns  of  Successful  API  Programs  API  Metrics  –  What  to  Measure?  API  Technology  &  OperaAons  Today:  Your  API  Sucks!  PCI  Compliance  and  APIs    
  • 4. THIS TALKIN A NUTSHELL•   User  experience  wins  •   API  users  =  developers  •   Developer  experiences  (generally)  suck  •   But  they  don’t  have  to…  
  • 5. #betterapis!
  • 6. Four simple rules1. Give developers every reason to build2. Make them successful faster3. Dont violate their trust4. Listen
  • 7. Hangup Reason #1Why would I use your API?
  • 8. Why  did  you  build  an  API?  
  • 9. Four simple rules1. Give developers every reason to build2. Make them successful faster3. Dont violate their trust4. Listen
  • 10. Simple  things  should  be  simple.  Complex  things  should  be  possible.              —  Alan  Kay  
  • 11. Krug says:1. People don’t read pages. They scan them.2. People don’t make optimal choices. They satisfice.3. People don’t figure out how things work. They muddle through.
  • 12. Hangup Reason #2You’re making this too hard.
  • 13. TTFR Time   To   First   Request  
  • 14. Four simple rules1. Give developers every reason to build2. Make them successful faster3. Dont violate their trust4. Listen
  • 15. Hangup Reason #3Are you going to support me?
  • 16. Four simple rules1. Give developers every reason to build2. Make them successful faster3. Dont violate their trust4. Listen
  • 17. Your  API  is  a  product.  Treat  it  that  way.  Your  developers  are  your  customers.  
  • 18. Why  is  this  so  hard?  
  • 19. Why  does  Freemium  work?  
  • 20. Do  it  beIer  
  • 21. SOAP   POST /InStock HTTP/1.1 Host: www.example.org Content-Type: application/soap+xml; charset=utf-8 Content-Length: 299 <?xml version="1.0"?> <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"> <soap:Header> </soap:Header> <soap:Body> <m:GetStockPrice xmlns:m="http://www.example.org/stock"> <m:StockName>IBM</m:StockName> </m:GetStockPrice> </soap:Body> </soap:Envelope>
  • 22. Why  REST  is  winning:  http://api.twitter.com/1/statuses/public_timeline.json
  • 23. Your  engineers  may  be  great  at  wriAng  the  code  behind  your  API.    Are  they  great  at  designing  for  API  adop<on?    
  • 24. POST !https://api.bluevia.com/services/REST/Advertising_Sandbox/simple/requests?version=v1!
  • 25. Opacity  is  inscrutable.  (Also,  unforgivable.)  Give  devs  the  informa<on  they  need  to  succeed.  
  • 26. Good  PaIerns  
  • 27. Put  yourself  in  their  shoes.  
  • 28. Four simple rules1. Give developers every reason to build2. Make them successful faster3. Dont violate their trust4. Listen
  • 29. Rapid API Workshop Webinar SeriesMapping  out  your  API  Strategy    PragmaAc  REST:  API  Design  Fu  10  PaJerns  in  Successful  API  Programs  Today:  API  Metrics  –  What  to  Measure?  API  Technology  &  OperaAons  Your  API  Sucks!  Next:  PCI  Compliance  and  APIs  
  • 30. Tired I am. REST I must.
  • 31. THANKS!    Send  ques<ons,  examples,  and  ideas  to  @apigee   Marsh  Gardiner      Brian  Mulloy   marsh@apigee.com      brian@apigee.com   @earth2marsh      @landlessness