Progressive Web Applications: when “progressive” sounds ironic
summary
Talk covers building a Progressive Web App that replaces native apps across platforms (iOS, Huawei, etc.), describing unexpected cross-platform limitations and hacks used to keep the service stable. It explains why the team dropped Firebase and how they implemented their own notification and data-exchange infrastructure to cope with platform restrictions and unpredictable mobile OS behavior.
AI-written summary · about
chapters (11)
- 0:00PWA introduction
- 1:01What are PWAs
- 2:27Service Worker updates
- 8:06Service Worker lifespan iOS/Android
- 11:17Service Worker limits
- 14:50Push notifications Firebase issues
- 19:07Dropping Firebase Messaging
- 24:09Push click issues
- 27:19Lost push clicks
- 29:28Platform issues summary
- 36:06Q&A
related talks
38mProgressive Web Applications: The What, the Why and the How
26mProgressive Web Apps Are Easy Now - Or Are They
41mProgressive Web Apps
11mWhat's inside the term 'progressive web apps'
02mProgressive Web Apps and What's Next for Mobile
48mProgressive Web Apps from A to Z
36mProgressive Web Apps — Trick or Real Magic
39mDesigning great progressive web apps
