Skip to content

Unofficial tool, not affiliated with Apple. It doesn't guarantee approval. Your flags never leave your browser.

Guideline 2.5.19 · 2.3.1(a) · Notes for Review

Describe your feature flags with specificity.

Paste your Remote Config or LaunchDarkly flags. ReviewNotes sorts your paywall tests, kill switches, staged rollouts, region gates, dormant features and debug menus, catches leftovers that look like hidden features, and writes App Review notes you can paste straight in.

  • Free, no sign-up
  • Runs in your browser
  • 4000-byte counter
An app icon with a green approval check, surrounded by feature-flag toggles and a review note

How it works

From a flag dump to notes a reviewer can follow.

  1. 01 Paste your flags

    Drop in a Firebase Remote Config template, a LaunchDarkly export, a .env file or just a list of names.

  2. 02 We sort them

    Each flag gets a category from its name, value and targeting rules: paywall test, kill switch, rollout, region gate, dormant or debug. Override anything.

  3. 03 Leftovers get caught

    Names with debug, test, staging, internal or bypass in them are the classic “hidden feature” rejection. The checklist fails if one is on.

  4. 04 A note Apple can follow

    Every remote feature with what it does, its state during review and how to reach it. Counted against the 4000-byte limit, ready to paste.

The generator

Flags in. Review notes out.

Everything runs in your browser. Your draft saves itself as you type.

1 Import your flags

Ctrl + Enter

Notes for Review

0 characters · 0 / 4,000 bytes

4 Pre-submit checklist

Import flags to see what a reviewer might trip over.

PDF checklist export is part of Pro.

What you get

Everything a reviewer needs, nothing they can trip on.

Specific, not generic

Apple rejects generic descriptions. Each flag gets a name, what it does, its state during review and the exact tap path.

Reads your real exports

Firebase Remote Config, LaunchDarkly, plain JSON, .env or a list.

Paywalls, rollouts, regions

A/B tests, percentage rollouts and EU-only screens get their own section, so the reviewer knows why their screen may differ.

Catches debug leftovers

debug, test, QA, staging, internal, bypass, cheat: if a reviewer can reach it, it reads as hidden. The checklist fails until it's off.

4000-byte counter

Apple limits the Notes field to 4000 bytes, not characters. We count both and offer a compact layout.

Private by design

Nothing is uploaded. Drafts autosave in your browser.

Guide · App Store guideline 2.5.19

What Apple actually says about hidden features

Quoted from the App Review Guidelines, last updated 16 October 2026. Checked on 23 October 2026.

“Don’t include any hidden, dormant, or undocumented features in your app; your app’s functionality should be clear to end users and App Review.”

Guideline 2.5.19 · Performance › Software Requirements

“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.”

Guideline 2.3.1(a) · Performance › Accurate Metadata

So are feature flags allowed?

Yes. Remote config, A/B tests and staged rollouts are everywhere on the App Store. The problem is undisclosed behaviour: a reviewer sees one app, and a flag flip later turns it into another. That's what 2.5.19 calls hidden or dormant features.

The fix is disclosure. Apple's own submission checklist asks you to “Include detailed explanations of non-obvious features and in-app purchases in the App Review notes, including supporting documentation where appropriate.” Your Notes for Review should say which features are remotely controlled, what state they're in during review and how to reach them, and confirm that developer switches are off.

Keep it under the limit: “The Notes field can contain up to 4000 bytes.”

Read guideline 2.5.19 App Review information help

App Store review notes template example
NOTES FOR APP REVIEW: [APP] [VERSION]

This build uses remote configuration. Every remotely
controlled feature is listed below with its state
during review and how to reach it.

DEMO ACCOUNT
Username: [demo user]   Password: [demo password]

REMOTELY CONFIGURED FEATURES
AI Coach (flag: enable_ai_coach)
  What it does: chat coach that plans weekly workouts
  During review: ON for the reviewer
  How to reach it: Home → Coach tab → Start session

IN-APP PURCHASES AND PAYWALL EXPERIMENTS
Paywall layout test (flag: paywall_variant)
  Two layouts; every in-app purchase is in both.

DEVELOPER AND INTERNAL SWITCHES (ALL OFF)
debug_menu_enabled, use_staging_api: OFF in this build
and not reachable by users.

CONTACT
[name, email, response time]

Pricing

Free for every submission. Pro when you ship a lot.

No subscription. Pro is a one-time purchase, and it isn't on sale yet.

Free

€0forever

  • Unlimited flags per app
  • Firebase, LaunchDarkly, JSON, .env and list imports
  • Auto-classification with overrides
  • Pre-submit checklist
  • Copy or download the note
  • 2 saved apps + autosaved draft

Pro

Coming soon

€12one-time

  • Unlimited saved apps
  • Note templates (games, subscriptions, health, kids)
  • PDF checklist export for your team
  • Everything in Free

Nothing is charged today. Everything in Free works now.

FAQ

Notes for Review, answered

Sources

Quotes last checked against these pages on 23 October 2026.

  • App Review Guidelines

    Apple Developer · page “Last Updated: October 16, 2026”

    Guideline 2.5.19 (hidden, dormant or undocumented features), 2.3.1(a) (describe features with specificity in Notes for Review) and 2.1(b) (in-app purchases must be reviewable).

  • App Store Connect Help: App Review information

    Apple Developer

    Where the Notes field lives, demo-account sign-in fields, and the 4000-byte limit on Notes.

Your next submission, fully disclosed.

Two minutes now beats a week-long rejection loop.