AppReviewFix
Guideline library
Apple App Store — App Quality

2.4.2 — Power efficiency

Official source: App Store Review GuidelinesTopic overview: The review process, app quality and enforcement
What this guideline means

Apple's review process checks for apps that consume excessive CPU, GPU, or network resources relative to their apparent functionality — background processes or polling loops that keep the device awake unnecessarily fall under this.

Why apps actually get flagged

Frequently caused by a background location or network polling interval set far more aggressively than the feature actually needs.

A real example

"Your app consumes an excessive amount of energy, even when running in the background, per guideline 2.4.2. Please optimize your app's power usage."

The short version, in more detail

Guideline 2.4.2 addresses apps that use too much power for what they do. Excessive CPU, GPU or network use, and background processes that keep the device awake needlessly, can be flagged during review. Battery impact is a user-experience matter, but it is also checked because it reveals misuse of system resources.

Why this rule exists

Battery life is one of the most visible parts of the iPhone experience, and users tend to blame the device or the operating system when an app quietly drains it. Because one poorly behaved app can damage that perception for everything else, Apple asks that apps use CPU, GPU, network and sensors in proportion to what they actually do. The guideline also protects the broader platform by discouraging patterns, such as constant polling, that waste shared resources.

What this guideline covers

  • CPU, GPU and network usage relative to app function.
  • Background processes and polling.
  • Keeping the device awake unnecessarily.
  • Location and sensor use at intervals that exceed need.

What usually triggers this rejection

  • Background location updates more frequent than the feature needs.
  • Aggressive network polling.
  • Animations or processing that run constantly.
  • Preventing the device from sleeping without reason.
  • Cryptocurrency mining or similar heavy work.

How reviewers evaluate it

  • Reviewers watch device behaviour such as heat and battery drain.
  • They compare resource use with the app's apparent purpose.
  • Instruments and diagnostics may be used in some cases.
  • Persistent overuse is more likely to be flagged than short spikes.

Common misunderstandings

  • Efficiency is not just a nice-to-have. It can lead to rejection.
  • Foreground use is judged differently from background use.
  • A well-reviewed app can still be flagged after an update that changes behaviour.

Common questions

Is there a battery limit?

No fixed number. Reviewers judge whether usage is reasonable for the app.

Can background activity be allowed?

Yes, for legitimate purposes in the allowed background modes.

Does mining count?

Heavy background work such as mining is treated as a violation.

Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.

Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.
Decode my rejection
Related guidelines
Functionality — Functionality, content and user experienceTarget API Level — Target API level requirements2.1 — App Completeness2.2 — Beta testing2.3.1 — Hidden or undocumented features
AppReviewFix
ProductDecoderPricingGuideline library
CompanyAboutFAQContact
ResourcesGuidesTopic overviewsCommon rejection reasons
LegalTermsPrivacy
© 2026 AppReviewFixBuilt by a developer, not a committee.