Review notes explain non-obvious features or special setup
Why it matters
App Store and Play Store reviewers spend roughly five minutes evaluating each submission. Apps with Bluetooth, AR, NFC, background location, subscriptions, or unusual onboarding flows that ship without review notes frequently get rejected under Guideline 2.1 (App Completeness) because the reviewer cannot reach the core feature in the time they allocate. Generic notes like "Hope you enjoy our app" do not count — they provide zero navigational guidance and still trigger rejection.
Severity rationale
Medium because missing or empty notes materially raise rejection risk for non-trivial apps but rarely affect simple single-purpose apps.
Remediation
Write review notes from the perspective of a reviewer who has never opened the app. Keep the notes between 150-400 words, cover login, required hardware, how to reach subscription test flows, and any onboarding gates. Commit them to REVIEW_NOTES.md at the repo root and paste the same text into App Store Connect's "Notes for Reviewer" field at submission time.
This app requires a Bluetooth Low Energy scale for the weigh-in feature.
Demo account credentials are above. To test without hardware, tap "Skip scan"
on the pairing screen to enter a demo reading. Subscription IAP uses sandbox.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the App Store Metadata & Listing Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from app-store-metadata-listing·automated