Contact emails
m...@chromium.org
Explainer
https://github.com/WICG/manifest-incubations/blob/gh-pages/pwa-migration-explainer.md
Specification
No information provided
Summary
When a user installs a Progressive Web App (PWA), its identity and security context are tightly bound to its web origin (e.g.,
app.example.com). This presents a significant challenge for developers who need to change their PWA's origin due to rebranding, domain restructuring, or technical re-architecture. Currently, such a change forces users to manually uninstall the old app and reinstall the new one, leading to a disruptive experience and potential user loss. This proposal introduces a mechanism for developers to seamlessly migrate an installed PWA to a new, same-site origin, preserving user trust and permissions.
Blink component
UI>Browser>WebAppInstalls
Web Feature ID
Missing feature
Motivation
Imagine you have the "SocialApp" app installed on your computer from
www.example.com/social. One day, the company decides to move the app to its own dedicated home at
social.example.com. Without a migration mechanism, the app you have installed would either break or redirect you to the new site in a generic browser window, losing its app-like feel. You would have to figure out that you need to uninstall the old app and install the new one from the new address. You might also lose your settings, like whether you've allowed the app to send notifications.
This feature aims to make that transition seamless. Instead of a broken experience, the app would notify you of an available update. With your approval, the app would relaunch from its new home at
social.example.com, with your notification settings intact.
Initial public proposal
https://github.com/WICG/manifest-incubations/pull/121
Requires code in //chrome?
True
Tracking bug
https://issues.chromium.org/396504527
Estimated milestones
No milestones specified
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5123349239955456?gate=5161507205808128