Monarch is built to run as a mobile PWA. Installation gives users a home-screen entry point and app-like chrome, but it should not be the first trust gate.
When to prompt
Prompt for install after a user has seen value, such as loading read-only account state, reviewing markets, using the journal, or creating a preview.
Do not interrupt active preview, confirmation, pause, revoke, or blocker recovery flows.
What can be cached
The PWA may cache:
- Static app shell.
- Fonts and icons.
- Non-sensitive docs and help assets.
- Last public market metadata snapshot with expiry.
What must not be cached
The PWA must not cache:
- Execution plans after expiry.
- Private account snapshots.
- Signatures.
- API wallet secrets.
- Confirmation payloads.
- Full assistant transcripts containing trade intent.
Offline behavior
Offline mode is read-only. If Monarch is offline, preview refresh and confirmation are blocked.
Cached public market context can still help orientation, but stale or missing private state must not appear executable.
Install routes and manifests
Monarch pages use the Monarch manifest and should keep the start URL aligned to /monarch. Companion implementation routes may exist internally, but user-facing install behavior should point to Monarch.
Related pages
- Monarch/PWA Overview: See where installation fits in the companion app.
- Wallets and Account State: Understand account readiness before execution setup.
- Troubleshooting: Check common account, preview, and wallet states.