How long does it take to build an app? It depends mostly on scope: how many screens, how many types of user, and how many outside systems it talks to. Store review and account setup sit on top, and they are the waits most people forget to plan. This page shows what the time is made of.
The stages and what stretches each one
| Stage | What happens | What stretches it |
|---|---|---|
| Scope and prototype | Decide the one job, list screens and rules, build a clickable prototype | Unclear goals, too many roles, slow decisions |
| Design | Real screens, states, icons, copy | Many screens, custom motion, late content |
| Build | Code, backend, admin, payments, integrations | Outside systems you do not control |
| Testing | Real devices, edge cases, bug fixes | More platforms, more roles, offline use |
| Store submission | Accounts, listing, screenshots, review | Rejections, account checks, new-account rules |
| Launch | Release, watch for bugs, fix | Late changes right before release |
Anyone who gives you a date without a written scope is guessing.
The waits nobody plans for
- Apple review. Apple's App Review page says it is "typically reviewing at least 50% of submissions in less than 24 hours and 90% in less than 48 hours" (Apple App Review, as listed on 9 October 2026). A rejection restarts the clock. See App Store rejection reasons.
- Google Play review. Google's help page says certain developer accounts may get extra checks, which "may result in review times of up to seven days or longer in exceptional cases" (Play Console Help, as listed on 9 October 2026). Plan for a week, not an hour.
- The 12 testers rule. New personal developer accounts created after 13 November 2023 must run a closed test with "a minimum of 12 testers who have been opted in continuously for at least 14 days" before applying for production access. Google says reviewing that application "usually takes seven days or less, but can occasionally take longer" (Google testing requirements). No developer can shorten the 14 days, so start early. See Play Store closed testing with 12 testers.
- Apple organisation enrollment. Apple requires a D-U-N-S Number for your legal entity (enrollment requirements). Apple's D-U-N-S page says "please allow up to 5 business days to receive your number from D&B" and then "up to 2 business days for Apple to receive your information" (Apple D-U-N-S help).
- Google organisation accounts. Google asks for a D-U-N-S number, and your details must match your Dun & Bradstreet profile (Play Console requirements). It states no timeline.
- Payment gateway verification. The gateway checks your business before you can go live. Each sets its own documents and timing, so ask the one you picked. See Razorpay vs Cashfree vs PayU.
What makes it longer
- Unclear scope. If the answer to "what does this screen do?" changes weekly, so does the date.
- Many user types. Customer, staff and admin are three apps' worth of screens.
- Integrations you do not control. A partner's API, a government portal or an old accounting tool can stall on access or approvals.
- Waiting on content. Photos, copy, prices and legal text arrive last on most projects.
- Changes mid-build. A new feature in week 4 moves the date.
- Two separate builds. iPhone and Android built separately double the testing.
What makes it shorter
- One platform first. Launch where most of your users are.
- Cross-platform code. One codebase removes duplicate work, though not store work. See React Native vs Flutter vs native.
- One job. Cut the app to the one thing people open it for.
- Fast decisions. A named person who can say yes in a day saves more time than any tool.
Start the clock early
None of these need a developer.
- Own the accounts. Create the Apple and Google developer accounts in your name or your company's.
- Find or request your D-U-N-S Number for an organisation account.
- Start the 12-tester list if you are on a new personal Google account.
- Collect content. Logo, photos, descriptions, prices, terms and a privacy policy.
- Name one decision maker who can approve screens within a day.
- Write the requirements. See mobile app requirements document, and how to publish an app on the Play Store for what Google asks for.
Want a scope and timeline for your idea? Tell us about your project.
Frequently asked questions
Can a single person develop an app?
Yes, if that person can do design, mobile code, a backend, testing and store setup, or will learn them. It usually takes longer than a team because the stages run one after another. A small first version with one job is realistic. Payments, roles and an admin panel are much harder alone.
What are the 7 stages of app development?
Lists differ. A common seven: idea and scope, prototype, design, build, testing, store submission, and launch with support. The stages overlap. For example, you can start Google's 12-tester period while the last screens are being built.
Can ChatGPT build an app?
It can write code for parts of an app. It cannot decide your scope, test on real phones, set up store accounts, or pass store review for you.
How long does App Store review take?
Apple's App Review page says it typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours, as listed on 9 October 2026. That is not a guarantee. A rejection means fixing the issue and resubmitting. See App Store rejection reasons.
How long does Google Play review take?
Google's page says certain developer accounts may see review times of up to seven days or longer in exceptional cases. New personal accounts also need a closed test with 12 testers for 14 days before applying for production access, and Google says reviewing that application usually takes seven days or less. Allow for both.