v147 · PWA · demo

Manifest Config Explorer

Build the PWA origin migration handshake with the current manifest fields: migrate_from on the new app, allow_migration in the old origin association file, optional migrate_to on the old app, and install_url for redirect-safe updates.

Migration scenarios

Each button regenerates the manifest JSON and validation result. The checks model the current same-site handshake; they are not generic PWA capability probes.

eligible

Migration can be suggested to the user

The new manifest names the old app, the old origin explicitly authorizes the new app, and both origins are HTTPS and same-site.

New app manifest https://files.example.com/app/manifest.json

      
Old origin association https://drive.example.com/.well-known/web-app-origin-association

      
Old app manifest https://drive.example.com/manifest.json

      
live validation

Handshake requirements

  • pending HTTPS origins
  • pending Same-site migration
  • pending Destination manifest id
  • pending migrate_from declaration
  • pending allow_migration authorization
  • pending User-visible behavior
  • pending Redirect-safe install_url

Field reference

Field or file Where it lives What Chrome uses it for
migrate_from New app manifest Declares the old app identity that may migrate into this destination app.
/.well-known/web-app-origin-association Old origin Authorizes the destination app with allow_migration: true, preventing unilateral takeover by another site.
migrate_to Old app manifest Optional proactive signal that points an installed legacy app at the destination app.
behavior Inside a migrate_from object suggest allows an ignorable update; force blocks launch until the user updates or uninstalls.
install_url migrate_from or migrate_to object Keeps a non-redirecting install page available when old app routes redirect to the new origin.

references

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