What Apple and Google are doing to your push notifications
Apple and Google have significantly changed how push notifications are managed on their platforms. Over the years, both companies have implemented various levels of control over notifications, shifting the balance of power from senders to users. This evolution has led to a decline in opt-in rates for notifications, impacting how brands communicate with their customers.
- ▪Apple and Google control the primary channels for push notifications, with all notifications passing through their servers.
- ▪The introduction of notification channels on Android and similar features on iOS has given users more control over what notifications they receive.
- ▪Recent changes have resulted in a notable decline in opt-in rates for push notifications, particularly among gaming and news apps.
Hacker News (Front Page) files mainly under programming. We currently carry 1,005 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Jacquescorbytuech |
| Canonical URL | https://www.jacquescorbytuech.com/writing/what-apple-and-google-are-doing-your-push-notifications |
| Publication time | Wed, 27 May 2026 19:24:10 +0000 |
| Retrieval time | 2026-05-27T19:38:03.746Z |
| Last seen | 2026-05-27T19:38:03.746Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 7GZbpPHsUyLN · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
27 May 2026 What Apple and Google are doing to your push notifications Contents Push as a battery problem Fifteen years of platform intervention What email did first The on-device editor What users actually do with notifications What the marketer can see Writing for the model in the pipe Shifting weight to owned surfaces What this becomes What to do about it 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.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Jacquescorbytuech.
Discussion
0 commentsMore from Jacquescorbytuech
