Guide · Notes for Review
Notes for Review for apps with feature flags
If a remote switch can change what users see or do, App Review should read about it in your notes. Here is what to include for each kind of flag, with a template you can copy.
By Claudiu Micu · Updated
Where the notes go
In App Store Connect, open the app version and scroll to App Review Information. The Notes field is there, next to the sign-in fields for a demo account. Apple’s help page sets the limit:
“The Notes field can contain up to 4000 bytes. You can write notes in any language.”
It’s 4000 bytes, not characters: accented letters take 2 bytes in UTF-8 and most emoji take 4.
What Apple asks for
“All new features, functionality, and product changes must be described with specificity in the Notes for Review section of App Store Connect (generic descriptions will be rejected) and accessible for review.”
“Include detailed explanations of non-obvious features and in-app purchases in the App Review notes, including supporting documentation where appropriate.”
Sort your flags first
Not every flag needs the same sentence. These are the groups ReviewNotes sorts flags into, and what a reviewer needs to know about each:
- Feature: what it does, its state during review, and how to reach it.
- Staged rollout: whether the review account is in the rollout, and what it sees if it isn’t.
- Paywall or A/B test: which variants exist, and that every in-app purchase appears in each.
- Region gate: which countries or regions see the feature, and how the reviewer can see it.
- Kill switch: which feature it can turn off, and that the feature is on during review.
- Dormant feature: code in the build that isn’t live yet. Say it’s there and when it will be switched on, or remove it.
- Debug or test switch: confirm it’s off and unreachable. If one is on, fix that before you submit.
- Remove before upload: code that detects App Review, fakes a demo state or loads code over the air. Don’t describe it; take it out of the build.
- Config value: copy, colours, limits. Usually listed by name only.
Rollouts and experiments
A reviewer is one more user to your flag service. If a feature is in a 10% rollout, the review account might not get it. Either pin the review account to the variant you want reviewed (most flag services can target one user or account directly) or say in the notes which variant the reviewer will see and that the others are complete.
For paywall tests, 2.1(b) matters:
“If any configured in-app purchase items cannot be found or reviewed in your app, explain the reason in your review notes.”
A template
NOTES FOR APP REVIEW: [APP] [VERSION] This build uses remote configuration. Every remotely controlled feature is listed with its state during review and how to reach it. DEMO ACCOUNT Username: [demo user] Password: [demo password] REMOTELY CONFIGURED FEATURES [Feature name] (flag: [flag_key]) What it does: [one specific sentence] During review: ON for the review account How to reach it: [Tab] → [Screen] → [Button] STAGED ROLLOUTS AND EXPERIMENTS [flag_key]: [n] variants; every in-app purchase is shown in each variant. DEVELOPER AND INTERNAL SWITCHES (ALL OFF) [debug_flag], [staging_flag]: OFF in this build and not reachable by users. CONTACT [name, email]
Replace every [bracket]. Generic lines like “bug fixes and improvements” are what 2.3.1(a) calls out, so name the screen, the button and the flag.
Sources
- App Review Guidelines · Apple Developer · “Last Updated: October 16, 2026”
- App Store Connect Help: App Review information · Apple Developer
- Provide information for a complete review · Apple Developer · App Review Help
Quotes checked on 27 October 2026. Apple and vendors change these pages, so read the current version before you submit. ReviewNotes is not affiliated with Apple.