The Interface manifesto
summary
Argues that APIs are turning organizations into deliberately complex adaptive systems and proposes an Interface manifesto to steer that change, starting with interviews from January and a public synthesis by next December. Cites concrete artifacts: research on developer portals, an API‑to‑docs community event, a Dev Portal Awards program, a mailing list and a podcast called API Resilience. Warns against industrializing docs into a Confluence‑like dead end and calls for design of humane affordances.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:35Welcome
- 1:20Introduction
- 2:50Interface manifesto
- 4:00How are APIs impacting individuals
- 4:47How APIs impact government and wider society
- 5:20Failure states
- 6:00Complexity perspective
- 6:35Adaptive systems
- 7:00Biological autonomy
- 7:53Nervous system evolution
- 9:12Navigating the landscape
- 9:59Local optimizations
- 10:38External vs internal
- 11:41Two worlds
- 14:05Postman
- 16:05An opportunity for change
- 16:25The Silo effect
- 17:37The opportunity
- 18:08Management hierarchies
- 18:31Living systems
- 18:46Complexity
- 19:33API Resilience Podcast
- 20:04New mailing list
- 20:50Complexity vs complexity
related talks
23mThe Interface economy
26mThe "I" is for Interaction! Applying a developer-centric approach to API design
27mUser focused API Design
14mDesigning APIs That Humans Love
16mWriting for what Matters
21mIntroducing The API Lifecycle
40mThe API mindset: tech, product, business and legal
28mAPIs should be products, devportals too - or shouldn't they?
