App Review notes examples that save back-and-forth.
Review notes are your private letter to App Review. Clear steps, working credentials, and honest constraints prevent Resolutions Center loops. Use these examples as a starting point, then attach them when you submit from Helm.
What good review notes include
Assume the reviewer has never seen your app. Give an account, a password, and the shortest path to the feature under review. Call out anything that looks empty without setup.
Do not hide geo blocks, paid walls, or hardware requirements. Say what will not work in their environment and how to verify the rest.
- Demo account that stays valid through review
- Exact taps to reach the new feature
- IAP products to buy and how to restore
- Regions, entitlements, or devices that are required
Demo account notes
Thank you for reviewing [App Name] [version].
Demo account
Username: review@example.com
Password: [strong temporary password]
This account has sample projects preloaded. After sign-in, tap Library → Sample Project to see the main flow. Please do not change the password. Contact [email] if the account locks.
In-app purchase testing notes
Thank you for reviewing [App Name] [version].
Sign in with review@example.com / [password]. Open Settings → Subscription to see available plans. Please sandbox-purchase “[Product ID / display name]” (monthly). After purchase, the Pro badge appears on the home screen. Restore Purchases is on the same screen. No backend approval is required for sandbox buys.
Geo-restricted features
Thank you for reviewing [App Name] [version].
Maps transit directions are available only when the device region is set to [Country]. To verify: set Region to [Country] (or use the in-app “Review: force [Country]” switch under Settings → Debug, enabled on this build). All other features work worldwide. If transit tiles show “Unavailable in your region,” the restriction is expected.
Login-required app
Thank you for reviewing [App Name] [version].
The app requires an account. Use review@example.com / [password]. There is no guest mode by design (account-based sync). After login, grant Photos permission when prompted to exercise import. Push notifications are optional for review. Sign-out is under Settings → Account.
Hardware or permission-heavy app
Thank you for reviewing [App Name] [version].
Bluetooth accessories are optional. Core editing works without hardware. To test accessory mode, pair any standard BLE heart-rate monitor, or tap “Use simulator sensor” on the Connect screen (review builds only). Camera and Motion permissions are requested only when those features are opened.
Attach notes when you submit in Helm
Add review information as part of your release flow and confirm it on the launch checklist before submit. Keep the demo account alive until the version is approved.
Related reading: submit an app for review, launch checklist, and What’s New examples for the public-facing side of the same release.
FAQ
Are App Review notes visible to customers?
No. Review notes are for App Review only. Customers see What’s New, promotional text, and your listing, not these credentials.
What if my demo account expires mid-review?
Keep it valid through approval. If it expires, reply in Resolution Center with fresh credentials quickly so the review can continue.
Should I put review notes in What’s New?
No. What’s New is customer-facing. Credentials and reviewer steps belong in App Review information only.
