Migration Demo

current page context

related installed apps

Uses navigator.getInstalledRelatedApps() as a surrounding install-context probe. PWA origin migration itself is manifest-driven by migrate_from and allow_migration, not by this API.

migration verification steps

Chrome performs these checks before migrating an installed PWA to the new origin:

• 1 Destination manifest.json includes a stable id scoped to the new origin
• 2 Destination manifest.json includes migrate_from naming the installed old app ID
• 3 Old origin hosts /.well-known/web-app-origin-association with allow_migration: true under the destination app ID
• 4 Chrome confirms the origins are same-site and can fetch the destination manifest plus old-origin association file
• 5 Chrome presents an update-style migration prompt, or a blocking prompt when behavior: "force" is set

code

// Check for related installed apps
// (Chrome checks this during origin migration too)
if ('getInstalledRelatedApps' in navigator) {
  const apps = await navigator.getInstalledRelatedApps();

  if (apps.length) {
    // A related app is installed — useful install context,
    // but PWA origin migration is driven by manifest fields.
    for (const app of apps) {
      console.log(app.platform, app.url, app.version);
    }
  } else {
    // No related apps — fresh install scenario
  }
}

// Detect if running as installed PWA
const isInstalled = window.matchMedia('(display-mode: standalone)').matches
  || window.matchMedia('(display-mode: minimal-ui)').matches
  || window.matchMedia('(display-mode: window-controls-overlay)').matches
  || navigator.standalone === true;

see also

• Manifest Configuration
• ChromeStatus entry
• MDN — Progressive Web Apps