App Standby Buckets
Android sorts apps into five buckets that cap job time, alarms and network by how recently they were used.
In one line
Can't run as much in the background if you rarely open the app
Android sorts apps into five buckets that cap job time, alarms and network by how recently they were used.
Rarely opened apps get tiny background budgets, so a retention team sees its sync silently slow down for dormant users. Active apps in the top bucket have almost none.
What it can and can't do
What the user does: Nothing. Android sorts apps into groups by how recently you opened them
It can
- Run about 10 minutes per 4 hours if you use it often
- Run jobs and alarms more freely when it sits in the Working group
- Move back to a better group after you use the app again
It cannot
- Pick its own group; Android sets that from your use
- Run more than about 10 minutes per 24 hours when the app is rarely used
- Run only once a day when it is in the Restricted group
- Face this on iPhone, which has no groups like this
How it differs between platforms: Android has five usage groups that cap jobs, alarms and network. iPhone has no per app group.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Not supported |
| First version | Android 9.0 (API 28) | Not available |
| Permission or entitlement | Not listed | Not listed |
| Protection level | none | none |
| How access is granted | none | not-exposed |
| What the user sees | None; set by the system from usage | Not listed |
| How long it lasts | Moves hourly based on use | Not listed |
| How to take it back | Settings > Apps; adb shell am get-standby-bucket | Not listed |
| Store policy | None listed | None listed |
| API | UsageStatsManager.getAppStandbyBucket() | Not listed |
| Notes | Job runtime: Working 10 min per 4 h; Frequent 10 min per 12 h; Rare 10 min per 24 h; Restricted once per day. Alarms: Working 10 per hour, Frequent 2, Rare 1, Restricted 1 per day. Network off for Rare and Restricted | iOS has no per-app bucket; see Background App Refresh and Low Power Mode |
Data you get
What comes back: Bucket
Shape: enum
How often: Hourly
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
bucket | enum | None | Active, Working set, Frequent, Rare, Restricted, Never | Not listed |
expedited_quota | integer | min per 24 h | Active 30, Working 15, Frequent 10, Rare 10, Restricted 5 | Not listed |
Technical limits
- Charging lifts limits except Restricted
- Active has quota only from Android 16
The story
What it is
Android sorts apps into groups by how often you use them and limits background work for the rarely used ones.
For you
You never see the groups. But an app you have not opened in weeks will be slower to sync and alert you, while apps you use daily keep working normally.
For makers
Makers see their reach shrink for dormant users, since background jobs, alarms and network all get cut. They lean on push messages and design the app to catch up the moment it opens.
Where you see it
| Type | Example | Apps |
|---|---|---|
| media | A news app has fresh stories ready for daily readers but needs a moment to catch up for people who rarely open it. | NYT |
| shopping | A store sends fewer background price refreshes to users in the rare bucket. | Amazon |
| games | A game you stopped playing weeks ago stops its timed energy refills in the background. | None named |
| messaging | A chat app must use high priority push to reach someone in a quiet bucket. | |
| analytics | A retention team notices background sync slows for dormant users and adjusts its win back campaign. | None named |
| ads | An ad SDK can upload events less often for apps in low buckets. | None named |
Risks
- Late alerts for rarely used apps
- Dormant users are harder to reach
Android and iPhone in short
- Android: Android only. Five buckets with strict job, alarm and network limits.
- iPhone: iOS has no buckets. It relies on Background App Refresh and Low Power Mode.
What the platform says
- Google: App Standby Buckets. Google describes buckets as a way to prioritize resources for apps people use most and limit those they do not.
Good uses and abuse
Legitimate uses
- Battery management
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 | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2018-08, Android 9 (API 28): App Standby Buckets introduced
- 2021-10, Android 12 (API 31): Restricted bucket assigned automatically after 45 days idle
- 2025-06, Android 16 (API 36): Job quotas enforced for Active bucket (20 min per 60 min) and based on top state and FGS
Related capabilities
Related
- Restricted bucket and battery restriction settings. Can only run in the background as much as your battery setting allows
- Deferrable background work (WorkManager, JobScheduler). Can run background jobs on Android, but not more often than every 15 minutes
Same idea on the web
- Push, periodic sync and background fetch. Can wake a site's background script after you leave, through push, timed sync or downloads
Sources
How well checked: Checked against real behavior.