Your API is So 2006 - Dreamforce 2011

  • 3,527 views
Uploaded on

Don't expect internal, partner, and open developers to build 2011 apps and integrations with 2006 API formats, chatty protocols and outputs. PuSH! RESTful! JSON! oh my.

Don't expect internal, partner, and open developers to build 2011 apps and integrations with 2006 API formats, chatty protocols and outputs. PuSH! RESTful! JSON! oh my.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
3,527
On Slideshare
0
From Embeds
0
Number of Embeds
5

Actions

Shares
Downloads
41
Comments
0
Likes
6

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
  • ,,
  • [ go over bullets ]Sample calls are no longer static pieces of documentation that can get outdated. With live API calls available within the documentation, you are guaranteed never to have non-functional outdated examples.

Transcript

  • 1. Your API is So 2006
    Delyn Simons
    @delynator, @mashery
    #df11
    August 2011
  • 2.
  • 3.
  • 4. <you think?>
  • 5.
  • 6.
  • 7. 7
    Accelerating Growth of APIs
    Total APIs over time
    Based on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011
  • 8. APIs since 2006
  • 9. “Their API is so
    2006.”
  • 10. “Their API is so
    awesome.”
  • 11.
  • 12. Who are developers?
    What do they want?
    How can you help them get what they want?
  • 13. Developers are 21st century craftsmen
    Photo Credit: flickr.com/tom_w_bn
  • 14. and women
    Photo Credit: © Eric Roth
  • 15. Developers build stuff
    Photo Credit: flickr.com/mashery
  • 16. Developers solve problems
    Photo Credit:
    flickr.com/delynator
  • 17. Developers
    tinker and prototype
    Photo Credit: flickr.com/techcrunch
  • 18. Developers
    change the game
  • 19. Developers rely on tools to practice their trade
    Photo Credit: © Eric Roth
  • 20.
  • 21. Who are developers?
    What do they want?
    How can I help them get what they want?
  • 22. Tools and terms of service they can rely on
    Photo Credit: © Eric Roth
  • 23. API Integration Pain Survey
    Survey conducted by YourTrove, Inc. August 2011
  • 24. Results Chart by ProgrammableWeb. Survey conducted by YourTrove, Inc. August 2011
  • 25. Treat your API like a core part of your business
    “It’s not what we set out to find, but it deserves to be said again: API providers are doing a horrible job of serving their developers well. This is a huge problem.”
    Survey conducted by YourTrove, Inc. August 2011
  • 26. Who are developers?
    What do they want?
    How can I help them get what they want?
  • 27. Tools and terms of service they can rely on
    Photo Credit: © Eric Roth
  • 28. “Their API is so
    2006.”
  • 29. Modern API management trends
    Please Drop the SOAP
    Chat Less, Do More
    Interactive Documentation
    Growing of internal and partner API usage
    Mainstream API Success
  • 30.
  • 31. Photo Credit:
    flickr.com/delyn
  • 32. REST vs. SOAP: Simplicity wins again
    32
    Distribution of API protocols and styles
    Based on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011
  • 33. 33
    REST vs. SOAP: Simplicity wins
    Distribution of API protocols and styles
    Based on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011
  • 34. JSON Rising: 55% of new APIs support JSON
    34
    Percentage of new APIs with JSON support
    Based on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011
  • 35. 20% of new APIs support only JSON
    35
    Percentage of new APIs with only JSON support
    Based on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011
  • 36. 1 in every 5 new APIs: “goodbye XML”
    36
    Percentage of APIs with XML support
    Based on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011
  • 37. Modern API management trends
    Please Drop the SOAP
    Chat Less, Do More
    Interactive Documentation
    Growing of internal and partner API usage
    Mainstream API Success (upside + downside)
  • 38. Chat Less, Do More with Push Notifications
  • 39.
  • 40.
  • 41. Modern API management trends
    Please Drop the SOAP
    Chat Less, Do More
    Interactive Documentation
    Growing of internal and partner API usage
    Mainstream API Success (upside + downside)
  • 42. Mashery I/O Docs
    Interactive Documentation
    • All methods and parameters clearly displayed
    • 43. Automatic key/credential retrieval
    • 44. Ability to make live API calls within documentation
    • 45. API call, HTTP header and response displayed
    • 46. Useful for exploring, learning, testing and debugging
  • 47.
  • 48. Modern API management trends
    Please Drop the SOAP
    Chat Less, Do More
    Interactive Documentation
    Growing of internal and partner API usage
    Mainstream API Success (upside + downside)
  • 49. Restructuring for Internal, Partner Growth
  • 50. Modern API management trends
    Please Drop the SOAP
    Chat Less, Do More
    Interactive Documentation
    Growing of internal and partner API usage
    Mainstream API Success
  • 51. APIs since 2006
  • 52. Mainstream Success
  • 53. Mainstream Success – Who’s Next?
  • 54. Modern API management trends
    Please Drop the SOAP
    Chat Less, Do More
    Interactive Documentation
    Growing of internal and partner API usage
    Mainstream API Success
  • 55. Thank you!Your feedback is a gift.
    Delyn Simons
    @delynator, @mashery
    #df11
    August 2011