Publishing a game on the App Store and Google Play involves four things: a developer account, a store listing, a set of declarations about age and privacy, and a review by the store. None of it is hard once you know what is coming, but each step has details that commonly delay first launches.
Both stores want the same basic assurance: that your game is what it says it is, that it handles player data honestly, and that it is suitable for the audience it claims. If you prepare for those three things, review usually goes smoothly.
This guide covers the process in general terms. Store rules change over time, so always check each store's current guidelines before you submit.
Step 1: set up developer accounts
You need a developer account with Apple and another with Google. Each requires identity details and a fee, and organisation accounts usually need verification of the business, which can take time. Start this early; it is often the first unexpected wait.
Decide whose name the game will publish under. If it is a branded game, you may want it under your organisation's account so it appears as yours. A studio can then be given access to manage builds and listings for you. Make this choice before launch, because moving a published game between accounts later is possible but adds steps.
Step 2: prepare the store listing
The listing is your game's shop window. Each store asks for similar items:
- Name and subtitle or short description. Clear, accurate and within character limits.
- Full description. What the game is, how it plays, and what makes it worth installing.
- Screenshots for each required device size, showing real gameplay.
- App icon at the required sizes.
- Preview video, optional but useful.
- Category, keywords and support details, including a support address and a privacy policy link.
Write the description for players, not for search engines. Say plainly what someone gets. Avoid claims you cannot back up, such as being the "number one" game, because stores and players both notice.
Screenshots should show the game as it really looks. Mock-ups that misrepresent gameplay can lead to rejection and disappointed players.
Step 3: answer the age rating questions
Both stores rate games through a questionnaire about content: violence, fear, language, gambling-style mechanics, user-generated content, chat and more. Your answers produce an age rating shown on the listing.
Answer honestly and precisely. Cartoon violence is rated differently from realistic violence, and features like open chat or simulated gambling can raise a rating significantly. If a store's reviewer sees content you did not declare, the game can be rejected or the rating changed.
If your game is meant for children, there are extra rules. Both stores have specific programmes and requirements for games aimed at kids, including limits on advertising, data collection and external links. Our children page explains the approach we take.
Step 4: declare privacy and data use
Both stores require a privacy policy and a declaration of what data your game collects and why. Apple shows this as privacy details on the listing; Google asks for a data safety form. They cover things like:
- Whether you collect contact details, identifiers, usage data, location or purchases
- Whether that data is linked to the player
- Whether it is used for tracking or advertising
- Whether it is shared with others
- How players can request deletion of their account and data
These declarations must match what the game, and any services built into it, actually do. A common cause of rejection is a mismatch: the form says no data is collected, but the game includes an analytics or sign-in feature that does collect it.
If players can create accounts, both stores expect a way to delete the account from inside the game or through a clear web page. Plan for this from the start rather than adding it after a rejection.
Step 5: test before you submit
Both stores offer ways to send test builds to a limited group before the public launch. Use them. Testing with real players on their own devices catches crashes, confusing screens and problems on older phones.
Google may require new personal developer accounts to run a closed test with a group of testers for a period before going to production. Check the current rule when you set up the account, so it does not surprise you near launch.
Step 6: submit for review
When the build and listing are ready, submit for review. A reviewer checks that the game works, matches its description and follows the guidelines. Most reviews are routine.
Common reasons for rejection include:
- Crashes or broken features during review
- Login walls with no test account provided to the reviewer
- Privacy declarations that do not match the game's behaviour
- Missing account deletion
- Permission requests with unclear explanations
- Purchases that do not use the store's payment system where it is required
- Misleading screenshots or descriptions
If you are rejected, the store explains why. Fix the issue, reply clearly, and resubmit. A polite, specific reply often resolves things quickly.
Step 7: launch and keep it current
Once approved, you can release immediately or schedule a date. You can also release to some countries first, which is useful for a soft launch.
After launch, keep the listing and declarations current. New features that collect data need updated privacy forms. New content may change the age rating. Both stores also expect games to keep up with newer operating system versions over time, so plan regular updates. The live ops page covers ongoing care.
Getting help with your launch
Store launch is a step many first-time publishers underestimate. On our projects, store listings, screenshots, ratings, privacy forms and review are part of the work, on your accounts or ours on your behalf. Our own games, including Game Collection and Ludo Fighters, have been through both stores. If you want a game built and launched end to end, tell us about it.
Frequently asked questions
Do I need separate accounts for the App Store and Google Play?
Yes. Apple and Google each require their own developer account, with their own verification and fees. Organisation accounts may take longer to verify than personal ones.
What is the most common reason games get rejected?
Crashes during review and privacy declarations that do not match what the game actually does are among the most common. Missing account deletion and unclear permission requests are frequent too.
Can I publish a game under my company name if a studio builds it?
Yes. The game can be published on your developer account, and the studio can be given access to manage builds, listings and review on your behalf.
Do age ratings matter for a casual game?
Yes. Every game needs an accurate rating. Features such as open chat or gambling-style mechanics can raise it, and undeclared content can lead to rejection.