PWA and Web Push API Blog Series
- Introduction (this post)
- Application Server (coming soon)
Progressive Web Apps and Web Push API
Progressive Web Apps (PWA) are a great way to create excellent experiences for users on the web and mobile. I’ve recently been experimenting in this space and have found it to be a lot of fun to create such apps. As part of my app, I wanted to be able to push notification messages to all clients whether they’re using the web or mobile instance of the PWA. I found that this can be done through the Web Push API.
In my experimentation, I created a PWA and quickly jumped into sending notifications to clients using the Web Push API. This involves three pieces communicating together: an Application Server, a Push Service and a Subscriber. The Push Summary details described by Mozilla were a huge help in getting a grasp on how all these components interface with each other. In my case the Application Server is a Node.js app and the Subscriber is my PWA. As for the Push Service, think of it as a third-party solution which the various browser vendors handle for now (I’ll dive deeper into this in a later post).
With these tools I was able to push notifications through a Node.js web server running on Azure. This was set up by leveraging the web-push module which helps in securely creating the correct message payloads to be received by the service worker running on the client. The result is a browser notification displayed on the user’s machine with the message:
Continue reading and learn about setting up a service worker in the next post: Progressive Web Apps and Web Push API - Service Worker
comments powered by Disqus