Refresh London - Designing an API for developer happiness
•
0 likes•162 views
An overview of what we've tried an learned about developer happiness when developing Cronofy's API.
Recommended
More Related Content
Viewers also liked
Viewers also liked (12)
Similar to Refresh London - Designing an API for developer happiness
Similar to Refresh London - Designing an API for developer happiness (20)
Recently uploaded
Recently uploaded (20)
Refresh London - Designing an API for developer happiness
- 1. DESIGNING AN API FOR DEVELOPER HAPPINESS
- 3. WHY DOES THIS MATTER ONBOARDING IS VITAL
- 4. SHARING OUR EXPERIENCE THINGS THAT HAVE WORKED THINGS THAT HAVEN'T WHAT WE'RE DOING NEXT
- 5. GOOD DOCUMENTATION START LANGUAGE AGNOSTIC
- 6. HIERARCHY OF API HAPPINESS ENDPOINT EXAMPLE LIBRARY FOR ME SIMILAR LIBRARY DOCUMENTATION
- 8. REQUEST JOURNAL RECORD EVERY REQUEST
- 10. STANDARDS THE WORLD DOESN'T NEED MORE WHEELS
- 11. UNDERSTAND CONTEXT WHAT DO YOUR CLIENTS KNOW
- 12. NON-BREAKING CHANGES NEVER BREAK EXISTING CODE
- 13. PREFIXED IDS VISUALLY TELL WHAT AN ID IS FOR
- 16. CONFRONT UNHAPPY PATHS ENCOURAGE THEM TO BE HANDLED
- 17. RATE LIMITS HAVE THEM FROM DAY ONE
- 18. SMART PUSH NOTIFICATIONS DON'T TELL ME WHAT I KNOW
- 19. DOG FOODING USE YOUR OWN API
- 20. RECOGNISE PLACEHOLDERS GUIDE COPY AND PASTE
- 21. ALPHA CHANNEL RELEASE EARLY TO PEOPLE WHO ASK
- 22. STATUS PAGE TELL PEOPLE IT'S YOUR FAULT
- 23. AVOID CLEVER DEFAULTS PRINCIPLE OF LEAST SURPRISE
- 24. DELAYING LIBRARIES WRITING CODE IS FRICTION
- 25. BETTER ERRORS BE AS HELPFUL AS POSSIBLE
- 26. BETTER GUIDANCE HELP THEM BE AWESOME
- 27. MORE EXAMPLES COPY AND PASTE TO SUCCESS