Skip to Content
Platform.Ontology

App Standby Buckets

Android sorts apps into five buckets that cap job time, alarms and network by how recently they were used.

Works without askingNotifications and backgroundAndroid background limitsAndroid and iPhoneIn the background

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

AndroidiPhone
StatusSupportedNot supported
First versionAndroid 9.0 (API 28)Not available
Permission or entitlementNot listedNot listed
Protection levelnonenone
How access is grantednonenot-exposed
What the user seesNone; set by the system from usageNot listed
How long it lastsMoves hourly based on useNot listed
How to take it backSettings > Apps; adb shell am get-standby-bucketNot listed
Store policyNone listedNone listed
APIUsageStatsManager.getAppStandbyBucket()Not listed
NotesJob 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 RestrictediOS 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

FieldTypeUnitRangePrecision
bucketenumNoneActive, Working set, Frequent, Rare, Restricted, NeverNot listed
expedited_quotaintegermin per 24 hActive 30, Working 15, Frequent 10, Rare 10, Restricted 5Not 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

TypeExampleApps
mediaA news app has fresh stories ready for daily readers but needs a moment to catch up for people who rarely open it.NYT
shoppingA store sends fewer background price refreshes to users in the rare bucket.Amazon
gamesA game you stopped playing weeks ago stops its timed energy refills in the background.None named
messagingA chat app must use high priority push to reach someone in a quiet bucket.WhatsApp
analyticsA retention team notices background sync slows for dormant users and adjusts its win back campaign.None named
adsAn 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

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-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

Same idea on the web

Sources

How well checked: Checked against real behavior.

On this page