Web Apps can’t really do *that*, can they?
summary
Demos show concrete capabilities and limits: service worker fetch interception replaces PNGs, supports three offline strategies (hard pre-cache, network‑then‑cache fallback, network-with-200ms timeout plus background cache update) and handles background sync and push (Chrome/Firefox live, Edge behind flag, Safari unclear). WebAssembly demo compiles C via emscripten, exposes readable wasm text, and runs a DNAnywhere .NET runtime in the browser (combined payload ~326KB; non‑wasm polyfill adds ~100KB). Credential Management is live in Chrome only; Payment Request API works in Chrome and Edge (Firefox developing, Safari uncommitted).
AI-written summary · about
chapters (27)
- 0:00Start
- 1:40Chrome Status
- 1:56Microsoft Edge
- 3:41Service Workers
- 4:24The Idea of a Service Worker
- 7:11What Is in the Serviceworker Dot Js File
- 11:14Run Your Application Offline
- 11:24Offline Support
- 11:46Caches
- 14:50Offline Approach
- 15:52Slow Network Connection
- 19:12Browser Support
- 20:00Web Assembly
- 21:05Web Assembly Source Code
- 21:27Fibonacci Sequence
- 22:14Compile C to Web Assembly
- 35:09Implement a To-Do List
- 35:49Display the Number of Items in the List
- 42:17Do Browsers Support Web Assembly Yet
- 43:08Credential Management
- 44:26Ceo Portal
- 45:53Instantiate a New Password Credential
- 46:49Logged in View
- 48:39Browser Support in Firefox and Edge
- 49:57Taking Payments from Users
- 50:41The Payments Request Api
- 51:19Adding a Payment Feature
