From Web APIs to Cross-Device Web Sites
summary
Built a Java REST framework in 2005 and now runs a browser-based PaaS called API Spark that creates, hosts, and manages web APIs without coding; argues REST fits human-driven websites but not machine-to-machine APIs and publishes a new architecture draft on GitHub draft with constrained principles (stateless, custom interface, offline support). Recommends one API per device/channel with versioning, cites Netflix’s device-specific APIs, and reports API Spark is live in limited public beta.
AI-written summary · about
chapters (12)
- 0:00Cross-device websites intro
- 1:54Classic sites to web APIs
- 3:41Unifying REST development
- 5:26Cloud impact on APIs
- 6:51Web API anatomy
- 8:15Composing APIs
- 10:22Open source to cloud shift
- 11:47REST limitations
- 13:54API style for machines
- 15:41Cross-device user experiences
- 17:47Defining cross-device sites
- 18:29Final thoughts
related talks
27mBuilding Great Web APIs
16mAPI Integration with JS: Scalable, and Future-Ready Systems
42mThe future of API (Platform) architecture
32mAPIs at the Crossroads From Integration Glue to Intelligence Infrastructure
28mRequiem for APIs - The Evolution of Web Development
50mMicroservices, APIs, and the Autonomous Web
22mState of APIs: Now and Next
28mThe App-Changing Magic (and Joy) of Web APIs
