Silent (background) push
A push with no alert that wakes the app in the background; Apple asks for 2 or 3 per hour at most.
In one line
Can wake the app quietly with a push, but only a few times an hour
A push with no alert that wakes the app in the background; Apple asks for 2 or 3 per hour at most.
Lets a server trigger a data refresh without the person seeing anything, and also reveals whether the install is still alive. Apple throttles it, so it is a nudge, not a reliable timer.
What it can and can't do
What the user does: Nothing. The app's server sends it, and you see nothing on screen
It can
- Wake the app to fetch fresh data before you open it
- Refresh content in the background without an alert
- Work on iPhone only if you did not force quit the app
It cannot
- Wake it more than about 2 or 3 times an hour; Apple slows down apps that send too many
- Wake it after a force quit or when Background App Refresh is off
- Carry a long message; it only holds a small amount of data
- Act as a separate type on Android, where it is just a normal data message
How it differs between platforms: iPhone treats silent pushes as a special type with throttling. Android treats them as ordinary data messages.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Partial | Supported |
| First version | Android 6.0 (API 8) | iOS 7.0 |
| Permission or entitlement | None; data-only FCM message | remote-notification UIBackgroundModes; aps content-available:1; apns-push-type background; apns-priority 5 |
| Protection level | none | entitlement |
| How access is granted | install | entitlement |
| What the user sees | None | None |
| How long it lasts | Data messages reach the app unless it is in the stopped state; high priority data messages are quota limited | Delivery not guaranteed; newest held notification replaces older; discarded after force quit |
| How to take it back | Force stop blocks delivery | Background App Refresh off; Low Power Mode; Force quit |
| Store policy | Play policy: no stealth background work that harms battery | App Review 2.5.4 on background modes |
| API | onMessageReceived() for data messages; short execution window then hand off to expedited WorkManager | application(_:didReceiveRemoteNotification:fetchCompletionHandler:), about 30 s of run time |
| Notes | Android treats this as an ordinary data message; no separate throttle number published; high priority ones can be deprioritized | Apple: do not send more than 2 or 3 per hour; excessive use is throttled; aps may contain only content-available |
Data you get
What comes back: Background wake by push
Shape: event
How often: Server driven, throttled
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
rate_guidance | float | per hour | 2 to 3 | Apple guidance |
run_time | integer | seconds | about 30 | approx |
Technical limits
- Not delivered after force quit
- Needs Background App Refresh enabled
- Throttled by the system
- System throttles delivery
The story
What it is
A push message with no alert that quietly wakes an app to refresh data.
For you
You never see it. The app just has fresh content when you open it. It also means a company can tell an app is still installed and alive, without you doing anything.
For makers
Makers use it to sync data and prefetch. Some also use it to check if an install is still there, which feeds measurement and cleanup of dead users. Apple throttles it, so it is a nudge, not a timer.
Where you see it
| Type | Example | Apps |
|---|---|---|
| messaging | A chat app wakes up in the background to decrypt and pre-load new messages. | Signal |
| news | A news app downloads the latest stories as you sleep. | Apple News |
| media | A podcast app pulls a new episode in the background. | None named |
| analytics | A marketing team sends a silent push to each device to count how many installs are still alive. | None named |
| ads | An ad platform checks that an install is live before it counts it in a campaign. | None named |
| games | A game refreshes its daily rewards shop quietly before you open it. | None named |
| security | A bank app quietly refreshes a fraud rule list without bothering you. | None named |
Risks
- Reveals the app is still installed
- Can drain battery if overused
Android and iPhone in short
- Android: Android treats this as an ordinary data message with no separate published limit.
- iPhone: Apple asks for no more than 2 or 3 per hour and throttles abuse. Force quitting the app blocks it.
What the platform says
- Apple: Pushing background updates. Apple documents background pushes as a way to wake the app and fetch content without showing anything to the person.
Good uses and abuse
Legitimate uses
- Sync
- Prefetch
Known abuse
- Pinging installs to confirm they are alive
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 1 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2013-09, iPhone iOS 7: Silent remote notifications (content-available) and background fetch introduced
- 2013-09, iPhone iOS 7: Silent remote notifications introduced
- 2017-08, Android 8.0 (API 26): Background execution limits
- 2019-09, iPhone iOS 13: apns-push-type header introduced; background pushes must use type background and priority 5
Related capabilities
Related
- Uninstall detection through push failures. Can find out the app was removed, but only after hours or days
- iOS app refresh and processing tasks. Can ask iPhone for short refreshes of about 30 seconds, but the system picks the time
- Notifications. Can show alerts, banners and badges, but only after you allow it
Same idea on the web
- Push API (Web Push). Can send you notifications after you leave, once you allow them
- Background Sync. Can retry sending queued data after you close the tab, once you are back online
Sources
How well checked: Checked against real behavior.