Repository navigation
beforeinstallprompt #106
Description
This GitHub issue is for collecting web developer signals for beforeinstallprompt.
The beforeinstallprompt event fires when a Progressive Web App (PWA) is installable. You can cancel the event and later call event.prompt() to control when the installation prompt is shown. The appinstalled event fires when the PWA is successfully installed.
Browser support
- Chrome 76 (Jul 30, 2019)
- Chrome Android 76 (Jul 30, 2019)
- Edge 79 (Jan 15, 2020)
- Firefox: not supported
- Firefox for Android: not supported
- Safari: not supported
- Safari on iOS: not supported
Give us feedback
If you're pressed for time, but you want this feature to be available in all browsers, please give this issue a thumbs up 👍 reaction.
However, a much better guide for us is to know how you'd use this feature, and what you're having to do in the meantime. This helps us judge the priority versus other features.
Copy the template below in a comment, and add the details that matter to you.
## What I want to do with this feature
<!-- Add your specific use-cases, even if they seem obvious to you. -->
## What I'm having to do in the meantime
<!--
Are you having to use another feature instead, a polyfill, or is it blocking you completely?
Why are the alternatives worse than using this feature?
-->All comments are expected to adhere to the Code of Conduct.
Learn more
You can learn more about this feature here:
Activity
celly-rocely commentedon Jul 27, 2026
What I want to do with this feature
We run Rocely, a recipe and meal-planning PWA. Users
who install it to their home screen come back far more often than users who
just bookmark it, so a reliable install step matters for retention.
We want one install flow that works the same way regardless of browser,
instead of branching our UI based on what the browser supports.
What I'm having to do in the meantime
beforeinstallpromptworks on Chrome and Edge. On Safari and Firefox wefall back to static, browser-specific "Add to Home Screen" instructions.
I tried the community polyfill at
https://github.com/easy-pwa/beforeinstallprompt-polyfill to see if it would
close the gap. It doesn't. On browsers without a real install API, it fires
a synthetic
beforeinstallpromptevent, then shows the same manualinstructions we already have. It changes the code, not the outcome.
At least three separate npm packages exist to paper over this gap:
That's nearly 80,000 weekly installs of workarounds for one missing browser
feature.
The manual flow costs us installs. On iOS, that's:
Four steps loses people at every stage, compared to a single native prompt.