[Tracking] Push notification follow-ups after #417 #447

Summary

#417 fixed push delivery and recovery with the smallest change. These items were kept out of its scope on purpose. Each one is optional. File a separate issue for an item before building it.

• Area: push notifications
• Source: Bring back push on Chrome and Android devices the server switched off #417 "Out of scope", and the 2026-10-06 push review

Candidates

• Per-device online suppression. Today one visible tab on any device suppresses push to all of that person's devices (is_user_online). Suppress per device instead.
• Deactivation metric and alert. Count subscriptions switched off, by reason (404/410, failed count), and alert on a spike. The FCM outage of 2026-08-09 went unnoticed for two months.
• VAPID keys in the worker health check. Push is silently off when VAPID_PUBLIC_KEY or VAPID_PRIVATE_KEY is missing.
• Key match at deploy. NEXT_PUBLIC_VAPID_PUBLIC_KEY (build time) must equal VAPID_PUBLIC_KEY (runtime). Check it in the deploy workflow.
• Android badge icon. favicon-32x32.png is fully opaque, so Android shows a white square. Use a 96×96 white-on-transparent badge (design system rules apply).
• Test-push button in Settings → Notifications.
• Faster save after pushsubscriptionchange. The client saves the new endpoint within a day. Save it on the next load instead, if the endpoint changed.

Related

• Bring back push on Chrome and Android devices the server switched off #417