Consumer APIs Must be Product-Driven
summary
Argument: APIs succeed when treated as products with clear business metrics, budgets and roadmaps. Recommends design-first with OpenAPI, product owners who own vision plus nonfunctional SLAs, and API management for rate limits, monetization and analytics. Cites practical outcomes: sportsradar sells data via API, Dropbox gains stickiness through integrations, adidas models a product API landscape. Warns against inside-out engineering and choosing REST or GraphQL for novelty rather than fit. Requires SDKs, interactive docs and support to prove value and scale.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:47API Product Ownership
- 4:11Adidas API
- 5:22API Product
- 8:00Landscape
- 9:03Consistency
- 9:57Lifecycle
- 12:35Product Owner
- 16:04Product Owner Responsibility
- 25:21Questions
related talks
25mAPIs are not a technical challenge
27mAPI Economy and Ecosystem
40mThe API mindset: tech, product, business and legal
39mSorry Developer, Your API Just Became a Product
28mAPIs should be products, devportals too - or shouldn't they?
21mScaling API Design
26mUsing APIs for Better Business Partnerships
16mMaster API Product Design with APIOps Cycles Method