The App-Changing Magic (and Joy) of Web APIs
summary
Shows how specific browser APIs replace libraries: using MessageChannel and message ports to link web workers and iframes avoids double-post overhead and keeps heavy work off the main thread; a small library called sandybox runs user code in a sandboxed worker; service worker respondWith transforms fetched assets (demo runs TypeScript compilation in-browser and caches results); and AudioWorkletProcessor generates brown noise for DeepBreathing.app, with Safari compatibility requiring extra cross‑browser debugging.
AI-written summary · about
chapters (9)
- 0:00Introduction and interactivity
- 1:24Rediscovering web platform joy
- 4:14What is a web API?
- 8:28Message Channel API deep dive
- 10:15Transferable skills from APIs
- 13:00Service Worker respondWith method
- 17:14Audio Worklet processor explained
- 24:39Shifting web app architecture
- 26:05Closing thoughts and Q&A
related talks
01h 13mWeb: The good parts
22mPWA patterns for window and service worker communication
38mThe Mysterious Life of Web Apps in the Background
37mA Single Page Story
50mMost useful browser APIs
47mAdventures in Rendering Off the Main Thread
23mWarm-Up Talk: Browser APIs – the unknown Super Heroes
22mThe (Abundant) State of the Web