Mobile Notifications

How alerts reach your phone today (responsive web) and what changes when the native app ships (Phase 2).

Today (responsive web)

Three channels reach mobile:

Email — daily digest by default (6 AM ET, configurable).
Web push — works on Android Chrome, iOS Safari (PWA mode only), and most desktop browsers.
In-app inbox — /alerts shows all fired alerts when you visit the app.

SMS is reserved for security events only (MFA, password reset, dispute); no marketing alerts via SMS.

Setting up web push

Create at least one alert subscription (/alerts → New).
Browser prompts for notification permission. Approve.
From there, alerts that match the subscription deliver via push.

If you missed the prompt:

Chrome: lock icon in URL bar → Site settings → Notifications → Allow.
Safari (iOS PWA): Settings app → Notifications → BlitzPulse → Allow.

Why iOS Safari requires PWA mode

Apple gates web push behind the Add to Home Screen install on iOS. A regular Safari tab never gets push, regardless of permission state. This is an Apple platform restriction — see mobile setup for the install steps.

When push fails

Push payload sizes are limited; we send a short title + body and rely on you opening the app for detail.
Push delivery p95 is <30s from server detection; if consistently delayed, check your phone’s “Background App Refresh” setting and re-allow notifications.

What changes with the native app (Phase 2)

Native push via APNs (iOS) and FCM (Android) — no PWA install needed.
Rich notifications with charts and mini-payoff visuals.
Background refresh keeps the app current without you opening it.
Notification sounds + categories (price alerts vs digest vs reconciliation).

Until then, the responsive-web push pipeline is the supported path.

Privacy

Push payloads contain only the alert summary (symbol + reason). Position sizes, P&L, and account details are never embedded — those load on app open. We never sell or share notification subscriber lists.