What Developers Want
summary
Developers ask for everything immediately so prioritize around business outcomes: measure API coverage (how much product is callable and documented with OpenAPI specs, snippets and sample apps), prefer tracking SDK installs vs API calls (installs can be CI noise; API calls correlate to revenue), use models like ARP and Orbit models to map funnel vs connection, treat vanity wins (10,000 t-shirts) as trend signals, and respond selectively — example: a PHP 8.1 SDK request arrived two weeks after release, forcing a business-prioritized choice.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:20Welcome
- 2:28What do developers want
- 4:12What do businesses want
- 5:49Maslows Hierarchy
- 6:45ARP
- 7:26Orbit
- 8:20Metrics
- 9:05Business Metrics
- 11:04Crazy Idea
- 11:24Developer Initiatives
- 13:30Key Points
- 17:30Thank You
related talks
28mDevelopers are People Too! Building a DX based API Strategy
26mBuilding successful API developer programs
26mAsk your Developer: the rise of the API company
24mHow to make your API Platform easy for Developers to Adopt
30mConsumer APIs Must be Product-Driven
29mBuilding What Developers Actually Want: Lessons Learned
54mAPI's a drivers for innovative business models
40mHow to market to developers during a recession