Skip to content
WebViewGold Vibe Coding to App Store
English
Get WebViewGold

App Store review

App Review notes: templates for web-based apps (login, purchases, location, AI)

Reviewers spend minutes with your app, not hours. The notes field is where you tell them what the app does, how to get past the login and why it asks for a permission. Good notes turn "we could not verify" rejections into approvals. Here are templates you can paste and adapt.

From $109 one-time per platform, or let our team do it all from $698.

  • Approval guarantee – or money back within 14 days
  • No coding needed
  • One-time payment, free updates
  • 24/7 human support
  • Made in Germany since 2014 · ISO 27001

Where the notes live

Apple: App Store Connect → your app → the version → App Review Information. It has a Sign-in required switch with username and password, a contact name, phone number and email, a Notes field (up to 4,000 characters) and attachments (screenshots or a video). Reviewers read the notes before they open the app, and they test on iPhone and iPad.

Google: Play Console → App content → App access. Choose "All or some functionality is restricted", then add one or more instruction sets with username, password and other steps. Google's review is partly automated, so credentials that work on the first try matter even more; the App access instructions carry the same information as Apple's notes.

What every note should contain

  • One or two sentences on what the app is and who uses it, written for a stranger.
  • The native features that go beyond the website: push notifications, Face ID, offline screen, QR scanner, share sheet. This answers Guideline 4.2 before it is asked.
  • A demo account that never expires, with no two-factor code, email verification or captcha in the way. If the account needs a code, make it a fixed one and write it down.
  • The exact clicks to reach gated screens (dashboard, paywall, admin area).
  • Which permission prompts will appear and why (camera for QR check-in, location for nearby offers).
  • Payments: say that digital features use in-app purchase and that any Stripe checkout is for physical goods, if that applies.
  • A contact who answers within hours. Reviewers do call.

Template: app with login

Paste into the Notes field and the Play App access instructions. Replace the bracketed parts.

App Review notes (login)
[APP NAME] is a [one-line description, e.g. habit tracker for remote teams]. Users sign up with email or Google / Apple, create [what they create] and get reminders as push notifications.

DEMO ACCOUNT (no 2FA, does not expire)
Email: reviewer@[yourdomain.com]
Password: [fixed password]
The account already contains sample data so every screen has content.

HOW TO TEST
1. Open the app, tap "Log in", enter the demo account.
2. The home screen shows [what]. Tap [tab] to see [feature].
3. Settings contains "Delete account" (account deletion is implemented server-side) and the privacy policy.

NATIVE FEATURES BEYOND THE WEBSITE
- Push notifications for [what] (permission is requested after sign-up, not at first launch)
- Face ID / fingerprint lock for the account screen
- Native offline screen with retry
- [Share sheet / QR scanner / other]

Sign in with Apple is offered next to Google sign-in. No account is required to read the public [pages], but all personal features need the demo account above.

Contact for questions during review: [name], [phone with country code], [email].

Great work! Never coded anything but managed to work with this. Easy and fast! Also with great help from the creators!

Lucas Dubois · CodeCanyon

Template: app with in-app purchases

Add it below the login template. Make sure the demo account has no active subscription so the reviewer can see the paywall.

Additional paragraph for apps with IAP or subscriptions
IN-APP PURCHASES
Premium features are sold through Apple in-app purchase (auto-renewable subscriptions "Premium Monthly" and "Premium Yearly"), implemented with RevenueCat. The demo account has no active subscription, so the paywall appears when tapping [where].
Restore Purchases is available under Settings, Subscription.
Subscription terms, price, duration and links to the Terms of Use and Privacy Policy are shown on the paywall.
The [shop / booking] section sells [physical goods / in-person services] and therefore uses our web checkout, as permitted by Guideline 3.1.3(e) / 3.1.3(d).
There is no other way to pay inside the app.

Template: location, camera and AI features

Keep only the paragraphs that apply. The AI paragraph addresses Guideline 1.2 (user-generated content) and the Play policies on generated content.

Additional paragraphs for permissions and AI
LOCATION
The app asks for location (while in use) when the user opens the "Nearby" tab, to show [what] within a few kilometers. Location is never collected in the background and can be denied; the tab then shows a manual search field. The demo account works from any location; sample entries are seeded worldwide.

CAMERA
The camera is used only for [scanning QR codes at check-in / uploading a profile photo]. The permission prompt appears when tapping [button].

AI FEATURES
[Feature] generates text / images with [provider, e.g. OpenAI] from the user's input. Generated content is private to the user by default. Public posts can be reported with the "Report" button on every item and are reviewed within 24 hours; users can block other users under their profile. Our content policy is linked in Settings. The AI does not provide medical, legal or financial advice, and the app says so in the feature's intro screen.

Demo accounts that work on review day

Most "Information Needed" rejections are a demo account that did not work.

  1. Create a dedicated reviewer account

    [email protected] with a fixed password, flagged in your database so cleanup jobs and trial expirations skip it.

  2. Seed it with data

    An empty dashboard looks like a broken one. Add sample items, a completed order, a few notifications.

  3. Remove every gate

    No email verification, 2FA, captcha or phone number step. If your product forces a code, hard-code one for this account and write it in the notes.

  4. Make content visible everywhere

    Reviewers sit in other countries and time zones. Region locks, geofences and "no events today" states hide your app's value.

  5. Test on the exact build

    Install the exact build you will submit, log out, and log in by typing the credentials from the notes.

  6. Keep it alive after approval

    Every update is reviewed again. The same account must still work in six months.

Attachments and common mistakes

  • For multi-step flows, attach a 30 to 60 second screen recording of the main path. Apple accepts video attachments; it is the fastest way to prevent "we could not locate the feature" replies.
  • Never write "this is our website as an app". It is an invitation to a 4.2 rejection; describe the native features instead.
  • Sign-in required switched off while the app shows a login wall: Guideline 2.1 "Information Needed" within a day.
  • Notes that contradict the listing or screenshots (features that are "coming soon") trigger 2.3.
  • Changing the login flow in a later version without updating the notes.

Frequently asked questions

Do reviewers actually read the notes?

Yes. Rejection messages often quote them; good notes are the difference between a 24-hour approval and a week in Resolution Center.

Can I skip the demo account if sign-up is free?

Apple still prefers one, and any verification email or code during sign-up can block the reviewer. Provide the account; it costs two minutes.

My app is only for my company's employees. What do I write?

Say so, provide a demo account and describe the workflow. If the app is truly private, consider Apple's unlisted app distribution or Apple Business Manager instead of the public store.

Do I need to rewrite the notes for every update?

They carry over per version. Update them whenever the login, pricing or permissions change, and check that the demo account still works before each submission.

Three ways to get your app into the stores

Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.

Do it yourself

$109 per platform, one-time

The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.

See plans on the main page

Cloud Builder

$349 per license, one-time add-on

No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.

How the Cloud Builder works Try the free demo

Full Service

$698 per platform $798

Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.

Full Service details Powered by WeSetupYourWebViewApp

Winter Sale prices valid until December 31, 2026.

Ready to ship your app?

App Store & Google Play approval guarantee – or your money back within 14 days

Rather hand it over? Full Service: we configure, build and deliver within 72 hours, from $698 per platform. Questions? Chat with us 24/7.

Refunds are granted under the conditions listed in our FAQ: a non-content rejection by Apple and/or Google, claimed within 14 days after purchase.