Re: [w3c/manifest] beforeinstallprompt : Prompting user makes it to hard to discern whether the user truly wanted to "install" a web app (#835)

> we don't think it's needed

@marcoscaceres Care to elaborate on this?

...I want you all to imagine that you are a developer or running a product.  Next I want you to imagine that you've built a beautiful web app, PWA, ..."web thingy that installs"

Then I want you to imagine, that a user asks..."How can I install your web app?"

How would **you** answer that question? You would have to give them a different set of directions for **every** browser, because every single one of these browsers is going to do something different with their elegant badging/ceremonies. Not to mention they all call **web apps** something entirely different.

...Now imagine a brand/app specific UI that directs them to install the app with an API that functions similar to `beforeinstallprompt`, that works/behaves consistently no matter the browser. I've attached an example...ignore the placeholder..it doesn't matter. The user clicks install, it opens a browser specific confirmation/prompt/whatever.

The only _real_ reason I can imagine browser teams avoiding implementing this is because they are worried about bad actors/abuse/whatever...they've got **post push notification permission request disorder**...and listen, _I get it._  Nobody likes being prompted every two seconds as they peruse the web. **I'm sure there are things we all learned from that implementation.**





-- 
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/issues/835#issuecomment-564578752