Guideline 4.10
Guideline 4.10 - Design: Monetizing Built-In Device Capabilities
Our Take
Apple is rejecting your app because it charges users for functionality that is already built into the device. Guideline 4.10 prohibits monetizing standard device capabilities — if the iPhone already does something natively (flashlight, compass, level, magnifying glass, calculator, QR code scanning, screen recording, etc.), you cannot wrap that capability in an app and charge for it. This guideline exists because Apple considers it deceptive to charge users for features they already have for free on their device. It applies to both paid apps and in-app purchases. A flashlight app that costs $0.99, a QR code scanner with a subscription, or a compass app with premium features that just overlay the device's magnetometer data all violate this guideline. The rejection is straightforward and rarely subjective. If your app's primary value proposition is a capability the device already provides natively, monetization will be blocked. The fastest compliant path depends on your situation. If your app truly just wraps a built-in feature, you need to either make it free or add substantial unique functionality that goes well beyond the built-in capability. If your app adds genuine value on top of the built-in feature (advanced data logging, professional-grade measurements, integration with other systems), make that additional value the focus and ensure the basic capability itself is free.
Resolution Guide
**Make it free** — Remove the price tag or IAP for the core capability. You can still monetize through ads (non-intrusively) or by adding premium features that go genuinely beyond the native capability.
**Or pivot your value proposition** — Add features that the built-in tool doesn't have. For a flashlight app: SOS patterns, colored filters, strobe timing controls for photography, integration with emergency services. For a compass: hiking trail recording, GPS waypoints, topographic overlays.
### If your app has BOTH built-in and unique features:
**Separate the monetization** — Make the basic capability (flashlight, compass, scanner) completely free. Only charge for the advanced features that don't exist in the native tool.
**Restructure your paywall** — The paywall should clearly describe what the user gets that they can't get for free on their device. 'Unlock advanced compass' is bad; 'Unlock trail recording, offline maps, and waypoint sharing' is good.
**Update your App Store description** — Lead with the unique features, not the built-in capability. If your first screenshot shows a flashlight toggle, Apple sees a flashlight app.
Prevention
Example Rejection Email
Consider Appealing
Appeal if your app provides substantial functionality beyond the native capability that the reviewer may have missed. Detail the unique features, integrations, or professional-grade enhancements that differentiate your app. If the app genuinely only wraps a built-in feature, make it free or add real value.
Before & After
App called 'Super Flashlight Pro' costs $1.99, provides a flashlight toggle and brightness slider — the same thing as the Control Center flashlight
App renamed to 'Light Studio,' flashlight is free, premium ($1.99) unlocks: customizable SOS patterns, photography lighting presets with color temperature control, strobe timing for emergency signaling, and integration with the Health app for emergency contacts
What changed: The basic device capability must be free. Monetization is only acceptable for genuinely unique features that go well beyond what the device provides natively.
Community Solutions · 0
Sign in to share your solution.
More Guideline 4 (Design) rejections
- Guideline 4.0 - Design: App Does Not Include iOS Features
- Guideline 4.0 - Design: App Looks Like a Website
- Guideline 4.0 - Design: Apple Pay Button Not Following Guidelines
- Guideline 4.0 - Design: Blurry Icons or Low-Resolution Assets
- Guideline 4.0 - Design: Broken Layout on iPad
- Guideline 4.0 - Design: Content Clipped by Notch or Safe Area