HTTP API Design: UX for the Nitpickeriest

Stripe, Heroku, Slack, all made their APIs so fun to use that developers started using them when they had a few minutes to tinker, no sprint allocation needed. We’ll go over the most important pitfalls and Developer Experience rules to make developers love working with your APIs.
Most developers are very opinionated, and can tell at great length just why a certain tool or API are wrong. Yet, when designing our own APIs we usually don’t have a lot of experience of being on the other side of the equation, or the time to get experienced. In this session you’ll get a cheat sheet of the important aspects to consider in your HTTP APIs as well as lessons (good and bad) from companies such as Stripe, Slack and Heroku.

Transcript

1. HTTP API DESIGN: UX FOR THE NITPICKERIEST
2. YOU’RE IN THE ARMY NOW
4. BETTER DX == BETTER BUSINESS
5. GOOD DX TEST
6. #1 TIME TO WIN
8. SET A GOAL
10. #2 API AS FIRST-CLASS PRODUCT
11. #3 EMBRACE EDGE CASES
12. #4 BE BORING
13. TREAT DX PROFESSIONALLY
14. bit.ly/nordic-dx Aviv Ben-Yosef B2B SaaS Consultant @avivby