MEGAINFRA-WEBAPP/docs/pwa-install-verification.md

2.4 KiB

Manual PWA install verification

After the icons ship and HTTPS is live, install each app on real devices and confirm they appear as two separate apps with the right names and icons.

What to confirm

For each device class, you should see two distinct app tiles:

Route App name Icon
/dashboard MEGA OPS Existing dashboard cube icon
/dashboard/chat Ask (or "MEGA Ask" on the long press / info screen) New chat-bubble + cube icon

If you see one tile only, or one tile with the wrong icon, something is wrong — either the second manifest didn't install (HTTPS check failed) or the icons got swapped.

macOS (Chrome or Edge)

  1. Visit https://<your-domain>/dashboard in Chrome or Edge.
  2. Click the install icon in the address bar → "Install MEGA OPS".
  3. Visit https://<your-domain>/dashboard/chat.
  4. Click install again → "Install Ask".
  5. Open chrome://apps (or Edge's equivalent). Confirm two distinct entries:
    • "MEGA OPS" with the dashboard cube icon
    • "Ask" with the orange chat-bubble icon
  6. Launch each one — it should open without browser chrome (no URL bar, no tabs). The two apps are independent processes but share cookies/auth.

iPhone (Safari)

  1. Visit https://<your-domain>/dashboard in Safari.
  2. Tap the Share button → "Add to Home Screen". Confirm the name "MEGA OPS" and the dashboard cube icon. Tap Add.
  3. Visit https://<your-domain>/dashboard/chat.
  4. Tap Share → "Add to Home Screen". Confirm the name "Ask" and the chat-bubble icon. Tap Add.
  5. Look at the home screen. Two distinct icons.

Android (Chrome)

  1. Visit https://<your-domain>/dashboard in Chrome.
  2. Either tap the install banner (if it appears) or use the menu → "Install app" / "Add to Home screen". Confirm name "MEGA OPS".
  3. Visit https://<your-domain>/dashboard/chat.
  4. Install again. Confirm name "Ask".
  5. Launcher should show two separate icons.

Behavioural expectations

  • Auth/session: shared. Logging in from either app logs in both. This is desired — both apps live on the same origin and use the same login flow.
  • Offline / cached data: shared service worker. If you install both apps, go offline in one, and notice stale data when you open the other, that's the symptom of a shared SW. If that surfaces as a real problem, scope a second SW to /dashboard/chat — but don't preemptively build it.