Web push can alert a person after the page closes, but it is a separate delivery channel with browser permission, a service worker, a subscription endpoint, a push service, and server-side policy. None of those layers guarantees that the person read an alert. This track follows urgent case assignments for field reviewers. It covers when to ask, how to bind subscriptions to accounts, what may appear on a lock screen, and how to recover when a device or push service does not deliver.
Topics in this track
- Notification Opt-In and Channel Preference — Ask for alert permission only after a relevant action and keep a usable in-app path after denial.
- Push Subscription Account Binding and Rotation — Bind each endpoint to a verified account and device lifecycle without exposing it as a public identifier.
- Private Notification Payload and Click Routing — Keep lock-screen text minimal and reauthorize the destination when a notification is opened.
- Push Delivery Retries, Expiry, and Inbox Fallback — Model accepted sends separately from device display and keep an authorized durable inbox.
Prerequisite paths
Browser Capabilities and Permission Lifecycle; Media and Live Updates; Privacy-Aware External Integrations.
Practice path
Build Project: private urgent assignment alerts and check decisions in Web Development: push notification decisions quiz.