Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
How To Make APIsThat Don’t SuckMichele TitoloSr. Mobile Engineer, Prolific Interactive@micheletitolo
@micheletitolo
@micheletitolo
@micheletitolo
An “API” for the sake of this presentationwill refer to any way your software cancommunicate with another piece of softwar...
@micheletitolo
Lesson 3:Follow Conventions@micheletitolo
@micheletitolo
Lesson 3 Summary• Conventions save time• Conventions save money• Conventions make developers happy@micheletitolo
@micheletitolo
Lesson 2:Don’t be clever@micheletitolo
@micheletitolo
• Be smart• Be concise• Don’t be cleverLesson 2 Summary@micheletitolo
@micheletitolo
Lesson 1:Document, Document,Document@micheletitolo
@micheletitolo
Lesson 1 Summary• Document• Document• Document@micheletitolo
@micheletitolo
Lesson 0:Expect the Unexpected@micheletitolo
@micheletitolo
Lesson 0 Summary• Follow conventions• Don’t be clever• Document, document, document@micheletitolo
Resources• Matt Gemmell - API Design• Google Tech Talk - How To Design A GoodAPI• Stackoverflow - What Do You ConsiderGood...
Thank You!Michele Titolo@micheletitolo
Upcoming SlideShare
Loading in …5
×

How To Make APIs That Don't Suck

22,030 views

Published on

At some point you’re going to have to deal with making or using APIs, here are some lessons to code by.

Published in: Technology, Business
  • Be the first to comment

How To Make APIs That Don't Suck

  1. 1. How To Make APIsThat Don’t SuckMichele TitoloSr. Mobile Engineer, Prolific Interactive@micheletitolo
  2. 2. @micheletitolo
  3. 3. @micheletitolo
  4. 4. @micheletitolo
  5. 5. An “API” for the sake of this presentationwill refer to any way your software cancommunicate with another piece of software.@micheletitolo
  6. 6. @micheletitolo
  7. 7. Lesson 3:Follow Conventions@micheletitolo
  8. 8. @micheletitolo
  9. 9. Lesson 3 Summary• Conventions save time• Conventions save money• Conventions make developers happy@micheletitolo
  10. 10. @micheletitolo
  11. 11. Lesson 2:Don’t be clever@micheletitolo
  12. 12. @micheletitolo
  13. 13. • Be smart• Be concise• Don’t be cleverLesson 2 Summary@micheletitolo
  14. 14. @micheletitolo
  15. 15. Lesson 1:Document, Document,Document@micheletitolo
  16. 16. @micheletitolo
  17. 17. Lesson 1 Summary• Document• Document• Document@micheletitolo
  18. 18. @micheletitolo
  19. 19. Lesson 0:Expect the Unexpected@micheletitolo
  20. 20. @micheletitolo
  21. 21. Lesson 0 Summary• Follow conventions• Don’t be clever• Document, document, document@micheletitolo
  22. 22. Resources• Matt Gemmell - API Design• Google Tech Talk - How To Design A GoodAPI• Stackoverflow - What Do You ConsiderGood Documentation• RESTful Web Services by LeonardRichardson@micheletitolo
  23. 23. Thank You!Michele Titolo@micheletitolo

×