apps/phone/ or writing a new client.
What this client is
A paired device, not an inbox. It holds an Ed25519 secret, signs/papi/*, and
optionally wakes via Expo Push.
Protocol pages: Mobile clients, Apps overview.
Path A — Reference app (apps/phone)
Prerequisites
- Node.js 20+
- Expo / EAS account
- Physical device for push (simulator is insufficient to sign off)
- Apple Developer membership for iOS
1. Install and test
2. Configure push credentials
3. Build for a device
4. Pair and verify
- Mac shows pair QR → scan in app → allow notifications.
- Settings: alerts registered.
- Dashboard → Send test alert → banner while app backgrounded.
- Optional: create a real approval and decide.
Path B — Your own app
Implement:- Pairing
- Device signing
- Phone API
- Push — your EAS/APNs project; node only stores tokens
Invariants
- Never put mail content in push payloads
- Never put the device secret on your servers
- Never use the Mac dashboard
X-FAU-Localtoken from mobile - Polling remains mandatory even when push works
Next
- Run a node
- Extend the codebase if changing
/papi