Re: [w3c/manifest] Allowing only site-triggered install prompt (#627)

Thanks @MatteoWebDesigner for the input. I share your concerns that there will be (or there is already) so much variance across browsers that helping uses will actually require UA sniffing (and showing help screens specifically for each to help users manage their PWA installations). 

To reframe the constraints which would need to be in place for `.install()` (using some web spec jargon):

 * Must be "SecureContext" (means basically HTTPS)
 * Must be triggered by user activation (click).
 * only possible on top-level browsing context (no iframe). 
 * Optional, time limited (like pop-up blocker rules). 

I think some "installability signals" requirements might be too onerous (e.g., MUST have a service worker, MUST be mobile capable, etc.). We could simplify it to the above.  

Then we just block away the `beforeinstallprompt` stuff. We get most of the benefits we (browser vendors) are after... and we make devs happy, because they have control over installation process.  

@mgiuca, thoughts? 



-- 
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/627#issuecomment-381488857