Going Web Native
summary
Argues the web now matches many native app affordances by showing concrete pieces: service worker as installer that enables offline caching, push, background sync and causes browsers to show an Add to Home Screen prompt; a manifest that produces standalone apps with no address bar; Web Components that run across Angular React etc; WebAssembly for heavy work like CAD and games; Workbox, Polymer/Stencil as starters; examples include Twitter switching to PWA and YouTube using Web Components and Safari auto-removing unused service workers after two weeks.
AI-written summary · about
chapters (28)
- 0:00Intro
- 2:04The web is dead
- 5:02Story time
- 6:15Getting started
- 8:07The wrong audience
- 10:35How many applications have you installed
- 11:40Native applications are disappearing
- 12:42The web is not dead
- 15:32The main issues
- 22:03Missing application model
- 23:53Progressive Web Apps
- 25:00App Manifest
- 25:43Service Worker
- 27:18How it works
- 29:25Push
- 33:40Performance
- 34:42WebAssembly
- 36:17Other APIs
- 39:43Summary
- 40:23Study
- 41:33Tools
- 42:02Frameworks
- 43:44Web Assembly
- 44:53Browser Compatibility
- 45:09YouTube Twitter
- 45:39Browser is becoming your new operating system
- 46:38About Violent
- 47:49Notifications
