Adding publisher

[aarongustafson]

Super-early thinking here. Feedback very welcome.

[tomayac]

I like the general direction, but may I suggest you build upon the web-app-origin-association file that was introduced in the context of URL handling. Here's the explainer deep link.

[aarongustafson]

@tomayac I had thought about that, but wasn’t sure if it might lead to confusion if the file exists within the individual PWAs and then again (to an extent) on the publisher’s site. I think the URL handling aspect is pretty complex in and of itself and I didn’t want to overload it.

I also wasn’t sure if it would cause a problem if we dropped details in that context. Totally open to your thoughts here.

[tomayac]

The web-app-origin-association file format already contains a "manifest" field, so I think this could easily work. Something to consider might be to factor in the new unique ID into the verification algorithm.

{
  "web_apps": [
    {
      "manifest": "https://music.example.com/manifest.json",
      "details": {
        "paths": ["/*"],
        "exclude_paths": ["/internal/*"]
      }
    }
  ]
}

[aarongustafson]

@diekus @marcoscaceres Thoughts on this proposal?

[tomayac]

Still thinking about the verification aspect. The web-app-origin-association file is similar to Apple's associated domain file, Android's assetlinks.json file, and Windows' windows-app-web-link file. What differs is that the web-app-origin-association file does not reference PWAs using a platform-specific app