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

> Different browsers can have different dynamic (engagement) requirements
I don't agree, you will end up with the following on every website. 
```
you should be prompted for installation automatically but: 
- If you are a X user: wait 5s
- if you are a Y user: click somewhere
- if you are a Z user: visit the site twice 
```

> What's weird about this is that we allow sites to spam notification permission requests immediately (which arguably is requesting a more invasive capability than installation), but we're more conservative with showing the install prompt. I think we should be more consistent about this.
Definitely. And educate developers is the way to go. Today, it's obvious that ask for a permission without context will lead to high rate of "block".
It is not the UA role to show a prompt when it decides to. It's like automatically ask for geolocation permission if the GPS is active on the terminal.
There is a requirement -> UA check the requirement -> requirement is satisfied -> UA allow the developer to prompt the enduser -> developer prompt the user at the right time in his context

> I think at the moment we're still early on in the life cycle of this feature, and people are worried if we codify this, we won't be able to increase the requirements later
Agree, but we are already in the "later" part
Edge made a move with auto index PWA depending of their own quality criteria and Chrome already gives guidelines in lighthouse.
check "quality signal of progressive web app part" https://blogs.windows.com/msedgedev/2018/02/06/welcoming-progressive-web-apps-edge-windows-10/
Edge considers service worker as an ehancement when it's big warning in lighthouse if it's missing.



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