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

@rniwa As the initial requester of this feature [on the WebKit bugtracker](https://bugs.webkit.org/show_bug.cgi?id=193959), first of all, thanks for openly engaging on this. 

I think people on this Issue thread mix a couple of not necessarily related (yet admittedly close) things:

1. Gating permissions on the installed state.
1. The way a prompt or ambient install badge would be shown.
1. The terms used to ask the user ("install" vs. "add to home screen" vs. "…").

For 1., this *can* happen at the UA's discretion, but certainly doesn't have to happen. The spec, as far as I can tell, makes no assumptions in this direction.

For 2., this *can* be an annoying overlay like the notifications prompt on many UAs, but it can also be a subtle (+) in the URL bar or anything else the UA in question comes up with.

For 3., this is completely up to the UA to decide, experiment, and optimize.  

The way I understand `beforeinstallprompt` is that it allows the developer to time the prompting right (e.g., don't ask immediately after loading, but maybe wait until a meaningful page action has happened, which could be "an item was purchased", "an article was read",…). This gives back control to the developer.

Apple has pioneered the concept of [Web Clips](https://www.apple.com/newsroom/2008/01/15Apple-Enhances-Revolutionary-iPhone-with-Software-Update/) way back in 2008, maybe there is a chance for Apple to evolve it in 2020, and incorporating some of the learnings from [Smart App Banners](https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariWebContent/PromotingAppswithAppBanners/PromotingAppswithAppBanners.html)?! 




-- 
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-564076432