How APIs Change Software Development
summary
APIs shift software from standalone products to reusable platform building blocks, claiming business value not just technical glue. Amazon’s Bezos 2002 API mandate enforces “everything has an API” and creates a network effect; organizations need a registry and discovery to realize that value. Practical advice: plan for extension, plan for augmentation, and make everything automatable via APIs. For composability prefer linkable hypermedia patterns (simple JSON links) and treat API design as product design with ongoing maintenance.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:37About me
- 2:15About XWay
- 3:09Software development has changed
- 4:18What is an API
- 6:35Platforms
- 7:58The Network Effect
- 9:12Jeff Bezos API Mandate
- 11:42Building on top of what others build
- 15:15Car analogy
- 16:22How can we become better
- 16:35Importance of APIs
- 17:27API Product
- 18:27How to Build a Better Product
- 20:29API Design litmus test
- 21:50How to evolve APIs
- 24:53Wrap up
- 25:17QA
- 26:40Mobile Apps
- 28:35API Styles
- 30:21HyperMedia APIs
- 31:50API vs UI
- 32:45Documentation
- 35:23Conclusion
related talks
28mThe New API Stack
40mThe API mindset: tech, product, business and legal
26mAPIs are the new skin of your organisation
32mAPIs are Arrangements of Power. Now what?
27mThe Disruptive Impact of APIs: How APIs are shifting business
41mThe platform revolution: How APIs transform industry structures
26mMastering API Strategies for Digital Transformation
23mContinuous API Product Management