Skip to Content
Platform.Ontology

Deferrable background work (WorkManager, JobScheduler)

The standard way to run background tasks; periodic work cannot repeat faster than every 15 minutes.

Works without askingNotifications and backgroundAndroid background limitsAndroid and iPhoneIn the background

In one line

Can run background jobs on Android, but not more often than every 15 minutes

The standard way to run background tasks; periodic work cannot repeat faster than every 15 minutes.

Defines how often a background sync can run for an idle install. The 15 minute minimum and bucket quotas make exact timing impossible, so apps lean on push for freshness.

What it can and can't do

What the user does: Nothing. It happens when the app sets up a sync, upload or cleanup job

It can

  • Run a job on a schedule, such as every 15 minutes or longer
  • Wait for good conditions, like Wi-Fi or charging
  • Retry later if a job fails

It cannot

  • Repeat faster than every 15 minutes
  • Run at an exact second; the system picks a good time
  • Use up the quota for its group; jobs get fewer minutes when the app is rarely opened
  • Count on a guaranteed time on iPhone, which has no fixed interval

How it differs between platforms: Android has a standard job system with a 15 minute minimum. iPhone has no guaranteed interval.

On Android and iPhone

AndroidiPhone
StatusSupportedPartial
First versionAndroid 5.0 (API 21)iOS 7.0
Permission or entitlementRECEIVE_BOOT_COMPLETED (optional, for reschedule), WAKE_LOCK (normal)BGTaskSchedulerPermittedIdentifiers (Info.plist)
Protection levelnormalnone
How access is grantedinstallnone
What the user seesNoneNone
How long it lastsPersisted across reboots by WorkManager; constraints decide startSystem decides when; earliestBeginDate is only a lower bound
How to take it backForce stop clears jobsForce quit stops tasks
Store policyNone listedNone listed
APIWorkManager.enqueueUniquePeriodicWork, JobScheduler.scheduleBGTaskScheduler.submit(BGAppRefreshTaskRequest or BGProcessingTaskRequest)
NotesPeriodic minimum interval 15 min (flex window 5 min); regular job quotas by bucket; Android 16 adds top state and FGS quota enforcementiOS has no guaranteed interval; see mob.bg.ios-refresh-processing

Data you get

What comes back: Periodic interval
Shape: integer
How often: Scheduled

FieldTypeUnitRangePrecision
min_intervalintegerminutes15Not listed
flexintegerminutes5 minimumNot listed

Technical limits

  • Cannot run more often than every 15 minutes
  • Subject to standby bucket quotas

The story

What it is

The standard way for Android apps to run tasks later in the background, no faster than every 15 minutes.

For you

You never see it. Photos back up, drafts send and data syncs when your phone has network or charge. It might finish late, but it should finish.

For makers

Makers use it for uploads, sync and cleanup that must not be lost. Since the timing is loose, they use push messages when freshness matters.

Where you see it

TypeExampleApps
mediaA photo app uploads new pictures when you are on Wi-Fi and plugged in.Google Photos, iCloud for Android
messagingA chat app retries a message that failed to send when the signal returns.Telegram
productivityA notes app saves your offline edits to the server when you reconnect.Evernote
fitnessA fitness app uploads your workout file after you finish and go online.Fitbit
adsAn ad or analytics SDK batches events and sends them in scheduled jobs.None named
gamesA game downloads new level files in the background overnight.Roblox

Risks

  • Can be used to poll for signals
  • Timing is not exact

Android and iPhone in short

  • Android: Periodic work cannot repeat faster than 15 minutes. Quotas depend on the standby group.
  • iPhone: iOS has no guaranteed interval. Apps use app refresh and processing tasks.

What the platform says

  • Google: WorkManager. Google pitches WorkManager as the recommended solution for reliable background work that must run even if the app exits.

Good uses and abuse

Legitimate uses

  • Sync
  • Uploads

Known abuse

  • Background polling harvesting signals

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2018-10, Android WorkManager 1.0: WorkManager stable release
  • 2024-10, Android 15 (API 35): Task timeouts for dataSync and mediaProcessing (see FGS timeouts)
  • 2025-06, Android 16 (API 36): Quotas also depend on top state and foreground service; STOP_REASON_TIMEOUT_ABANDONED added

Same idea on the web

  • Periodic Background Sync. Can refresh an installed web app now and then while closed, at times the browser picks
  • 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