# Mobile game development timeline: how long launch takes
Source page: https://dfygames.com/guides/mobile-game-timeline (published 2026-10-19, updated 2026-10-19) · Topic: Buying a game
Cite as: DFY Games, "Mobile game development timeline: how long launch takes", updated 2026-10-19, https://dfygames.com/guides/mobile-game-timeline

**Quick answer:** Build time and launch time run on different clocks. A DFY Core game targets a submission-ready build in 10 business days after payment, complete intake and blueprint approval; Advanced reaches a polished first playable in 10 business days and normally completes within 30 days. After that, new personal Google Play accounts need a closed test with at least 12 opted-in testers for 14 days, and both stores review on their own schedule.

- Core build target: 10 business days
- Advanced full build: Within 30 days
- Google closed test (new personal): 12 testers for 14 days
- Google review: Up to 7 days, can be longer
- Apple review: Apple-controlled, no fixed time

## Three clocks: the build, your approvals and the stores

Most launch dates slip because three different schedules get merged into one. The studio controls the build. You control how fast decisions come back. Apple and Google control testing requirements and review. Plan each separately and the overall date becomes predictable.

| Phase | Controlled by | Typical length |
| --- | --- | --- |
| Intake, payment and blueprint | You and the studio | Before the clock starts; blueprint approved on day 1 |
| Build | Studio | Core: 10 business days. Advanced: first playable in 10, full build within 30 days |
| Feedback and approvals | You | 24-hour windows at the prototype and visual checkpoints |
| Google Play closed test | Google (new personal accounts only) | At least 12 opted-in testers for 14 days, then an application for production access |
| Google Play review | Google | Up to 7 days, longer in exceptional cases |
| App Store review | Apple | No published fixed time |

DFY Games publishes its timing in fixed wording so that it cannot be read as a launch promise: "Core: submission-ready build targeted within 10 business days after scope lock and complete intake." "Advanced: polished first playable targeted within 10 business days, with the full submission-ready build normally completed within 30 days." "Store access, closed testing and review happen afterward and are controlled by Apple and Google."

Sources: Google Play Console Help, "Testing requirements for new personal developer accounts" https://support.google.com/googleplay/android-developer/answer/14151465?hl=en; Google Play Console Help, "Publish your app" https://support.google.com/googleplay/android-developer/answer/9859751?hl=en; Apple Developer, "App Review" https://developer.apple.com/app-store/review/

## Build milestones for a focused game

