Originally published on the QueueFly blog — canonical URL points to the original.
Most guides about push notifications stop at the SDK snippet. That's the part Firebase makes easy — and it's why so many teams discover, mid-incident, that they shipped a demo, not a system. This guide covers what actually happens between "your code calls send()" and a notification appearing on a phone in another timezone, and the operational machinery nobody puts in the tutorial.
I've spent 15+ years building backends in payments and banking, where "the message didn't arrive" is an incident report, not a metric. I now build QueueFly , which is what I wished existed the first ten times I rebuilt this from scratch. This guide is vendor-neutral first — the product angle comes last, honestly labeled.
How push delivery actually works
Every push notification travels the same path, regardless of what anyone's marketing page says:
Registration. The app asks the OS for a device token — from FCM (Android/web), APNs (iOS), or both.…