multiple pwa on same origin could be conflicting for app scoped to path

[hemuio]

multiple pwa on same origin with different path could be conflicting, at how pwa over path app opens and their installations by browsers

where origin/home is taken implicitly host of other as usually scoped in such manner, and how browser behave, that may not be the case intended, and pwas that are taken as sub of host may have their seperate existence and scope to themselves first

these issues could be resolved through path ones ((origin)/(path)) given higher precedence over origin/host if scope is declared
or new manifest key that explicit it somehow, determined how browser behave to each by declaration, as there is already "scope" key then precedence would resolve, yet there could be more where new key would be suiting.
then atleast those path scoped pwa will open in their own window/pwa session then in host, even if origin scoped app installed

[dmurph]

We have guidance here: https://web.dev/articles/building-multiple-pwas-on-the-same-domain

The longest scope is given precedence.

Does that clarify things?

[hemuio]

i read that, from where i find path scoped if given precedence over origin/host/domain, then would be convenient for developers to host pwa on same origin with path differences and functions align accordingly, and also could be better user experience

For example, in browser(chrome/firefox) a web version pwa opened that is path scoped and installed on device, currently browser pick origin pwa installed not path scoped even if its installed, as it is directly mapping scope thus should be given priority over resolution which pwa to pick open that page

or could forget the path(complicating too much) and just explicit scoping should be enough for determination, if origin or path, pick just as stated in manifest

what do you mean by the longest scope given precedence? by character length? how longest determined, on what parameters?

[dmurph]

I'm not sure I really understand. The scope length is the length of the resolved scope field in the manifest. So:

• app A scope is www.example.com/apps/foo/
• app B scope is www.example.com/apps/

The url www.example.com/apps/foo/a.html is controlled by app A, because out of the two apps that have the url in their scope (A and B), app A's scope field is longer.

If you have a specific feature request or spec problem can you clarify?