Install prompt timing is conversion design, not browser trivia

Why this matters

web.dev installation prompt guidance starts with a practical truth: users may not be familiar with the PWA install process, and developers are in the best position to know when it is the right time to invite installation. That means the prompt is part of product design, not merely browser API usage.

What changed

The documentation discusses enhancing the install dialog, the beforeinstallprompt event, prompt placement, analytics, fallbacks, and libraries. The common thread is timing: a prompt should appear when the user understands the value of keeping the app, not when the page wants a metric.

What builders should check

• Map the user moment that proves repeat value.
• Use in-product education before calling the browser prompt.
• Track prompt impressions, acceptance, dismissal, and later retention.
• Provide a manual install path for browsers without the same event behavior.
• Do not block core content behind installation.

OpenPWA angle

OpenPWA should treat install prompt design as conversion ethics. The goal is not to maximize interruption; it is to help the right user keep the right app at the right moment. That is the difference between app discovery and dark-pattern distribution.

Sources:

• web.dev: Installation prompt