Home▸Articles▸Computer Science

Understanding PWA Installability Criteria

Progressive Web Apps require specific conditions to be met for users to install them on their devices.

mysimulator teamUpdated June 2026≈ 3 min read▶ Open the simulation

What PWA Installability Criteria Are

Progressive Web Apps (PWAs) are web applications that offer a native app-like experience. For PWAs to be installed on devices, certain criteria must be met. These include having an HTTPS connection for secure data transmission, a valid manifest file that defines the PWA's properties and icons, and a service worker that enables background synchronization and offline support.

The 'beforeinstallprompt' event is fired when a user navigates to a page with a PWA that meets these criteria. This allows the site to prompt the user to install the app.

Why These Criteria Matter

Ensuring an HTTPS connection protects users from data breaches and ensures secure communication between the client and server, which is crucial for PWAs that may handle sensitive information.

A manifest file provides metadata about the PWA, such as its name, icons, start URL, and background color. This helps in creating a consistent user experience across different devices and platforms.

live demo · related simulation● LIVE

Real-World Examples

For example, Google Maps uses PWAs to offer a seamless navigation experience. By meeting the installability criteria, users can save the app on their home screen for quick access.

Another example is Flipboard, which leverages PWAs to provide personalized news feeds. The ability to install these apps enhances user engagement and convenience.

Impact of Installation Funnel

The 'beforeinstallprompt' event triggers a series of actions that can be tracked through the live install funnel, which helps developers understand how many users see the prompt and ultimately decide to install the app.

By analyzing this data, developers can optimize their PWA for better user engagement and higher installation rates.

Frequently asked questions

What happens if a PWA doesn't meet all the installability criteria?

If a PWA does not meet all the installability criteria, users will not see the 'beforeinstallprompt' event and thus cannot install the app on their devices.

Can I test these criteria without deploying my PWA to HTTPS?

While you can test some aspects of your PWA's installability locally or using a non-HTTPS environment, it is crucial to deploy your PWA over HTTPS for real-world testing and actual installation.

How does the 'beforeinstallprompt' event work?

The 'beforeinstallprompt' event fires when a user navigates to a page with a PWA that meets the installability criteria. It allows the site to show a prompt on the device's home screen, asking users if they want to add the app to their homescreen.

What are some best practices for optimizing installation funnels?

Best practices include ensuring all necessary files (manifest, icons) are correctly configured and available, using service workers effectively, and providing a clear user experience that encourages installations.

Try it live

Everything above runs in your browser — open PWA Installability Criteria Simulator and change the parameters while it is running. Nothing is installed, nothing is uploaded, the whole model lives in one tab.

▶ Open PWA Installability Criteria Simulator simulation

What did you find?

Add reproduction steps (optional)