The "I" is for Interaction! Applying a developer-centric approach to API design
summary
Argues that API design must treat interfaces as interaction design focused on developer experience, identifying two core surfaces: the human portal and the runtime app–API. Lists four failure modes: projecting internal models, stylistic biases, bad assumptions, and budget/time limits. Recommends concrete tactics: interview and survey target developers, observe public client code, prototype interfaces with simulated data, use historical usage to guide v2 decisions. Cites examples: a company removes a SOAP endpoint after usage analysis, teams colocate API and app devs; promotes API explorers, lazy registration, and OAuth2.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:50Interaction Design
- 3:00UserCentric Design
- 5:56Design Products
- 6:35frictionless integration
- 8:40Project your own perspective
- 9:40Biases
- 12:25What matters
- 13:05Bad assumptions
- 13:40Limitations
- 14:05Shortcuts
- 14:55Mental Models
- 15:35Ask Developers
- 16:50Listen
- 17:20Observe
- 18:40Historical Data
- 20:15All Aspects
- 21:15Immediate Feedback
- 21:55Interface Style
- 22:20Hypermedia
- 23:00Target Audience
- 23:40Developer vs API
related talks
27mUser focused API Design
28mDevelopers are People Too! Building a DX based API Strategy
29mThe Interface manifesto
01h 01mAPI Design – How to Do It Better (and How Not To)
23mThe Interface economy
26mAPIs are the new skin of your organisation
22mThe Art of Effective API Design
27mTrends & anti-patterns; navigating the digital landscape for future survival