# Saturated category risk — commodity or highly competitive app category

- **Pattern:** `ab-000461` (`app-store-policy-compliance.risk-indicators.saturated-category`)
- **Severity:** info
- **Lifecycle:** active
- **Last modified:** 2026-04-18
- **Canonical URL:** https://auditbuffet.com/patterns/ab-000461
- **License:** CC-BY-4.0 — attribute to AuditBuffet Pattern Catalog (https://auditbuffet.com/patterns/ab-000461)

## Why it matters

Apple guideline 4.2 applies heightened scrutiny to apps in saturated categories — to-do lists, flashlights, weather apps, meditation apps, Bible/scripture apps, and daily quote apps collectively have hundreds of thousands of existing submissions. An app entering one of these categories without a clear technical differentiator in the codebase faces a higher probability of minimum-functionality rejection on borderline signals that would otherwise be tolerated. This is informational because the category alone does not cause rejection — but it amplifies the impact of every other borderline finding in this audit.

## Severity rationale

Informational because saturated-category positioning is a risk multiplier, not a direct violation — it raises the bar for every other check in this audit rather than constituting a standalone rejection reason.

## Remediation

Identify and surface the specific technical differentiator in the app's first screen and store description. A differentiator must be verifiable in the codebase — a novel integration, an offline-first architecture, a unique workflow, or a community feature — not marketing copy.

Before submission, ensure every quality, content, and platform check in this audit passes cleanly with no borderline results. A saturated-category app that also has a thin WebView or missing accessibility labels will not survive review.

If no differentiator exists, build one before submitting: offline caching (`AsyncStorage`, SQLite), push notification workflows, or a community sharing layer are all implementable in `src/` without major architectural changes.

## Detection

- **ID:** `saturated-category`
- **Severity:** `info`
- **What to look for:** Count all relevant instances and enumerate each. Determine the app's primary category from `app.json` category metadata, Play Console category selection, or the app's core functionality. Assess whether the app is entering a category with extreme commoditization: to-do lists / task managers, note-taking apps, flashlight apps, calculator apps, weather apps, alarm clock apps, tip calculators, unit converters, QR code scanners, Bible/scripture apps, daily quote / affirmation apps, meditation / white noise apps. These categories have tens of thousands of existing apps. An app entering one of these categories without a clear differentiation story faces heightened scrutiny under Apple guideline 4.2 and 4.3. This is informational — it is not a rejection on its own, but combined with other borderline signals it significantly raises rejection risk. Note the category and the level of market saturation.
- **Pass criteria:** App is in a differentiated category, OR it is in a saturated category but has a clear, specific differentiator evident in the codebase (novel feature, integration, community layer, workflow innovation). At least 1 implementation must be verified. Result is `pass` or `skip` only — never `fail`.
- **Fail criteria:** Not applicable — this is an informational check. Result is `pass` or `skip` only.
- **Skip (N/A) when:** Cannot determine the app's primary category from the codebase; app's category is clearly differentiated with no saturation risk.
- **Detail on fail:** Not applicable — result is `pass` or `skip` only.
- **Remediation:** Being in a saturated category raises the bar for every other check in this audit. Ensure the app passes all quality, content, and platform checks without any borderline results. Consider adding a differentiating feature before submission.

  Review the configuration in `src/` or `app/` directory for implementation patterns.

## External references

- external apple-guideline-4.2-saturation — https://developer.apple.com/app-store/review/guidelines/#minimum-functionality

Taxons: regulatory-conformance

HTML version: https://auditbuffet.com/patterns/ab-000461