The short answer
To publish an app you need an Apple Developer Program membership and a Google Play developer account, a store listing with screenshots and a privacy policy, the privacy and data-safety forms filled in, and a build that passes review. New personal Google Play accounts must first run a closed test with at least 12 testers for 14 days. Plan time for this before your launch date.
Before you start: the accounts
- Apple Developer Program. A paid yearly membership, as an individual or an organisation. An organisation account needs a D-U-N-S number, which can take time to get, so start early.
- Google Play Console. A one-time registration fee, with identity verification. Organisation accounts need business details and verification too.
- Open them in the business's name, not a developer's personal account, so the app always belongs to the business.
Worth knowing
Check the current fees and verification steps on Apple's and Google's own pages when you sign up; both change their rules from time to time.
Google Play's testing requirement for new accounts
At the time of writing, a new personal Google Play developer account cannot publish to production straight away. It must first run a closed test with at least 12 testers who stay opted in for 14 days, then apply for production access. Organisation accounts are not held to this rule.
Twelve real testers for two weeks is easy to underestimate. Line them up before the build is ready: friends, early customers, a waiting list. Ask them to open the app regularly, not just install it.
What both stores ask for
- 01Store listing. App name, short and long description, icon, screenshots for each required device size, category and contact details.
- 02Privacy policy at a public URL, matching what the app actually does.
- 03Privacy forms. Apple's App Privacy details and Google's Data safety section: what data you collect, why, and whether it is linked to the user.
- 04Content rating questionnaires.
- 05Account deletion. If users can create an account, both stores expect a way to delete it, in the app and (for Google) from the web.
- 06Test login. If the app needs an account, give reviewers working credentials, or the review will stall.
The most common reasons apps get rejected
- Crashes or broken features during review, often on a device size nobody tested
- Placeholder content, or features that are not finished
- Privacy forms that do not match what the app collects
- No way to delete an account that the app lets you create
- Selling digital content without the store's in-app purchase system, where the rules require it
- Missing reviewer login details
- An app that is little more than a website in a wrapper
A release checklist we use
- 01Test on small and large phones, both platforms, on a slow connection
- 02Check every permission prompt has a clear reason string
- 03Fill the privacy forms from what the code actually does
- 04Prepare screenshots and listing text
- 05Add reviewer credentials and notes explaining anything unusual
- 06Submit to the testing track first, then production
- 07Set up crash reporting before the first public release
Plan the launch around review
Review usually takes from hours to a few days, and a rejection adds a fix and another review. Announce a launch date only after the build is approved, or keep a few days of buffer. With React Native and Expo, many small fixes after launch can ship as over-the-air updates without a new review; native code changes still need one (see native vs cross-platform apps).
We take apps from first sketch to the store, including the accounts, listings and review. Book a 15-minute call if you are planning a launch. Related reading: the Firebase Auth logout fix on Android.
“The step that surprises founders most is Google's 12 testers for 14 days. Two weeks is a long time to discover at the end. Plan it in from the start.”
Questions people ask us.
An Apple Developer Program membership, a store listing with screenshots, a public privacy policy, the App Privacy details, a way to delete accounts if users can create them, reviewer login details if needed, and a build that passes review.
New personal Google Play developer accounts must run a closed test with at least 12 testers opted in for 14 days before they can apply for production access. Organisation accounts are not held to this requirement.
Usually from a few hours to a few days on each store. A rejection adds the time to fix and resubmit, so leave a buffer before any announced launch date.
Common reasons are crashes during review, unfinished content, privacy forms that do not match the app, no account deletion, digital purchases outside the store's payment system where required, and missing reviewer login details.