Review notes explain non-obvious features or special setup

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.

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.

• ID: app-store-metadata-listing.review-submission.review-notes-quality
• Severity: medium
• What to look for: Check for review notes in: REVIEW_NOTES.md, review-notes.txt, submission-notes.md, fastlane/Deliverfile (notes field or review_information hash), eas.json (review configuration). Evaluate the quality and completeness of review notes: (a) for apps with non-obvious flows, check if notes explain how to reach and test the core functionality, (b) for apps with hardware dependencies (Bluetooth, AR, NFC), check if notes acknowledge that certain features require specific hardware and offer an alternative demonstration path, (c) for apps with server-dependent features, check if notes confirm the backend is live and accessible, (d) for apps with subscription or IAP, check if notes explain how to test purchases (sandbox accounts for App Store, test purchases for Google Play), (e) absence of any notes at all is not automatically a failure — simple, obvious apps may not need them. Judge based on whether a reviewer encountering the app cold could navigate and evaluate it without additional context. Count all instances found and enumerate each.
• Pass criteria: Review notes exist and address the non-obvious aspects of the app; they are accurate and useful (not just "Please approve my app"); or the app is simple enough that notes are unnecessary. At least 1 implementation must be confirmed.
• Fail criteria: Complex app with Bluetooth, hardware, subscription, or unusual flows has no review notes at all; review notes exist but contain only generic text ("Hope you enjoy our app!") with no actionable guidance.
• Skip (N/A) when: App is simple enough (single-purpose, no auth, no hardware, no subscription) that review notes provide no additional value.
• Detail on fail: "App uses Bluetooth (react-native-ble-plx detected) but no review notes explain how to test Bluetooth features without specific hardware".
• Remediation: Well-written review notes reduce the chance of rejection for misunderstood functionality and speed up the review process.
  1. Write review notes from the perspective of a reviewer who has never used your app
  2. Address these questions if relevant: How do I log in? What hardware do I need? How do I test purchases? Are there any features only accessible after completing a setup flow?
  3. Keep notes concise — 150-400 words is ideal. Reviewers won't read an essay.
  4. In App Store Connect: review notes go in "Notes for Reviewer" in the submission form
  5. Example structure:

     This app requires a Bluetooth Low Energy device for core functionality.
     A demo account is provided above. The app will prompt for Bluetooth permission
     on first launch — allow it to see the device scanning feature.