The Phantom of the App: Background Services

on YouTube ↗30m

" summary

Survey of concrete service worker features and limits: covers background fetch with pause/resume and access to bytes, periodic background sync (min ~12 hours, requires install and permission, runs on same network), and notification triggers that fire offline but always show a notification. Shows debugging via DevTools Application panel, notes most features are Chromium-only (push is also in Firefox), and stresses that periodic sync runs invisibly while notification triggers are visible.

AI-written summary · about

" chapters (13)

1. 0:00Introduction to background services
2. 3:33What are background services
3. 7:10Service worker lifecycle and events
4. 11:47Debugging background services
5. 13:11Payment handler API
6. 14:54Background sync API
7. 15:16Background fetch API
8. 16:18Push messaging API
9. 17:23Notification triggers vs periodic sync
10. 22:59Periodic background sync in code
11. 26:11Notification triggers in code
12. 27:58Browser support and PWA focus
13. 28:42Trade-offs and user experience

" related talks

• 58mService workers - beyond the cachePhil Nash · NDC Sydney 2018
• 17mService Worker and the Appification of the WebNolan Lawson · DotJS 2016
• 25mOffline-enabled Web AppsMugdha Lakani · Shift Dev 2019
• 26mBrowsers behind your backPhil Nash · jsDay 2017
• 30mThe Beauty of Service WorkersTroy Taylor · ngAtlanta 2019
• 38mThe Mysterious Life of Web Apps in the BackgroundMax Firtman · CityJS Conference 2020
• 01h 00mService Worker: Bringing Native App Experience to Web AppsVyktor Zozuliak · OdessaJS 2015
• 36mPWA underhood: what makes it so progressiveSergiy Babich · FrontEnd Con 2018