Surviving the Zombie Apocalypse of Connected Devices
summary
Argues that using HTML hypermedia APIs (microformat-style HTML, forms for state changes, CSS3 selectors for parsing) plus adaptive web design (mobile‑first, progressive enhancement, responsive CSS, delayed AJAX) turns a fat‑client problem into a fat‑API solution: build a richer server that serves view+metadata, use native controls for primary flows and webviews for secondary ones. Cites a surprising 3112 device long tail where 40% of mobile traffic comes from three iOS types and 60% from 3,112 others. Claims higher API cost but far lower client duplication and easier scaling.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:10Platform fragmentation
- 8:12Skinny APIs not solution
- 10:17Hypermedia as app state
- 13:26Media type for APIs
- 17:16HTML as API media type
- 20:02Objections to HTML APIs
- 22:46Hybrid apps with hypermedia
- 27:24Capability fragmentation
- 33:49Future of fragmented devices
- 34:09Adaptive web design
- 37:05Mobile first strategy
- 41:25API and web same endpoint
- 45:39Hybrid architecture recap
- 47:23Future architecture needs
related talks
27mHTML Hypermedia APIs and Adaptive Web Design
45mMuddling Through the Mobile Web
30mThe internet of things challange:building APIs that last for decades
39mDoes The Browser Have A Future
44mDesigning Hypermedia APIs
56mClosing Panel: "HTML5 and Devices"
33mHypermedia – the solution for future web applications?
43mResponsive Design, Past, Present and Future