Re: [w3c/manifest] Procedure for moving manifests and Apps (#850)

@aesinnllc - You are watching this thread or repo, thus receiving email every time someone replies to it. Unsubscribe to the thread or at https://github.com/watching. (Nobody is directly sending you email related to this.)

@RealAlphabet - While I sympathize with wanting to change your domain name and stop paying for the old one, it is simply not possible to do that safely due to the architecture of the web. This extends far beyond PWAs. (If you had 400,000 users on a regular website that isn't a PWA, you would still need to maintain the old domain to host a redirect in perpetuity.) Cookies, storage, permissions, are also tied to the origin. If you want to change your domain name, you are essentially starting a new app from scratch.

Even if we did implement a procedure for moving PWAs from one origin to another, you would still be required to maintain a presence at the old origin to declare the new domain to hand off to. (Though I suppose you could decide to stop paying for the old domain after 1-2 years after you consider most of your users to be migrated.)

For same-origin moves, I believe this is basically solved.

> since the manifest URL is the stable identifier

The manifest URL has never been the stable identifier; it was traditionally the `start_url`. So you should have always been able to move the manifest to a new URL (on the same origin) and have the pages point to the new location, then the updater will check the new location of the manifest.

For the past year or so, we have added the `id` field which is now the stable identifier, so you can actually change the `start_url` as well, as long as you keep the `id` set to the value of the old `start_url`.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/850#issuecomment-1888381649
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/850/1888381649@github.com>