APIs are not a technical challenge
summary
Main claim: building an API is rarely a technical problem but four business problems — identity vs product (Netflix removes APIs because the user experience is the product), internal culture and buy-in across sales/marketing/support, trust requires long-term stability (uptime, clear pricing/licensing, responsive support), and adoption through packaging and marketing. Concrete prescriptions: decide whether data or app is being sold, involve the whole company, run and consume the API internally, publish docs/SDKs and GitHub samples, create a developer portal, and don’t use raw developer count as the success metric.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:15APIs are not technical challenges
- 3:45Our app is our product
- 4:53Our data is our product
- 6:05Identity is important
- 7:13Cultural challenge
- 8:22Reality check
- 12:23Customer service
- 14:18Building successful API
- 14:55Trust challenge
- 15:52What to trust
- 17:12Pricing
- 18:22Trust
- 19:02Adoption
- 19:52Release
- 20:38Marketing
related talks
30mConsumer APIs Must be Product-Driven
27mAPI Economy and Ecosystem
26mAPIs are the new skin of your organisation
40mThe API mindset: tech, product, business and legal
26mAsk your Developer: the rise of the API company
33mDriving business growth and brand strategy in API-powered “Age of Assistance”
28mAPIs should be products, devportals too - or shouldn't they?
21mAPI Evolution: Master the Future of Business Integration