Views: 11
Summary – Push notification reliability, which drives engagement, retention, and conversion, is often perceived as lower on PWAs, especially on iOS. However, Android natively supports the Push API via Service Workers, and iOS 16.4+ now offers Web Push—provided the app is installed from Safari, the permission flow is optimized, and VAPID keys and tokens are managed properly. Result: near-native performance, TTM and costs halved.
Solution: deploy your PWA with a cloud push service, follow best practices, and rely on an expert to achieve a channel equivalent to a native app.
Push notifications have become an essential lever for maintaining connections with users, driving engagement, and optimizing conversion in modern applications. Whether it’s a web app, a PWA, or a native application, the ability to deliver a contextual message at the right moment can transform the user experience.
However, the perception persists that PWAs struggle to offer reliability on par with native apps, particularly on iOS. In this article, we separate fact from fiction and examine the technical and business challenges of push notifications on PWAs to inform decision-makers in their architectural choices.
Push Notifications: A Critical Stake for Applications
Push notifications shape engagement and retention. They can turn a fleeting interaction into a loyalty cycle.
Push notifications represent a direct channel to the user, enabling real-time reminders, offers, or alerts. In a saturated market, the ability to appear on the lock screen is the difference between a forgotten app and one adopted for the long term.
Beyond engagement, they contribute to retention by regularly reminding users of added value. A well-targeted notification reinforces the sense of usefulness and reduces churn, fostering organic growth through digital word-of-mouth.
Finally, push notifications serve conversion by prompting action: time-limited promotions, delivery status updates, or the launch of a new feature. This channel suits both transactional communications and marketing campaigns.
User Engagement
Push notifications allow contextual messaging without forcing the user to reopen the app. They can remind users of an abandoned cart, signal a critical update, or offer personalized content. When segmented by profile or behavior, they create a tailor-made experience.
In a recent case, a Swiss education company used push reminders to invite its customers to participate in pedagogical surveys. The responsiveness improvement was clear: the open rate rose by 18%, demonstrating the effectiveness of time-aligned targeting with user habits.
This example highlights that a well-thought-out notification strategy strengthens app adoption and generates continuous interaction with the user base, a key factor for medium-term growth.
Retention
User retention is a major challenge for any mobile or web application. Push notifications help bring back active users by offering relevant content—breaking news, file updates, or order tracking.
For example, a Swiss SME specializing in logistics implemented delivery progress alerts via a PWA. Result: the monthly re-engagement rate doubled, proving that even enterprise applications can benefit from automated reminders.
Such a scenario demonstrates that push notifications are not reserved for B2C services: in the B2B realm, they enhance satisfaction and trust by providing transparent process tracking.
Conversion
During the conversion phase, a push notification can act as a final nudge to complete a purchase or download a resource. The urgency of a limited-time promotion or the announcement of low stock creates a sense of scarcity.
A Swiss cultural organization tested special-offer push notifications to boost ticket sales. Simply sending a notification announcing a “1-hour flash discount” generated a 22% increase in online transactions.
This feedback underscores the power of push to turn latent interest into immediate action while optimizing marketing campaign ROI.
PWA vs. Native Applications: The Debate
Native applications offer full access to system APIs but require separate development efforts and higher costs. PWAs, on the other hand, accelerate time to market and ensure unified maintenance.
Native applications benefit from full control over hardware and deliver an optimal user experience. They can leverage advanced features such as background geo-tracking, augmented reality, or continuous scheduled tasks.
PWAs, built on standard web technologies, deploy via URL and install directly from the browser. The same codebase serves Android, iOS, and desktop, drastically reducing development and maintenance costs.
Historically, PWAs suffered from limited OS feature access, particularly for push notifications on iOS. However, this gap is narrowing, provided the technical specificities and platform constraints are well understood.
Performance and APIs
Native apps rely on dedicated SDKs to maximize performance and exploit system APIs (accelerometer, Bluetooth, biometric sensors). They compile for the target platform and benefit from runtime optimizations.
PWAs run on the browser’s JavaScript engines and use Service Workers to handle caching, offline mode, and notifications. Advances in JavaScript engines and WebAssembly significantly narrow the performance gap, especially for graphical rendering and intensive computations.
A predictive maintenance project by a Swiss facility management institution compared both approaches. The PWA achieved 95% of native app performance on Android while offering twice the speed to production.
Cost and Maintenance
Maintaining two native codebases (iOS and Android) requires dedicated resources, separate testing, and continuous feature synchronization. Costs skyrocket, especially amid frequent updates and long-term maintenance.
PWAs, by contrast, rely on a single repository. Updates are pushed server-side without needing store publication, reducing operational costs.
Time to Market
Building a native app requires setting up two environments (Xcode for iOS, Android Studio for Android) and obtaining certifications on each store. Apple and Google approval timelines extend delivery cycles.
PWAs are instantly accessible via a URL and require no validation process. Fixes and new features are deployed immediately. The time to market is therefore significantly reduced, a crucial advantage for MVPs or time-sensitive projects.
A Swiss agri-food startup launched its online ordering platform prototype in under four weeks thanks to a PWA. User feedback allowed quick UX adjustments before considering a native wrapper for the most critical features.
Edana: strategic digital partner in Switzerland
We support companies and organizations in their digital transformation
Do PWAs Support Push Notifications Today?
On Android, PWA push support is complete and comparable to native. On iOS, since version 16.4+, web notifications are officially supported but under strict conditions.
For several years, Android has natively integrated the Push API and Service Workers. PWAs can receive push messages even outside the browser context and display notifications similar to native apps.
With iOS 16.4 and later, Apple introduced Web Push support in WebKit. PWAs installed on the home screen can now subscribe to push, but the experience remains dependent on Safari and specific system permissions.
To ensure reliability, it’s essential to properly handle permission flows, implement a relay service to work around WebKit provider limitations, and test across different iOS versions.
Android
Android has offered mature PWA push support for several years. Service Workers enable receiving and displaying notifications, adding interactive actions, and defining notification channels.
The behavior is often nearly identical to a native app: custom icon, message grouping, interactions, and deep links to a specific page within the application. Developers have APIs to manage notification priority and lifespan.
A Swiss e-commerce company adopted a PWA for its mobile site. Abandoned cart reminder notifications achieved a delivery rate of 98% on Android, with an average cart recovery rate of 14%.
iOS
On iOS, official PWA push support arrived only with iOS 16.4. Before then, it was impossible to send push notifications via a service worker in Safari, severely limiting PWA effectiveness for Apple users.
Today, Safari-installed PWAs can receive push once the user grants explicit permission. Notifications follow the same format as native apps, but their display depends on WebKit and Apple’s policies.
A Swiss healthcare provider entrusted our team with managing iOS notifications: by replicating native workflows in Safari, we achieved a 72% permission rate, demonstrating the channel’s viability.
Conditions and Permissions
To receive push on iOS, the PWA must be installed from Safari to the home screen. Notification permissions are handled by the browser, not by a dedicated system dialog.
It’s crucial to guide users through the installation flow, explain the added value of push, and provide follow-ups in case of initial refusals. Without this, permission rates plummet.
Managing subscription tokens and their automatic renewal requires a dedicated server infrastructure capable of communicating with Apple’s Web Push endpoints and handling key rotation.
How Push Works on a PWA (Simplified)
Service Workers act as the intermediary between the browser and the notification server. They receive push messages and trigger notifications even when the PWA is not active.
The Service Worker runs in the background and registers via the PWA’s JavaScript code. It intercepts push events, processes the payload, and displays the notification using the Notifications API.
The flow is as follows: the backend sends a message to the Push Service (Firebase Cloud Messaging for Android, Apple Push Notification Service for iOS PWAs), which relays the notification to the browser. The Service Worker then handles the event.
This architecture decouples the PWA from the main application server, ensuring that notifications can be received even when the interface is not loaded.
Service Worker and the Push API
The Service Worker registers on the first visit and remains active in the background. It listens for the “push” event and triggers a callback function to display the notification.
The Push API provides methods to subscribe to the service, handle encryption keys (VAPID), and retrieve the subscription token. This token is essential for the server to target the specific device.
A Swiss university used a misconfigured Service Worker: VAPID keys were not correctly specified and notifications were not encrypted. After correction, the delivery rate jumped from 60% to 97% on both Android and iOS.
Backend Notification Flow
The backend must implement a module to manage user subscriptions, store tokens, and send push messages via the dedicated services. This can be a serverless function or a microservice.
Each notification is encrypted with the VAPID keys sent to the push service. The payload can include a title, body text, icon, redirect URL, and interactive actions.
The backend should also handle errors: expired tokens, unavailable devices, or invalid subscriptions. A routine to clean up obsolete tokens keeps the database clean and delivery efficient.
Comparison with Native
In a native app, only the internal SDK manages tokens and sends messages without involving a browser. Notifications are handled via Firebase or APNS with system dialogs for permissions.
The main difference with PWAs is the need for a Service Worker and browser context. This technical overhead remains marginal if the server and JavaScript code are well architected.
A Swiss provider hesitated between a PWA and native. After analyzing the workload, we showed that a well-architected PWA coupled with a cloud push service delivered an equivalent experience at 40% less budget.
Master PWA Push to Maximize Engagement
Push notifications on PWAs are now reliable on Android and functional on iOS since version 16.4+, provided best implementation practices are followed and users are guided through installation and permission granting. Using a wrapper or a cloud push service can simplify management and bring the experience closer to that of a native app.
Whether your project requires a rapid MVP, a multi-platform enterprise app, or a cost-effective concept test, PWAs offer a sweet spot balancing performance, controlled costs, and time to market. Our experts can help you design a robust, scalable push solution aligned with your business strategy.
