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

Thanks everyone for your input. Good point from @firtman about being able to check if the app is already installed - it's definitely a requirement. 

I think we now want input from stake holders/implementers: 

 * @mgiuca and/or @slightlyoff (Alex originally proposed  `beforeinstallprompt`, so I think his input would be really great here now that we've seen this play out over the last few years), 
 * @andreasboven from Mozilla (who did a lot of the pioneering work on ambient badging at Opera) and @snorp (who is working on Firefox for Mobile and has opinions around this),
 * and from the folks at Microsoft who are working on PWAs, like @patrickkettner and others. 

If we get consensus that the current UX situation is not ideal, then we can start considering adding an API based on the requirements listed thus far:

 * Must be "SecureContext".
 * Must be triggered by user activation.
 * By default, only exposed on top-level browsing context. 
 * Optional, time limited (like pop-up blocker rules or rate limited payment request).
 * Must provide a means to check if app is already installed. 
 * For backwards compat, browsers can continue to use ambient badging, installability signals, etc. 
 
Anything I've missed? Awaiting implementer interest before continuing. 

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