Providing a childcare service for your API
summary
Argues that success depends on design before code and recommends concrete rules: APIs must be extensible, loosely coupled, long‑living, verbose; split functionality (example: a product + variant APIs pair) so a product API returns default item and thumbnails while a variant API returns high‑res images and per‑variant prices, allowing independent evolution. Uses a four‑step loop listen learn build measure, advocates prototyping/mocks, release‑first, fail‑fast (aim under one month) and KPIs like +20% customer satisfaction in six months.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:17Brain
- 2:11Design Process
- 4:49Where to start
- 9:45Four stages
- 15:02Success early
- 15:44Customers
- 17:11API teams
- 19:31Listening
- 20:52Fail fast
- 22:02Alignment
related talks
01h 07mDesign and Build Great Web APIs
30mFrom futons to functions: the principles of good API design
11mLifecycle of an API design
36mEverything is an API
32mLet's put U in UX!
53mA Case For Outside-In Design
27mDesigning Even Larger (JavaScript) Applications
01h 10mTowards higher Reusability : Applying Clean Architecture to API Landscape.