423 - Web Push API
Basic Information
| Attribute | Details |
|---|---|
| Product Name | Web Push API |
| Standards Organization | W3C / IETF |
| Specification Document | https://developer.mozilla.org/en-US/docs/Web/API/Push_API |
| Product Type | Browser Push Notification Standard API |
| Core Technologies | Service Worker, VAPID Keys |
| Latest Changes | January 2026 Chrome Introduces Push Frequency Limits |
Product Description
The Web Push API is a W3C-standardized browser API that enables web applications to receive push messages from a server, even when the application is not in the foreground or not loaded. Based on Service Worker and VAPID (Voluntary Application Server Identification) key technologies, Web Push delivers cross-platform push notifications for both desktop and mobile browsers with a one-time user authorization. In 2026, Chrome introduced engagement-based push frequency limits, driving the industry towards more precise push strategies.
Core Features/Characteristics
- Background Push: Receive messages even when the app is not in the foreground or not open
- Service Worker Driven: Intercept and handle push events via Service Worker
- VAPID Authentication: Application server authentication based on public-private key pairs
- One-Time Authorization: Users only need to authorize once to continue receiving pushes
- Cross-Platform Support: Supported on both desktop and mobile browsers
- Apple Safari Support: Apple has added Web Push support in Safari (macOS and iOS)
- Rich Notifications: Supports rich media notifications with icons, images, action buttons, etc.
- Silent Push: Silent push for background data synchronization
- Chrome Frequency Limits (2026): Intelligent frequency control based on user engagement
- Encrypted Transmission: End-to-end encryption of message content
2026 Chrome Frequency Limit Rules
- Push message volume is related to the time users spend on the site
- Permission prompt frequency is linked to user session duration
- Low-engagement sites are limited to no more than 1000 messages per minute
- Exceeding the threshold returns an HTTP 429 error
Business Model
- Open Standard: Web Push API is a free W3C standard
- Browser Vendor Support: Provided for free by Chrome, Firefox, Safari, Edge, etc.
- Third-Party Push Services: OneSignal, Pushwoosh, PushPushGo, etc., offer value-added services
- SaaS Push Platforms: Provide paid features like push management, analytics, A/B testing
- No Platform Tax: Reach users directly via the web without app stores
Target Users
- Web application and PWA developers
- News and media websites
- E-commerce and retail websites
- SaaS applications
- Content publishers
- Teams that cannot or do not want to develop native apps
Competitive Advantages
- No App Installation Required: Reach users directly through the browser
- Cross-Platform Uniformity: One API covers all major browsers
- Open Standard: No vendor lock-in
- Low Cost: Push notifications without developing native apps
- Apple Safari Support: Covers iOS/macOS Safari users
- PWA Integration: A core capability of Progressive Web Apps
Market Performance
- Supported by all major browsers (Chrome, Firefox, Safari, Edge)
- A key driver of the PWA ecosystem
- 2026 Chrome frequency limits drive the industry towards higher-quality pushes
- Continued growth in the third-party push service market
- Widely used in news, e-commerce, and other fields
Relationship with OpenClaw Ecosystem
Web Push API serves as browser push infrastructure for OpenClaw:
- Web App Push: OpenClaw web apps can push notifications to users via Web Push
- No Native App Required: Users can receive OpenClaw notifications without installing an app
- PWA Support: OpenClaw can provide a complete push experience as a PWA app
- Full Platform Coverage: Achieves mobile + web coverage alongside APNs (421) and FCM (422)
- Low-Cost Reach: Reach users without paying app store fees
- Engagement Optimization: 2026 Chrome rules require OpenClaw to optimize push strategies