APIs should be products, devportals too - or shouldn't they?
summary
Argues that APIs are utilities not products, showing why shared API standards (Kubernetes, PSD2, telecom APIs via the Linux Foundation) scale better than bespoke, differentiated APIs; demonstrates how developer portals and packaging turn those utilities into marketable offerings, citing Stripe’s embedded checkout and Twilio’s productized docs as examples; presents the interface-portfolio idea where APIs sit under embedded solutions and no-code products so smaller firms can adopt quickly and portals become the place that actually differentiates the offering.
AI-written summary · about
chapters (10)
- 0:00API products debate
- 2:35APIs as utilities?
- 7:16Three economies model
- 11:16APIs as collaboration tools
- 15:53Commoditization concerns
- 19:05Developer portals as products
- 20:53Embedded solutions beyond APIs
- 22:57Interface portfolio strategy
- 24:21Adapting interfaces for business
- 25:46Summary and next steps
related talks
15mAPI Portals Reimagined: Past, Present, and Future Trends
23mThe Interface economy
30mConsumer APIs Must be Product-Driven
26mAPIs are the new skin of your organisation
27mAPI Economy and Ecosystem
40mThe API mindset: tech, product, business and legal
25mUnlocking API Potential: The Power of Developer Portals
39mSorry Developer, Your API Just Became a Product