Re: [w3ctag/design-reviews] Web Install API - Same Origin (Issue #888)

Hi @diekus, after reading your comment both @plinss were still confused about several aspects of this API:

Wrt `related_applications`:
- We don’t understand what the use cases are. Say, I have a website with a manifest file. _Why_ would that website prefer to be installed from another repository instead of using itself as the source of truth? What are the use cases? Is it monetization? Analytics? Something else?
- Orthogonal to the use cases, it seems like it would require the Cross-Origin version of the API to work? How is `related_applications` useful if it's restricted to the same origin?

Wrt installing multiple PWAs from the same origin and `related_applications` / `prefer_related_appliations`:

When separating the API into a same-origin and a cross-origin version, it’s important that the separation is "clean", i.e. that the same origin version can be implemented independently and no parts of it should require the cross-origin version of the API. With that in mind:
- It is unclear to us what same origin use cases the parameters of the `navigator.install()` function serve, since it seems they are primarily geared around verification, which is not really needed in the same origin case. 
- Same for the arbitrary `referral-info` parameter: what is the use case for it in a same-origin context?
- Same for `related_applications` / `prefer_related_appliations`: it seems that for these to function they require the cross-origin version of the API?

Also, given the text in the explainer, it is still unclear to use what the author flow is for e.g. having a website that includes multiple apps (`website.com/foo`, `website.com/bar`, etc.). A code example would help! 

We also don’t quite understand the signature of `navigator.install()`: it seems that `manifest_id` is optional but it is possible to provide `manifest_id` without `install_url`. What is the use case of that in a same-origin context? It also seems like in the case of a single website containing multiple apps, one would probably want to provide an install_url, and it seems like it's the manifest id that should be optional?

Also please note that TAG principle around [preferring a dictionary for optional arguments](https://www.w3.org/TR/design-principles/#prefer-dictionaries).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/888#issuecomment-2070133317
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/888/2070133317@github.com>