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

1. How To Make APIs
That Don’t Suck
Michele Titolo
Sr. Mobile Engineer, Prolific Interactive
@micheletitolo

2. @micheletitolo

3. @micheletitolo

4. @micheletitolo

5. An “API” for the sake of this presentation
will refer to any way your software can
communicate with another piece of software.
@micheletitolo

6. @micheletitolo

7. Lesson 3:
Follow Conventions
@micheletitolo

8. @micheletitolo

9. Lesson 3 Summary
• Conventions save time
• Conventions save money
• Conventions make developers happy
@micheletitolo

10. @micheletitolo

11. Lesson 2:
Don’t be clever
@micheletitolo

12. @micheletitolo

13. • Be smart
• Be concise
• Don’t be clever
Lesson 2 Summary
@micheletitolo

14. @micheletitolo

15. Lesson 1:
Document, Document,
Document
@micheletitolo

16. @micheletitolo

17. Lesson 1 Summary
• Document
• Document
• Document
@micheletitolo

18. @micheletitolo

19. Lesson 0:
Expect the Unexpected
@micheletitolo

20. @micheletitolo

21. Lesson 0 Summary
• Follow conventions
• Don’t be clever
• Document, document, document
@micheletitolo

22. Resources
• Matt Gemmell - API Design
• Google Tech Talk - How To Design A Good
API
• Stackoverflow - What Do You Consider
Good Documentation
• RESTful Web Services by Leonard
Richardson
@micheletitolo

23. Thank You!
Michele Titolo
@micheletitolo