Re: [w3c/manifest] Document the unique identifier or tuple of identifiers for a PWA (#586)

Interesting that so many of them are versioned. I wonder where this advice comes from? Could it be that "best practice" with service workers is to version all assets, and the manifest is just being versioned along with that?

> So if Chrome and others switch to using manifest URL to uniquely identify PWAs ... then around 5% of sites will generate a new A2HS prompt when the manifest URL changes

I think there's still some confusion here. Chrome already uses the manifest URL to uniquely identify an app. If the manifest URL changes, it's a different app. There are no changes to Chrome that need to be made along these lines (this bug is to *document* this in the spec, which I think is reasonable).

> Is Chrome using manifest URL right now? I tried changing the manifest URL on a test site and didn't get the A2HS prompt. So I suspect Chrome is currently applying a different heuristic to identify new/updated PWAs.

I think it is. If you change the manifest URL you should get a new app. Theories for why you aren't:

- When you changed the manifest URL, the new manifest didn't satisfy the PWA checks.
- Someone mentioned that Chrome for Android has a limit of 3 apps per origin. It's possible you hit that limit?
- I'm mistaken and Chrome for Android is in fact using the start_url or something as the unique key.

-- 
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/586#issuecomment-386933947