Expedited and user-initiated long jobs
Jobs that start soon or run long after a user action: Android expedited and UIDT, iOS 26 continued processing.
In one line
Can run jobs soon or for a long time after you tap something, with daily limits
Jobs that start soon or run long after a user action: Android expedited and UIDT, iOS 26 continued processing.
These are the sanctioned ways to finish work the person started (upload, export). They need a visible progress surface, so apps can no longer quietly continue large jobs.
What it can and can't do
What the user does: You tap Export, Upload or Process and the app keeps working after you leave
It can
- Start an expedited job that runs soon on Android
- Run a long task started by you (user initiated job) on Android 14 and newer
- Continue processing after you leave on iOS 26
- Show progress while the job runs
It cannot
- Run past the daily quota for expedited jobs on Android (30 minutes at best, 5 when restricted)
- Start a long job on iPhone without a foreground tap
- Skip showing progress on iPhone with iOS 26
- Use the GPU in the background without the Apple GPU entitlement
How it differs between platforms: Android has daily quotas for expedited work and long jobs need a network constraint. iPhone 26 continued processing starts only from a foreground action.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Android 12 (API 31) | iOS 26.0 |
| Permission or entitlement | RUN_USER_INITIATED_JOBS (API 34, normal) | BGTaskSchedulerPermittedIdentifiers with continued-processing prefix; GPU entitlement for GPU work |
| Protection level | normal | entitlement |
| How access is granted | install | entitlement |
| What the user sees | Notification with progress required for UIDT | Live Activity style progress UI |
| How long it lasts | Per job; stopped if the user stops it in the task manager | Tasks showing little progress are terminated first; starts in the foreground |
| How to take it back | Task manager 'Stop' | Swipe or user cancel |
| Store policy | None listed | None listed |
| API | WorkManager setExpedited, JobInfo.Builder.setUserInitiated(true) | BGContinuedProcessingTask, ProgressReporting |
| Notes | Expedited quota per 24 h: Active 30 min, Working 15, Frequent 10, Rare 10, Restricted 5; UIDT has no fixed quota but needs a network constraint and notification | Starts from a foreground user action; must report progress; separate GPU entitlement |
Data you get
What comes back: Job quota
Shape: object
How often: Per 24 h
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
expedited_active | integer | min | 30 | Not listed |
expedited_restricted | integer | min | 5 | Not listed |
Technical limits
- Both need visible progress
- iOS tasks are terminated first if progress is low
The story
What it is
Allowed ways to finish long jobs you started, like uploads or exports, with a visible progress notice.
For you
You start a big upload, a video export or a backup and then leave the app. You see a progress notice and can stop it. You are never in the dark about a long job.
For makers
Makers get a proper way to finish heavy work after you leave the app. In return they must show progress. This stops apps from quietly running large jobs in the background.
Where you see it
| Type | Example | Apps |
|---|---|---|
| creative | A video editor finishes exporting your clip after you switch apps. | CapCut, LumaFusion |
| productivity | A cloud app uploads a big folder and shows a progress bar in the notifications. | Google Drive, Dropbox |
| games | A game finishes downloading a large patch while you check messages. | None named |
| social | A social app uploads a long video post after you leave. | Instagram, TikTok |
| fitness | A fitness app syncs a long workout file after the run. | None named |
| ads | A hidden kit used to run big jobs quietly, which new rules forbid. | None named |
Risks
- Hidden long jobs
- Battery and data use
Android and iPhone in short
- Android: Android has expedited jobs for short urgent work and user initiated transfers for long ones.
- iPhone: iOS 26 adds continued processing for jobs you start in the app.
What the platform says
- Google: User initiated data transfers. Android lets apps run long transfers you start, with a notification you can see and stop.
- Apple: Continued processing tasks. iOS 26 lets an app keep working on a job you start, with progress shown on screen.
Good uses and abuse
Legitimate uses
- Large upload or export
Known abuse
- None
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 4 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
- 2021-10, Android 12 (API 31): Expedited jobs introduced
- 2023-10, Android 14 (API 34): User-initiated data transfer jobs introduced
- 2025-09, iPhone iOS 26: BGContinuedProcessingTask lets foreground started work continue with progress UI
Related capabilities
Related
- Deferrable background work (WorkManager, JobScheduler). Can run background jobs on Android, but not more often than every 15 minutes
- iOS app refresh and processing tasks. Can ask iPhone for short refreshes of about 30 seconds, but the system picks the time
Same idea on the web
- Background Fetch. Can download or upload big files after you leave the tab, with a progress notice
Sources
How well checked: Checked against real behavior.