How To Make Your Website A Progressive Web App (And Why You Might Want To)
summary
A progressive web app turns a plain HTML/CSS/JS site into an installable, offline-capable app by adding HTTPS, manifest.json, and a service worker that manages caching and updates; real examples include party.party which caches audio for offline use (author saw ~300,000 party events) and Damn Dog packaged into the Microsoft Store with push notifications implemented via Firebase. Notes include: browsers require many PNG icons (no SVGs), test and fix with Lighthouse, and push can use Firebase, OneSignal or Twilio.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 7:02The role of a developer
- 10:51Websites versus apps
- 12:29Client app requests
- 14:13Native app limitations
- 17:52A true story of rejection
- 22:00The open web
- 23:11Introducing PWAs
- 28:23Technical PWA requirements
- 33:37Real-world PWA examples
- 44:06PWA games and stores
- 48:20Push notifications
- 50:48Resources for PWA devs
- 53:23Conclusion
related talks
58mHow To Make Your Website A Progressive Web App And Why You Might Want To
36mHow To Make Your Website A Progressive Web App (And Why You Might Want To)
38mProgressive Web Applications: The What, the Why and the How
37mIntro to Progressive Web Apps
47mProgressive Web Apps
10mAny Site can be a Progressive Web App
43mProgressive Web Apps - the Return of the Web?
50mThe (Awesome) Future of Web Apps