Re: [w3ctag/design-reviews] Incubation: PWA (same-site) Origin Migration (Issue #1164)

Dp-Goog left a comment (w3ctag/design-reviews#1164)

> Relying solely on HTTP redirects would prevent migrations where the URL does not change. For example, a developer might have accidentally (or intentionally) created multiple PWA installations on the same origin (e.g., via different start_url paths) and now wishes to consolidate them into a single identity. In this "Split App" scenario, there is no HTTP redirect because the paths remain valid; only the manifest identity is changing.

Thank you for your reply. Sure, let me explain with a valid use-case. Consider that the developer has created 2 hypothetical apps:
1. `page.com/video/` with a valid manifest at `page.com/video/manifest.json`
2. `page.com/meet/` with a valid manifest at `page.com/meet/manifest.json`

Now if the developer wants to rebrand to a single app that contains both urls (`/video/` and `/meet/`), since they're both valid urls, one will not redirect to the other. Thus users will be stuck in one app or the other (or both if they have installed them), leaving the developer with no way to migrate them to a single app.

Please let me know if this makes sense.

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

Message ID: <w3ctag/design-reviews/issues/1164/4112250730@github.com>