Push Notifications Overview and Use Cases
You'll learn what push notifications are on the web, how they work at a high level, and when they genuinely benefit your users.
What Are Web Push Notifications?
Push notifications are messages sent from a server to your user's device—even when your PWA or website isn't open. Unlike in-app notifications (which require the page to be loaded), push notifications appear at the operating system level, just like native app alerts.
Think of them like text messages for your web app: the message arrives whether the recipient is actively using your app or not. They're powered by Service Workers, which run in the background and can receive messages from your server via a push service (managed by the browser vendor).
How They Work (High-Level)
- User grants permission for notifications
- Browser subscribes to a push service (Google FCM, Mozilla, etc.)
- Your server sends a message to that push service
- The push service delivers it to the user's device
- The Service Worker receives the push event and displays the notification
The browser acts as an intermediary, so you don't need the user's personal contact info—just their subscription token.
When to Use Push Notifications Effectively
Good use cases:
- New messages in chat/social apps (timely, personal)
- Breaking news for media sites (urgent, relevant)
- Order status updates (transactional, expected)
- Calendar reminders (user-initiated)
Bad use cases:
- Generic marketing blasts (spam)
- Content that isn't time-sensitive
- Anything users didn't explicitly request
Notifications are powerful but easily misused. Use them sparingly and always respect the user's attention—one poorly-timed notification can cause someone to revoke permissions forever.
Key Takeaway: Push notifications let your web app reach users even when closed, but should only be used for timely, relevant, user-valued information to avoid becoming intrusive noise.