Building Delight into API interactions

What are key moments for creating developer delight in interacting with your API? Some thoughts on good and great practices I've seen across the web and dev tools

Transcript

1. Building ✨Delight ✨ into API Interactions Bear Douglas @beardigsit DevRel Lead @SlackHQ
2. Hi, I’m Bear!
3. Do you remember your first Heroku deploy?
4. From web.archive.org, Mar 30, 2010
5. What does “delight” get you?
6. 1. Adoption 2. Success rate of integration 3. Customer Satisfaction (CSAT) 4. Willingness to promote (NPS) 5. Retention over time Quality Affects
7. Think about the user journey
8. 1. Onboarding and setup 2. Daily use 3. When something goes wrong Key Moments For Delight
9. Let’s start with daily use
10. Consistency
11. OpenAPI Magic
12. 41 68 8:48 PM – 15 Jul 2014 Ease and speed of use
13. Now, let’s talk onboarding
14. Controversy - the Fabric installer
15. Can you make it one step easier?
16. Can you reduce context switching?
17. Delight in failure - really.
18. Grace in failure
19. The power of suggestion
20. Support as DevX
21. Love coffee? Visit our site to see the full Barista Bar menu and specials! #LoveCoffee 41 68 8:48 PM – 15 Jul 2014 The Barista Bar @baristabar Voice & tone
22. Engage in real dialogue
23. Surprise and delight
24. Follow up & follow through
25. Your team feels delight dividends
26. 1. Adoption 2. Success rate of integration 3. Customer Satisfaction (CSAT) 4. Willingness to promote (NPS) 5. Retention over time Quality Affects
27. Thanks!