Basic FAQsLast Updated: December 03, 2018
Q 1: How are web push notifications different from app push notifications?
Native app notifications can take full advantage of the device features - the camera, GPS, accelerometer, compass, contact list and so on. Whereas web app notifications still can’t utilize any hardware on the device.
Native app notifications are limited to mobile phones and tablets. Web push notification's reach extends to mobile phones and tablets along with desktop as well.
Native app notifications support rich media - images, videos, gifs, audio, and other interactive elements. Web push notifications only support large images (only on Chrome 56 and above).
Q: How do web push notifications work?
There are three actors involved with delivering a push notification, along with a fourth, optional, component for advanced functionality.
Push Notification Service: Each browser, including Chrome, Safari and Firefox have their own notification delivery service. Chrome uses Google Cloud Messaging ( and now Firebase Cloud Messaging ) and Safari uses Apple Push Notification Service ( APNS ).
Service Worker Registration: Developer must register the service worker on the browser. This is only for Chrome and Firefox. Safari does not support service workers.
User’s Subscription ID: Subscriber ID is generated when a user opts in to receive notifications from a specific website.
Q: Should I Build My Own Web Push Solution Or Use A 3rd Party Service Provider?
There are a couple of points to keep in mind before taking that “Make or Buy” decision. Building a web push notification platform will, in fact, make it a second product altogether within your core business - a product that demands continuous resources to -
- Develop the solution
- Test and release the product
- Fix the bugs
- Ensure security
- Provide ongoing support and maintenance
- Keep in sync with the technology updates
When making that rather important “Make or Buy” decision, ask yourself - are you ready to put in that amount of resource, time and money?