One push. A million phones.

Understand it one step at a time

The short runs these in order in about 32 seconds. Here they are written out — pick any step to jump the short straight to it.

1. 1

   Send this to a million phones

   One line of copy, one send button, and 1,000,000 devices that need to hear about it.

   MSDevMart · 1,000,000 devices · send now

2. 2

   Three platforms, three of everything

   APNs wants a .p8 key, FCM wants a service account, WNS wants a package SID. Different payloads too.

   APNs · FCM · WNS · 3 credential formats

3. 3

   The loop finishes tomorrow

   A million sequential HTTP calls at 44 a second. The sale it was announcing ended hours ago.

   loop · 44 devices/sec · 6h 12m remaining

4. 4

   Fix: Azure Notification Hubs

   One send to the hub. It holds the credentials, the registrations and the per-platform payloads.

   msdevmart-push · 1 send

5. 5

   The hub speaks every platform

   One call becomes an aps payload, an FCM notification and a WNS toast. You wrote none of them.

   fan-out · APNs · FCM · WNS

6. 6

   Target by tag, not by device

   Devices register with tags. You send to “city:bengaluru AND tier:prime” and never touch a token.

   tag expression · city:bengaluru && tier:prime

7. 7

   Dead tokens clean themselves

   Uninstalled apps get rejected by APNs and FCM, and the hub removes those registrations for you.

   feedback · 18,400 expired registrations removed

8. 8

   A push is not a message queue

   No ordering, no retention, no receipt. If it must arrive, it belongs in your app, not in a banner.

   best-effort · fire and forget

9. 9

   Your loop vs the hub

   The same push, and the difference is how much delivery machinery you are on the hook for.

   maintain it · or configure it

10. 10

    Send once. Reach a million.

    Your code should describe the audience and the copy. Everything below that is the hub’s job.

    Azure Notification Hubs · msdevmart-push