Ask your Developer: the rise of the API company
summary
Distills three public-API types — product supporting, developer product, and developer enabled — and argues most firms are not true dev products; examples include Twilio, Stripe, Plaid, Google Maps, SendGrid and Zapier’s ~2,000 apps. Emphasizes the metric of initial momentum: the first hundred API calls or time to “hello world,” shipping quick wins via sample apps, use-case guides and a CLI (Zapier example). Recommends the “code on the homepage” test and deep, published knowledge (Gremlin’s ~20,000-word guide) as practical signals.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:05What defines an API company
- 3:36Secrets of great API companies
- 6:47Developer problem
- 9:39Knowledge sharing beyond service
- 11:21Public APIs explained
- 13:49Developer audience
- 16:22Developer product vs enabled
- 17:24First API success tactics
- 21:15Q&A
related talks
26mBuilding successful API developer programs
23mContinuous API Product Management
24mHow to make your API Platform easy for Developers to Adopt
39mSorry Developer, Your API Just Became a Product
12mAPI Economy and Crucial APIs to Know About
28mDevelopers are People Too! Building a DX based API Strategy
30mConsumer APIs Must be Product-Driven
40mThe API mindset: tech, product, business and legal