FYI: Making 'beforeinstallprompt' event in Chromium dependable by developers for install (by removing interaction requirement)

[Dan Murphy]

Hello folks,

We are planning to remove the engagement requirement for the 'beforeinstallprompt' event in m131. There is a feature flag still so we can undo this in the future if needed (`kBypassAppBannerEngagementChecks`). This is from a long culmination of feedback from developers and partners that the unreliability of this event was a deal-breaker for ever using it.

Adding folks from the "Question around PWA beforeInstallPrompt not firing" email as FYI as well.

Thanks!

Dan

[Dan Murphy]

-David (email doesn't work).

Yes and we are going to enable it by default, likely today (here).

On Thu, Oct 10, 2024 at 9:02 AM Thomas Steiner <to...@google.com> wrote:

Hey Dan,

Exciting update! I think that's a step in the right direction. We've definitely heard the unreliability feedback before, so great to hear that we're working on a response. The corresponding flag for testing this early seems to be `chrome://flags/#bypass-app-banner-engagement-checks`.

Cheers,

Tom

--

Thomas Steiner, PhD—Developer Relations Engineer (blog.tomayac.com, toot.cafe/@tomayac)

Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany
Geschäftsführer: Paul Manicle, Liana Sebastian
Registergericht und -nummer: Hamburg, HRB 86891

----- BEGIN PGP SIGNATURE -----

Version: GnuPG v2.4.3 (GNU/Linux)

iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck

0fjumBl3DCharaCTersAttH3b0ttom.xKcd.cOm/1181.

----- END PGP SIGNATURE -----

[Dan Murphy]

Circling back: This is now the behavior by default in m131: https://chromiumdash.appspot.com/commit/ce05a019cac87a05210efd6d8f6fdfeea3252e77