PWA Installation Is a Conversion Event. Treat It Like One.
Getting users to install your Progressive Web App is critical for engagement. According to Google, installed PWAs generate 4x more page views, 80% longer session duration, and 3x higher conversion rates compared to browser-based usage. Yet PWA installation rates average only 3-5% without optimization. Optimized installation flows can increase installation rates to 15-20% or higher. The key is understanding when and how to prompt users for installation based on their behavior and engagement signals.
At x13apps, we optimize PWA installation and engagement for maximum user adoption. Here is our strategy.
The Web App Manifest
The web app manifest (manifest.json) controls how your PWA appears when installed. Essential manifest properties: name (full app name for splash screen), short_name (12 characters for homescreen label), icons (192x192 and 512x512 PNG), start_url (the page that opens when the app is launched), display (standalone for app-like experience without browser chrome), theme_color (toolbar color), background_color (splash screen background), and orientation (preferred screen orientation). Each property affects whether browsers offer installation and how the app appears after installation.
Manifest optimization tips: provide at least 2 icon sizes (192px and 512px), use PNG with transparent background for icons, set display to standalone (not browser), use a distinct background color that matches your brand, and ensure start_url is the same origin as your app. Invalid manifest properties prevent installation entirely. Use Lighthouse PWA audit to identify manifest issues before launch. Test installation on actual devices: what works in Chrome DevTools may behave differently on a real device.
Intelligent Installation Prompts
Never trigger the install prompt immediately when users arrive. They do not know your app yet. Instead, use the BeforeInstallPromptEvent to control when to show the installation prompt. Track user engagement signals that indicate installation readiness: time on site (2+ minutes), pages visited (3+ distinct pages), returning visits (2+ sessions), and key conversion actions (completed purchase, created account). Users who meet 2+ of these criteria are 3x more likely to install than users prompted immediately.
Create a custom install UI rather than relying on the default browser prompt. Design an in-app installation banner that: explains the benefit (save for offline use, faster access), appears at a natural break point (after completing an action, not during onboarding), provides a clear call to action with a button, and can be dismissed without permanently hiding (allow re-prompting after subsequent visits). Custom install UIs convert at 2-3x the rate of browser default prompts according to Google case studies.
Post-Install Engagement
Installation is the beginning, not the end. Installed PWAs must deliver ongoing value to prevent uninstallation. Implement features that leverage PWA capabilities: push notifications (re-engage users with relevant updates), background sync (complete user actions even after they leave), and offline access (enable usage during connectivity gaps). Push notifications from PWAs achieve 30-40% click-through rates compared to 1-3% for email. But overuse drives uninstalls. Limit to 2-3 notifications per week unless providing time-sensitive value like order updates or appointment reminders.
Track post-install engagement metrics: daily active users, session frequency, retention rates (day 1, day 7, day 30), and uninstall rate. If uninstall rates exceed 10% within 30 days, assess whether your app provides sufficient ongoing value. Survey uninstalled users when possible to understand why they left. Implement web app banner detection to offer re-engagement when users return to your site after uninstalling. At x13apps, we build PWAs that users choose to install and keep. For more, read our PWA offline-first strategies guide.