When a user selects "Add to Homescreen" from the app menu, we generate a web app even if the Web Manifest does not contain any "icons". We fall back to using the page favicon.

We have been operating with the assumption that we will generate WebAPKs for web manifests with no icons and fall back to the page favicon as well.

Dominick mentioned (offline and via code review) that:
- We currently require the Web Manifest to have non-empty icon URLs in order to display the add-to-homescreen banner
- Falling back to the page favicon for WebAPKs would add a bit of complexity

Sam, what is the desired long term behavior? Should we generate WebAPKs for Web Manifests with no icon URL. According to Glenn's spreadsheet, 96% of Web Manifests also contain an icon

Dominick is suggesting not generating WebAPKs for Web Manifests with no icon URL for the dev preview (regardless of what the long term decision is). I am fine with this decision

Given
"- We currently require the Web Manifest to have non-empty icon URLs in order to display the add-to-homescreen banner"

I agree with not creating a WebAPK in this case. Add to homescreen menu resulting in a WebAPK should only override engagement checks for the banner - not offer differing triggering logic.

Agreed with Yaron -- no reason to introduce a difference here. Given that the vast majority of sites have icons (probably even more as a % of PWAs) I don't think it's a big issue.

Decision made, marking as fixed