A one-loop game, the kind that fits the [Core package](https://dfygames.com/games), moves through five build checkpoints. Each one gives you something to look at or play:

| Checkpoint | When | What you see |
| --- | --- | --- |
| Blueprint | Day 0-1 | Mechanic, audience, visual direction, monetization map |
| Core prototype | Day 2-3 | Playable loop and the first feedback window |
| Art and systems | Day 4-7 | Final style, progression, sound and monetization |
| Device QA | Day 8-9 | Bug list, performance check, store-ready build |
| Submission kit | Day 10 | App icon, screenshots, copy, policy checklist, build |

A bigger studio build with several systems runs on months rather than days, mostly because more systems means more design decisions, more content and more testing. Our [walkthrough of the first ten business days](https://dfygames.com/guides/dfy-game-build-process) goes through each checkpoint in detail.

## The approvals that move your date

The customer side of the schedule is small but it sits on the critical path. Under DFY Games' terms, late feedback shifts the delivery date by the length of the delay. These are the moments that matter:

- Day 1: approve the blueprint. Nothing is built until the mechanic, screens, art and monetization are locked.
- Days 2-3: play the prototype and send one consolidated set of notes from one feedback owner.
- Days 4-7: approve the visual checkpoint. New systems at this stage are scope changes, not revisions.
- Days 8-9: provide store and legal information, and have your developer accounts ready.
- Day 10: approve the submission.

> Open the developer accounts in week one: Apple and Google both verify new developer accounts before you can publish, and that can take a while. Start registration as soon as you commit to the build, so the accounts are ready by day 8.

## Google Play closed testing for new personal accounts

Google requires personal developer accounts created after November 13, 2023 to run a closed test with at least 12 testers who stay opted in for 14 days in a row, then apply for production access. Organization accounts and older personal accounts are not subject to this rule, so check which kind you have before you put a date on anything.

DFY Games coordinates up to 15 invited playtesters as part of every package. That helps you reach the threshold, and the rule still applies in full: the account owner remains responsible for eligibility and for truthful answers in the production-access application. Recruit testers who will keep the build installed and actually play it; testers who drop out reset your planning.

Sources: Google Play Console Help, "Testing requirements for new personal developer accounts" https://support.google.com/googleplay/android-developer/answer/14151465?hl=en

## App Store and Google Play review

Google says review can take up to seven days, or longer in exceptional cases. Apple publishes no fixed review time and expects the submission to be complete: working build, accurate metadata, privacy details and a way for the reviewer to reach every feature. A rejection adds a fix-and-resubmit loop, which is why each DFY Games package includes one initial submission and review-response cycle. No studio can guarantee approval or a review date; plan store review as its own stage after the build and your approvals.

Before you submit, run through the [mobile launch checklist](https://dfygames.com/guides/mobile-launch-checklist). Most avoidable delays come from missing disclosures or reviewer access rather than the game itself.

Sources: Google Play Console Help, "Publish your app" https://support.google.com/googleplay/android-developer/answer/9859751?hl=en; Apple Developer, "App Review" https://developer.apple.com/app-store/review/

## A worked calendar for a Core game

> Illustrative schedule, not a promise: Assumptions: Core package, blueprint approved on a Monday, feedback returned within 24 hours each time, and a new personal Google Play account. Ten business days puts the submission-ready build at the end of the second week. The iOS build can go to Apple review straight away. On Android, the 14-day closed test starts once the testers are opted in, so production access cannot be requested before roughly week five, and Google's review comes after that. With an organization account or an older personal account, Android submission can follow the build directly.

Notice where the time goes: on Android, more of it is store process than build. Starting tester recruitment during the build, rather than after delivery, is the single cheapest way to shorten the calendar.

Sources: Google Play Console Help, "Testing requirements for new personal developer accounts" https://support.google.com/googleplay/android-developer/answer/14151465?hl=en; Google Play Console Help, "Publish your app" https://support.google.com/googleplay/android-developer/answer/9859751?hl=en

## How a bigger build and a launch campaign change the schedule

Advanced uses the same first ten business days to reach a polished first playable vertical slice, then completes the full submission-ready build within 30 days, depending on the written blueprint, asset volume and feedback speed. The store phases come after that, exactly as for Core.

If you choose a package with the launch service, the 30-day campaign period starts when campaigns go live, after the game is published. Ready to put a date on your own game? [Start your build](https://dfygames.com/start) and the blueprint will set out the schedule in writing.

## FAQ

**How long does it take to make a simple mobile game?**
A focused one-loop game in DFY Games' Core package targets a submission-ready build in 10 business days after payment, complete intake and blueprint approval. Store testing and review come afterward.

**Why can't my game go live the day the build is finished?**
Apple and Google review every submission, and new personal Google Play accounts must first run a 14-day closed test with at least 12 testers. Those steps are outside any studio's control.

**Do I need 12 testers for Google Play?**
Only if your developer account is a newly created personal account. Organization accounts and older personal accounts can publish without that closed test.

**How long does App Store review take?**
Apple does not publish a fixed time. A complete submission with working reviewer access avoids the most common delays.

**What makes a game take longer than planned?**
Slow feedback and new ideas added after the blueprint is approved are the usual causes on the build side; account setup and closed testing are the usual causes on the store side.

## Related
- Service page: [Mobile game development](https://dfygames.com/games)
- [DFY Games process: what happens in your first ten business days](https://dfygames.com/guides/dfy-game-build-process)
- [Before you submit: a mobile app launch checklist](https://dfygames.com/guides/mobile-launch-checklist)

## Sources
- Google Play Console Help, "Testing requirements for new personal developer accounts" https://support.google.com/googleplay/android-developer/answer/14151465?hl=en
- Google Play Console Help, "Publish your app" https://support.google.com/googleplay/android-developer/answer/9859751?hl=en
- Apple Developer, "App Review" https://developer.apple.com/app-store/review/

---
DFY Games (Done For You Games), https://dfygames.com. More guides: https://dfygames.com/guides · Index for AI assistants: https://dfygames.com/llms.txt