Skip to Content
Platform.Ontology

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.

Works without askingNotifications and backgroundPushAndroid and iPhoneIn the backgroundAfter you uninstall

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

AndroidiPhone
StatusPartialSupported
First versionAndroid 6.0 (API 8)iOS 7.0
Permission or entitlementNone; data-only FCM messageremote-notification UIBackgroundModes; aps content-available:1; apns-push-type background; apns-priority 5
Protection levelnoneentitlement
How access is grantedinstallentitlement
What the user seesNoneNone
How long it lastsData messages reach the app unless it is in the stopped state; high priority data messages are quota limitedDelivery not guaranteed; newest held notification replaces older; discarded after force quit
How to take it backForce stop blocks deliveryBackground App Refresh off; Low Power Mode; Force quit
Store policyPlay policy: no stealth background work that harms batteryApp Review 2.5.4 on background modes
APIonMessageReceived() for data messages; short execution window then hand off to expedited WorkManagerapplication(_:didReceiveRemoteNotification:fetchCompletionHandler:), about 30 s of run time
NotesAndroid treats this as an ordinary data message; no separate throttle number published; high priority ones can be deprioritizedApple: 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

FieldTypeUnitRangePrecision
rate_guidancefloatper hour2 to 3Apple guidance
run_timeintegersecondsabout 30approx

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

TypeExampleApps
messagingA chat app wakes up in the background to decrypt and pre-load new messages.Signal
newsA news app downloads the latest stories as you sleep.Apple News
mediaA podcast app pulls a new episode in the background.None named
analyticsA marketing team sends a silent push to each device to count how many installs are still alive.None named
adsAn ad platform checks that an install is live before it counts it in a campaign.None named
gamesA game refreshes its daily rewards shop quietly before you open it.None named
securityA 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

Good uses and abuse

Legitimate uses

  • Sync
  • Prefetch

Known abuse

  • Pinging installs to confirm they are alive

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction1 of 5How much the user has to do
Fingerprint bitsNot ratedRough 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

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.

On this page