Developers are People Too! Building a DX based API Strategy
summary
Claim: treating APIs as products and measuring developer experience raises adoption and cuts integration cost. Presents concrete metrics like task invocation ratio and time to first call, shows common friction (slow registration, XML‑RPC vs REST, Fahrenheit units) with a weather API example, recommends personas (Josh, Tony, Brenda), and a methodology: set business goals, define users, prototype observe iterate before build. Suggests prototyping tools Apiary and SoapUI and warns that DX is a discipline, not a sticker.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:38Presentation Analysis
- 6:00Designing an API
- 9:00SOA vs API
- 12:00Developer Experience
- 14:52Personas
- 16:26HumanComputer Interaction
- 18:31API Usability Theory
- 19:46Cognitive Dimensions
- 21:46Methodology
- 23:12Prototype
- 25:01Questions
related talks
26mIs DX the new CX?
44mExceptional Handling: DX as a Priority for API Products
26mThe "I" is for Interaction! Applying a developer-centric approach to API design
26mArchitecting A Great Developer Experience
25mWhat Developers Want
28mWho is your API for? Applying user personas to build better dev platforms
31mGetting developers hooked on your API
26mAsk your Developer: the rise of the API company