Mobile App
The Quazzar mobile app (iOS + Android, Phase В.4) gives you a paired view of your OS instance from your phone. The setup flow is built around a QR-pair handshake — there’s no email/password screen, you authenticate by scanning a code shown on your server’s web UI.
What’s in v1
- Dashboard — system metrics, app status, recent alerts.
- Monitor — spike attribution view; tap a spike to see which OS subsystem the rolling baseline blamed it on.
- Apps — list / start / stop / restart your installed apps.
- Molly — text chat with the OS-side AI assistant. Voice mode is deferred to a follow-up release.
- Alerts — full alert history with severity filters. Push notifications deep-link straight to the right alert.
- Settings — server selector, push toggle, sign-out.
Pairing your phone
- On your desktop, open Quazzar and go to Settings → Connected Devices.
- Tap Pair phone. The OS shows a QR code (valid for 5 minutes).
- Open the Quazzar app on your phone. It opens to the pair screen with the camera already focused.
- Point the camera at the QR. The screen shows “Pairing…” while the OS mints the relay JWT and stores the device record.
- Once the handshake succeeds you land on the Dashboard.
The phone keeps a long-lived bearer token, so you only do this once per phone-server pair. If you re-install the app, you’ll need to scan again.
Push notifications
When you grant notification permission during onboarding, the app uploads its FCM/APNs token through the pair tunnel up to CP. CP fans new alerts out to every paired device on your instance.
You can toggle pushes per-app in Settings → Notifications. To
disable a single device without uninstalling the app, your CP admin
can mute it via POST /api/v1/devices/{device_id}/mute.
Plan caps:
| Plan | Devices per phone | Push per day |
|---|---|---|
| Community | 2 instances | 50 |
| Pro | 5 instances | 500 |
| Team / Enterprise | unlimited | unlimited |
Privacy
- The QR code is only valid for 5 minutes and is single-use.
- Pair traffic between your phone and the OS is end-to-end encrypted
through the CC relay — see
mobile-pairing-protocol.mdfor the wire spec. - Your push token lives only on CP; FCM/APNs sees the token but never the message body (your alerts are template-rendered server-side and the body field is short, but you can mute push entirely if you’d rather not transit Apple/Google at all).
Operator setup
If you’re the operator running CP for a fleet, follow Mobile Push Setup to provision the FCM service account + APNs key.