What Apple and Google are doing to your push notifications

I wrote recently about what Google, Yahoo, Microsoft, and Apple are doing to your email: how four providers stopped being transport layers and turned into active intermediaries between brands and their customers, parsing, ranking, summarising, and increasingly answering on the recipient's behalf. The same thing is happening to push, with two companies in control instead of four. Apple and Google run the only two pipes that matter, and every notification you have ever sent has passed through one of them. Over the last five years the on-device model that now sits between delivery and your lock screen began summarising, reordering and, on some surfaces, rewriting it. Notification summaries on Android. Push as a battery problem Push begins as a battery problem. In June 2009 Scott Forstall stood at WWDC and made the case that an iPhone could not afford to let every installed application maintain its own background poll against a remote server. The proposal, delayed from its initial September 2008 announcement after Apple decided to restructure the underlying infrastructure for scale, was the Apple Push Notification Service, a single persistent TLS connection from each device to Apple, over which any registered third party could deliver alerts.1 APNs shipped with iPhone OS 3 on 17 June 2009. Google followed in 2010 with Cloud to Device Messaging, then Google Cloud Messaging in 2012, then Firebase Cloud Messaging in 2016.2 The channel was intermediated from the start. Every notification you send to an iPhone passes through Apple's servers; every one to an Android phone passes through Google's. The platforms have always been able to throttle, drop, log, deprioritise or refuse. For most of the channel's history they did very little of it visibly. The architecture was permissive of intervention; they simply chose not to intervene much. That restraint is what ended. Fifteen years of platform intervention The early consumer push era between 2009 and 2017 was comparatively quiet. APNs and the various Google services delivered to whichever apps the user had installed, with limited platform-level filtering and minimal user controls beyond a single per-app on or off toggle. Android's first significant on-device intervention was notification channels in Android 8 Oreo, August 2017.3 Before Android 8, individual notifications carried a priority level decided by the sender.

After Android 8, that lever passed to the developer at the channel level and then to the user at the channel level. The developer declared a small number of channels per app (downloads, messages, promotions, and so on), each with an importance value from IMPORTANCE_NONE to IMPORTANCE_HIGH; the user could then independently mute, demote, badge-disable or fully block any channel without affecting the others.3 Once a channel's importance was set by the developer it could not be raised later. Any app targeting Android 8 had to declare channels or notifications would simply not display. Apple introduced its own version in iOS 15 in September 2021 under different language. Focus, Scheduled Summary, and a new four-level interruption taxonomy (passive, active, time-sensitive, critical) restructured how iOS treated each push.4 Time-sensitive was the only level you could meaningfully address, and Apple was explicit, then and now, that you should not use it for marketing.4 Android made permission itself the lever in August 2022, when Android 13 turned POST_NOTIFICATIONS into a runtime permission, requiring an explicit user grant rather than the implicit opt-in that had applied since the platform's launch. Opt-in rates fell predictably: Pushwoosh's 16 million device sample showed gaming apps losing nearly a third of their opted-in base and news apps dropping 19 percent.5 Batch's 2025 benchmark, drawn from more than 800 billion messages across 10,000 apps, reported Android opt-in falling from 85 percent to 67 percent in a year and the cross-platform average settling at 61 percent.6 Every step subtracts a degree of sender control. Some of it passes to the user, and that is a good thing: a person deciding what is allowed to interrupt them is the channel working as it should. The rest passes to the platform, and that is the part that should concern a sender, because the platform's judgment is opaque, unappealable, and increasingly made by a model rather than by a setting the user chose. Over fifteen years the channel has been rebuilt around one assumption: the receiver's attention is a scarce resource the platform is obliged to defend. It defends that resource for its own reasons as much as the user's.

A clean, low-fatigue notification surface protects the platform's retention and ecosystem, reduces uninstalls, and shows off its AI, so the editing is the platform guarding an asset it owns, not pure user advocacy. As a sender you are on the wrong side of that assumption, whichever way the control moved. What email did first Email is further along, and I've told that story in full. The same intermediation has been building on push in parallel, a step behind, which makes email a reliable preview of where push is going. Push is the harder case, though: email at least gives senders some instrumentation to see it working, Postmaster Tools and deliverability dashboards, where push gives them almost none. There is no push equivalent of the inbox, either: an email persists in a place the recipient can scroll back through, search and return to, while a notification lives only in the notification centre, which clears, drops and summarises what passes through it and retains nothing reliably. Machine learning has decided inbox placement since the late 1990s, when Bayesian spam filtering moved providers off rule-based filters and onto classifiers weighing content, sender reputation and recipient engagement; authentication standards (SPF, DKIM, DMARC) layered on later as signals feeding those models rather than replacements for them. Marketers slowly learned to treat email less as a publishing act than as a request a hidden classifier grants or denies. Gmail's tabbed inbox in 2013 sorted legitimate mail into Primary, Promotions, Social and Updates with the same kind of classifier. The Promotions tab was not the spam folder but a separate category for commercial mail the user had agreed to receive yet the model judged promotional; Apple Mail added its own categorisation in 2024. Each move pushed the line between the sender's intent and the user's experience another step away from the sender. Mail Privacy Protection, shipping in iOS 15 in September 2021, was the visibility blow. Apple Mail began prefetching remote content through Apple-controlled proxies whether or not the user opened the message, masking the IP address and breaking the open-pixel mechanism marketers had relied on for a decade.

One vendor, Omeda, watched Apple-driven open rates climb from 22.6 to 40.5 percent in six months purely from those prefetches rather than from readers.7 The open rate in its old form became unrecoverable, and click-through and downstream conversion took over as the engagement signal. Then Yahoo and Google made deliverability itself the gate. From early 2024, any sender pushing real volume to personal inboxes has had to authenticate with SPF and DKIM, align DMARC, offer one-click unsubscribe and keep spam complaints under a low ceiling, or not reach the inbox at all; Google moved from deferrals to outright rejection in November 2025, and Microsoft published equivalent rules.8 Apple Intelligence summarisation reached Mail in October 2024, and Gmail's Gemini summaries followed. Push has now arrived at roughly the same intermediation maturity email reached a decade earlier, with a few differences in the mechanism that cut against you. Email runs on open, federated protocols (SMTP, IMAP, and the DKIM and DMARC standards) that anyone can implement; the reading client is decoupled from the provider, so a recipient can open the same mailbox in any app; and a subscription is just an address on a list that you, the sender, hold. Push has none of that. A user's permission lives inside a specific install on a specific device, a native app or, since iOS 16.4, a home-screen web app, tied to a token (APNs or FCM) that Apple or Google can invalidate at will, and you hold no list you can take elsewhere. Web push widens who can send, with no App Store download required, but the notification still lands in the same tray under the same on-device editing, so it broadens the channel without escaping the editor. Email has DKIM signatures a receiving mailbox can check; push has no analogue, because every notification is already signed by Apple or Google's infrastructure as a condition of being delivered at all. Email gives you layout control via HTML; push gives you a small structured payload and little control over the collapsed lock-screen view beyond the platform's templates.

You can supply a richer custom layout for the expanded view, a content extension on iOS, custom layouts on Android, but it renders only once the user pulls the notification open, and the collapsed text the summariser works on stays template-bound. Email lives in a queue the user opens deliberately; push interrupts. In email, the death of the open rate should have taught marketers what an open always was: a proxy for delivery at best, never for engagement. Plenty never learned, and still read opens as engagement today.