Do I need Google Play to install a PWA on Android?

No — installation happens directly through Chrome, with no store listing or store review involved.

Why doesn't the install banner show for some users?

Usually low engagement on the page, a non-Chrome browser or in-app social webview, or a missing technical requirement like HTTPS, the manifest, or the service worker.

Can I trigger my own install button instead of waiting for the Chrome banner?

Yes — capturing the beforeinstallprompt event lets you show a custom Install button and fire the native dialog on click, giving you control over exactly when it appears.

Does a PWA work offline after installing on Android?

Basic navigation does if the service worker caches assets; offer screens that need live data (casino, betting) typically still fetch online, but the icon and app launch behave like a native app.

Does the install flow differ across Android versions?

The core logic is the same from Android 5 onward, but banner timing and menu wording vary across OEM firmware — worth accounting for when writing prelander hints for different geos.

How to Install a PWA on Android

Installing a PWA on Android takes a couple of taps — no Google Play listing, no store review, no APK download. Users see a native Chrome banner or a menu item, and the result is a home-screen icon that launches full-screen like a regular app. Here's exactly what that flow looks like and how to get more visitors to actually tap install.

What the user sees on a PWA landing page

When a site meets Chrome's criteria (HTTPS, a valid manifest, a registered service worker, minimum engagement), the browser automatically shows a mini-infobar at the bottom of the screen offering to add the app to the home screen. The user sees an icon, a name, and an Install button — visually close to a Google Play listing card. The banner doesn't fire on the very first page load: Chrome factors in behavioral signals like scrolling, time on page, and repeat visits.

Method 1: the automatic install banner

The highest-converting path is when Chrome shows the banner on its own and the user just taps Install. After the tap, Android fetches the manifest and icons and drops a shortcut on the home screen in 2-5 seconds — no store redirect, no APK permission screen. That near-zero friction between click and install is exactly why PWAs outperform native APKs in paid traffic funnels.

Method 2: manual install from the Chrome menu

If the auto-banner doesn't fire (first visit, an ad blocker, an older Chrome build), the user can open the three-dot menu and tap Install app or Add to Home screen. That menu option is available almost any time the site technically qualifies as a PWA — it's worth calling out with a short hint or GIF right on the prelander.

The technical requirements behind the banner

Chrome only offers the install prompt when there's a valid manifest (name, icons, start_url, display: standalone), the site is served over HTTPS, and a service worker is registered. Miss any one of those and the banner never shows, and Install from the menu can silently fail. Building on APEX, that's handled at the platform level — your storefront and domain are already configured to pass Chrome's install criteria.

How to increase install conversion

Conversion improves with the basics: a short prelander with a clear Install CTA, a clean icon and name with no caps-lock spam, and prompting for install after one or two user actions rather than on the very first screen. Split tests across prelanders and offer pages (sticky per visitor) show which combination drives more installs on a given geo — that's built into APEX, no extra tooling needed.

Common issues and OEM browser quirks

On some Android devices — Xiaomi/MIUI, Huawei, certain Samsung Internet builds — banner behavior differs: sometimes more aggressive, sometimes buried deeper in settings. If traffic arrives through an in-app webview from a social app rather than Chrome itself, PWA install may not be available at all, and you need a forced open-in-browser step. That's a common, hard-to-see cause of install-rate drop-off unless you break analytics down by browser.

FAQ

Do I need Google Play to install a PWA on Android?: No — installation happens directly through Chrome, with no store listing or store review involved.
Why doesn't the install banner show for some users?: Usually low engagement on the page, a non-Chrome browser or in-app social webview, or a missing technical requirement like HTTPS, the manifest, or the service worker.
Can I trigger my own install button instead of waiting for the Chrome banner?: Yes — capturing the beforeinstallprompt event lets you show a custom Install button and fire the native dialog on click, giving you control over exactly when it appears.
Does a PWA work offline after installing on Android?: Basic navigation does if the service worker caches assets; offer screens that need live data (casino, betting) typically still fetch online, but the icon and app launch behave like a native app.
Does the install flow differ across Android versions?: The core logic is the same from Android 5 onward, but banner timing and menu wording vary across OEM firmware — worth accounting for when writing prelander hints for different geos.

Build your PWA in APEX in minutes

Cloaking, anti-bot, push, split tests and your own domains — in one service.

Get started free