Giving App Reviewers a Demo Login: What Apple and Google Need From You
Short answer: If your app sits behind a sign-in, the reviewer at Apple or Google must be able to get inside and see every feature without waiting for you. Provide a working demo account with realistic data, put the details in the review fields the stores give you, and add short notes explaining anything that is not obvious. A missing or broken demo login is one of the most avoidable reasons for a delay, and fixing it takes an afternoon rather than a week.
Who is the reviewer, and what do they do?
Picture a stranger with a test phone, a checklist and a limited amount of time. They open your app for the first time, they do not know your business, and they cannot ring your office to ask for a code. If the first screen asks for an email and password and they have neither, the review stops there.
Apple's App Review Guidelines say, in general terms, that if your app needs a login, you must supply an active demo account or a built-in demo mode so the app can be fully reviewed. Google Play has a section in the Play Console, under App content, where you declare whether parts of the app are restricted and provide access instructions. Check both vendors' current wording before you submit, as these screens change.
The owner's questions, answered
Which fields do we fill in?
On the Apple side, the version page in App Store Connect has an App Review Information area. It holds a sign-in required switch, user name and password fields, a notes box and contact details. On the Google side, the app access declaration lets you describe restrictions and add credentials or instructions. Put the same information in both, adapted to each form.
What kind of account should it be?
A dedicated account that you create only for reviewers, with a clear name such as "reviewer@yourcompany.example" (use a real address you control). Do not hand over a staff member's real login, and do not use a customer's. The account should have the permissions of your most capable role, or you should supply one account per role if the roles see different things. A bookkeeping app with "owner", "staff" and "client" views needs three logins, or one login that can switch.
What data should it contain?
Enough that no screen looks empty. A reviewer opening a jobs list and finding nothing may assume the app is broken or too thin. Seed the account with a handful of realistic but fictional records: five customers, three open jobs, one completed invoice. Avoid real customer names and personal details in demo data.
What if the sign-in uses a text message or email code?
This is where many submissions fail. A one-time code sent to a phone number the reviewer does not have cannot be completed. Options:
- Give the demo account a fixed code that your server accepts only for that account.
- Add a clearly labelled review bypass that skips the second step for that account only.
- Provide a built-in demo mode that needs no sign-in at all.
Whichever you choose, mention it in the notes and keep it restricted to the demo account so it cannot become a back door for everyone.
What if the app needs hardware or a physical place?
Say so, and give another route. A parking-sensor app, a kiosk companion or a delivery driver app can be hard to test without the real kit. Add a short screen recording to the notes or a link to one, plus a demo mode that simulates the hardware. State this plainly, for instance: "Bluetooth scanning needs our reader. A simulated scan is available under Settings, Demo."
Do we need to keep the account working after approval?
Yes. Reviewers may test again on updates, and a later version could be checked by someone else. Treat the account as part of your release process: confirm it works before each submission.
Writing review notes that help
Notes are not a sales pitch. They are directions. A good set has four parts:
- Access: how to sign in and which role the account has.
- Tour: the three or four places the reviewer should visit, in order.
- Oddities: anything that could look like a bug but is intended, such as an order screen that stays empty until a driver is assigned.
- Contact: a phone number and email that someone actually answers during review hours.
Here is an illustrative example for a fictional app: "Sign in with the details above. The account is a Manager. Tap Jobs, open 'Example Road clean', and press Complete to see the invoice step. Payment uses Stripe test mode in this build, so no card is charged. Push notifications are optional and can be skipped."
Pre-submission checklist
- [ ] The demo account signs in on a fresh install, on a phone that has never seen the app
- [ ] The password has no expiry that will trigger during review
- [ ] Multi-factor prompts are handled or bypassed for this account only
- [ ] Every main feature has sample data behind it
- [ ] The server is live and not in maintenance mode
- [ ] The review build points at a production-like environment, not a developer's laptop
- [ ] Payment screens work in a test mode, with a note saying so
- [ ] Account creation and deletion in the app work for a new reviewer, since stores look at those flows too
- [ ] Contact details are filled in and monitored
Mistakes that cause bounce-backs
Credentials typed with a trailing space. Copy, paste and try them yourself on a clean device.
A demo account locked after too many attempts. Reviewers sometimes try more than once. Disable lockout for that account.
A staging server that sleeps. Free hosting tiers can take a minute to wake. The reviewer may mark the app as unresponsive.
Geofenced content. If your app only works in one city, the reviewer in another country sees nothing. Add a way to set a location in demo mode.
Notes written for staff. Use plain language and avoid internal jargon and abbreviations.
FAQ
Do apps without a login need any of this?
If every feature is open from the first launch, you do not need demo credentials. You should still explain anything unusual in the notes.
Can we give the reviewer a real customer account?
No. Use fictional data. Real personal details in a test account create a privacy problem you do not need.
What happens if the reviewer cannot sign in?
Typically the submission is returned with a message asking for working access. You supply it and resubmit, which costs time but not a penalty, though repeated issues slow things down.
Does Google ask for the same thing?
Google asks you to declare restricted areas and provide instructions or credentials so its team can reach them. Fill the form in carefully rather than assuming Apple's notes carry over.
If you would like help preparing a reviewer-ready build, send us the details of your app and we will set up the demo account and notes with you.