Re: [w3c/manifest] Remove beforeinstallprompt and appinstalled events. (#836)

We also publish an installable PWA. In Firefox it’s not installable, of course, and we document in our FAQ that the application isn’t installable from all browsers, but to date I’ve thought of this as falling somewhere in the progressive enhancement realm sorta. The application remains usable in Firefox, just as it remains usable in Chrome, etc, without installation. This seems pretty important given the user can choose not to install even in a browser where installation is supported, and likely wouldn’t want to install until first using it enough to decide that doing so would be worthwhile. (To me this seems like the rare case where “the gap” is reversed — PWAs have a fantastic capability in this regard that _native apps lack._)

So your comment made me curious @briantbutton: what does “not support Firefox” mean for your app in practice? Do you mean: 

- “we don’t sweat it that FF users can’t install”
- “because FF doesn’t have this feature, we officially don’t consider FF supported, but the app might work there anyway”
- “we prompt users to use a different browser (but they can dismiss the prompt)”
- “we outright block FF usage”
- something else

Again, just curious — I haven’t heard of doing anything but the first before. Hopefully OP will forgive a bit of topic drift — it’s good to learn more about how people are really responding to the state of things I think.

FF usage seems to be getting so low now that all of this might be theoretical in another year or two anyway, for better or worse ... :(

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/836#issuecomment-841875650