Docs·Web App·Trading Alerts

Web Push delivery

Browser-native push notifications via Firebase Cloud Messaging. Survives tab close, works on desktop and mobile, supports rich notification body. One-time permission grant + per-alert channel checkbox.

Web Push is the browser-native delivery channel — notifications pop on your desktop / mobile lock screen even when the platform tab is closed, as long as the browser is running and you've granted notification permission. We use Firebase Cloud Messaging (FCM) under the hood; per-platform behaviour follows the browser's own notification rules. Setup is one click — grant the browser permission when prompted — and after that Web Push is a checkbox on every alert.

Web Push permission prompt

How to enable

  1. Open the alerts inbox or any indicator alert dialog.
  2. Tick the Web Push channel.
  3. The browser prompts: "mrd-indicators.com wants to send notifications".
  4. Click Allow.
  5. A test notification arrives within ~5 seconds confirming setup.

If you previously clicked Block in step 4, the browser remembers — you need to manually re-enable in the browser's site-settings (see "Re-enable after a Block" below).

Per-browser notes

BrowserBehaviour
Chrome / Edge (desktop)Native OS notification; persists until clicked or auto-dismisses per OS settings.
Firefox (desktop)Same as Chrome.
Safari (desktop, macOS 13+)Supported; uses Safari's own notification pipeline.
Chrome (Android)Lock-screen notification.
Safari (iOS 16.4+)Requires installing as PWA first (Add to Home Screen) — see Add to Home Screen. After install, push works like a native app.
Chrome (iOS, any version)Not supported — iOS only allows Safari's notification pipeline. Use Safari PWA.

Notification format

Each push has:

  • Title — [mrD] Symbol TF Source.
  • Body — the alert message (templated; supports placeholders).
  • Icon — our brand mark.
  • Tag — collapses repeated alerts (so 5 RSI fires on the same pair don't queue 5 lock-screen items; only the latest shows with (×5)).
  • Action buttons (on desktop) — Open chart · Mute alert · Dismiss.

Click any notification → the platform opens to the symbol's chart with the alert's source indicator focused.

Service worker

Web Push works by registering a service worker (/firebase-messaging-sw.js) on the platform domain. The worker stays installed even after you close the tab; that's how lock-screen notifications can arrive without the tab being open. The trade-off — if you clear site data the worker uninstalls and you have to re-grant permission.

Re-enable after a Block

If you previously clicked Block:

  • Chrome / Edge — click the lock icon in the address bar → Site settings → Notifications → Allow.
  • Firefox — click the lock icon → Connection secure → More information → Permissions → uncheck "Use Default" for Notifications.
  • Safari — Safari menu → Settings → Websites → Notifications → set mrd-indicators.com to Allow.

After changing, reload the platform tab; a small banner offers to retry the test notification.

Per-device subscriptions

Each browser / device counts as a separate Web Push subscription. Sign in on your laptop and your phone → both receive pushes. To disable on one device:

  • Per-device toggle in the Account → Profile → Connected devices.
  • OR clear site data on that device.

Delivery latency

Same range as Telegram — 2-5 seconds typical. The FCM hop adds ~1s vs. Telegram's direct bot API. Background tabs / sleeping devices may queue several pushes; iOS specifically batches aggressively.

Common pitfalls

  • No notification despite Allow — the OS-level notification settings (Windows Focus Assist, macOS Do Not Disturb, iOS Focus modes) override browser permission. Check OS.
  • Notifications stopped after browser update — sometimes the service worker needs re-registration. Refresh the platform tab.
  • iOS not pushing — you must install as PWA first (Home Screen icon). Standalone Safari does not push.
  • Same alert pushing on 3 devices at once — by design. Disable per-device if you don't want all of them.

What's next