One major advantage of native platforms is the ease with which users can be re-engaged by updates and new content, even when they aren't looking at the app or using their devices. Modern web apps can now do this too, using new technologies such as the Web Push API.
Core guides
- Using service workers
- A simple guide for those new to the Service Worker API.
- Using the Push API
- Learn the essentials behind the Web Push API.
- Using the Notifications API
- Web notifications in a nutshell.
Technologies
| Technology | Description | Support summary | Latest spec |
|---|---|---|---|
| Service workers | JavaScript running in a special worker context that is run by the browser under certain circumstances such as fetch or push events. These allow the service worker to intercept responses and customise them in any way you want, for example caching assets for offline use before they are served. | Experimental: Chrome and Firefox (more detail) | Service Workers |
| Push API | When subscribed to, the push service provides an endpoint that can be used by a server to send a push message to a web app under the control of a particular service worker. | Experimental: chrome and Firefox (more detail) | Push API |
| Notifications API | Fires system notifications directly from web applications. | Widespreadin modern browsers (more detail) | Notifications API |
Tools
- ServiceWorkerWare
- An Express-like microframework for easy Service Worker development.
- oghliner
- Not only a template but a tool for deploying Offline Web Apps to GitHub Pages.
- sw-precache
- A node module to generate service worker code that will precache specific resources.
See also
- The service worker cookbook
- A series of excellent service worker recipes, showing how to implement an offline app, but also much more.
Document Tags and Contributors
Tags:
Contributors to this page:
chrisdavidmills,
bunnybooboo
Last updated by:
chrisdavidmills,