How to test PWA installation on Android and iPhone

Android: test the available browser flow

Open the intended HTTPS address in a supported browser such as Chrome. Use the browser’s installation option or the site’s install control when it is available. The exact label and behavior can vary with browser version and app configuration.

Confirm installation, then launch the app from its icon. Check the app name, icon, starting page and route to the offer. Also test a first visit and a return visit rather than assuming they behave identically.

iPhone: verify the home-screen path

Open the website in Safari. Use the Share menu and the option to add the site to the Home Screen; where an “Open as Web App” option is shown, enable it for the web-app experience. Confirm the name and add it, then open the new icon. Labels may vary by language and iOS version.

Do not show an Android-only browser prompt as the sole iPhone instruction. Confirm the currently supported path on the specific iPhone and iOS version used in your test.

When an install control is missing

Check whether the site is already installed, the browser supports the intended flow, the deployment uses HTTPS and the manifest is correctly linked and accessible. Inspect the application in browser developer tools rather than assuming the problem is advertising traffic.

A custom browser installation event is not universal. A missing event does not justify recording a click as an installation. An in-app browser may need a clear instruction to continue in a supported external browser.

Notifications need a separate test

Installation and notification permission are separate. Only request notification access when it makes sense for the user and when the implementation supports it. On supported iOS versions, web push is available for home-screen web apps under the platform’s conditions.

Confirm permission granted, permission denied and no-support states. Do not promise push delivery or background behavior based only on the existence of an installed icon.

Record a small, reproducible device matrix

• Device, operating-system version and browser version.
• Source application and whether it opens an in-app browser.
• First visit, install path and first launch from the icon.
• Return visit, login/session behavior and the destination offer.
• Unsupported-installation, denied-notification and weak-network behavior.

Separate technical support from campaign results

The checklist establishes whether the experience works; it does not establish that the campaign is profitable. Keep it alongside the launch checklist and confirm what the service counts as an install on the pricing page.