https:\/\/support.google.com\/partners\/answer\/7336533<\/span><\/a><\/p>\n <\/p>\n
If you ask a room of developers what mobile device features are missing from the web, push notifications are always high on the list.<\/p>\n
Web push notifications allow users to opt-in to timely updates from sites they love and allow you to effectively re-engage them with customized, relevant content.<\/p>\n
The Push API and Notification API open a whole new set of possibilities for you to re-engage with your users.<\/p>\n
Two technologies<\/h3>\n
Push and notification use different, but complementary,\u00a0APIs: push is invoked when a server supplies information to a service worker; a\u00a0notification\u00a0is the action of a service worker or web page script showing information to a user.<\/p>\n
Are service workers involved?<\/h3>\n
Yes. Push is based on service workers because service workers operate in the background. This means the only time code is run for a push notification (in other words, the only time the battery is used) is when the user interacts with a notification by clicking it or closing it.<\/p>\n
If you’re not familiar with service workers, read\u00a0the\u00a0service worker introduction. We will use service worker code in later sections when we show you how to implement pushes and notifications.<\/p>\n
<\/p>\n