MobileCodeCross TeamUpdated
How long it takes to build a mobile app
Simple apps often take a few months; medium builds about six months; complex work can run toward a year. Auth, payments, and stores drive time.
Mobile
10 min
- Simple
- 2-4 months
- Medium
- 4-7 months
- Complex
- 7-12+ months
CodeCross planning estimate
CodeCross planning estimate
CodeCross planning estimate
A mobile app is not one clock. Scope, design, build, test, store review, and launch each take time. Some of that time is yours. Some of it belongs to Apple or Google. This page walks through those phases, what slows each one, and what the stores actually say about review. Month and week ranges below are a CodeCross planning estimate, not a store promise.
Builder prototypes belong on vibe coding. Put the first job in a partner brief before anyone quotes weeks.
What the stores publish about review time
Apple App Review says App Review typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours. You get email on status changes. You can also check status in App Store Connect. Apple says an incomplete submission can delay review or fail.
Google does not publish one typical review time for every Play update. What it does publish is the new-account gate. Personal Play accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in for 14 days before they can apply for production. Internal testing does not meet that rule. After you apply, Google says review usually takes seven days or less, and can take longer.
Those store clocks sit after your build. They do not replace scope, design, or test. A first upload that crashes or lacks a demo login may be delayed or fail review; Apple does not publish a separate statistical exclusion for those submissions. Apple’s App Review Guidelines say submissions should be final, tested on a device, and include a demo account when the app has login.
CodeCross planning ranges
These ranges are a CodeCross planning estimate for a team that already has store seats and a thin first-value job. They are not Apple or Google numbers.
- Thin MVP — often about 2–4 months when scope stays thin.
- Medium — often about 4–7 months with a real backend, payments, or more than one role.
- Complex — often about 7–12+ months for marketplaces, regulated work, or deep offline.
A Cursor prototype can look done in days. Store-ready auth, secrets, and review still take a real calendar. See what production-ready means.
Scope
Scope is the job a stranger can finish. Write that job down. Name what is out. Name who accepts it. This phase is short when the brief is honest. It stretches when the team keeps adding a second platform, a second role, or a payment path no one priced.
What slows scope: unowned Apple or Play seats, no named first-value path, and a prototype treated as the product. Put seats on the company from day one. See who owns App Store and Play Console. A partner brief should name the first-value job, the platforms in or out, and whose legal entity holds those seats. That document is what keeps week counts honest. See how to brief a mobile app partner.
Design
Design is the screens and empty states for that first job. It should include sign-in, errors, and the path back out. Apple’s Human Interface Guidelines sit next to App Review for a reason. A pretty flow that hides login or a broken link still fails review.
What slows design: redesigning every sprint, skipping empty states, and copying a website into a phone shell. Apple Guideline 4.2 says the app should be more than a repackaged website. Play’s functionality policy rejects apps with little utility or content.
Build
Build is the code, backend, and store listing fields. Auth, payments, and privacy forms belong here, not after upload. If money moves inside the app, read monetization before you wire a paywall.
What slows build: integrations without sandboxes, secrets in the client, and a second OS before the first path is green. Cross-platform can share UI work. It does not half store review. See native vs Flutter / React Native.
Test
Test on a device, not only a simulator. Apple’s before you submit list says test for crashes and bugs, keep metadata complete, and give App Review full access. If the app has accounts, give a live demo login and turn the backend on.
What slows test: no crash reporting on a release build, a demo account that fails from Apple’s network, and privacy forms that do not match the SDKs in the binary. Play Data safety must match what the app and its SDKs collect. Apple’s App Review page also says you should include a demo account and any special hardware notes. If the reviewer cannot sign in, the clock you wanted (50% under 24 hours) does not apply. Play’s testing requirements for new personal accounts are a second, separate calendar: 12 testers opted in to a closed test for 14 days in a row before you can even apply for production.
Store review
Review starts when the binary and listing are complete. Apple’s 24- and 48-hour figures are for submissions that are ready. Over 40% of unresolved Apple issues relate to Guideline 2.1 — crashes, placeholders, and incomplete information.
On Play, a new personal account still owes the 14-day closed test before production. That is calendar time you cannot skip. After you apply, Google says the production-access review usually takes seven days or less. A later update can still be rejected. If an update is rejected, the last live version stays on Play.
What slows review: missing demo login, a privacy policy that does not match the binary, payments that skip in-app purchase, and a thin web wrapper. Budget a resubmit. See why apps get rejected.
Launch
Launch is the listing going live and the first week of watching crashes, sign-in, and payments. Apple’s upcoming requirements still apply after you ship. Apps uploaded to App Store Connect must target iOS 13 or later (since 9 September 2026) and must be built with Xcode 26 or later using an iOS 26 SDK (since 28 April 2026).
What slows launch: a personal Apple ID holding the Account Holder seat, a Play listing that does not match the binary, and paid ads before the first-value path is green. Harden a builder MVP before you buy clicks. A rewrite is not the default. See rewrite vs harden. A first week of launch is not “done.” You still owe a release build with crash reporting, a person who can ship a hotfix, and a calendar for the next store SDK bump. Those hours belong in the estimate. They are not hidden inside Apple’s 48-hour review share. Year-one keep-alive is a separate budget. See year-one TCO.
How to compress without lying
Freeze the first-value job. Start store seats in week one. Keep decisions under 48 hours. Do not open a second platform until the first path works. Read an estimate as milestones and assumptions, not a slogan. See how to brief a mobile app partner. Scope and store-seat setup can start the same week. Design can start while the brief is still thinning, as long as the first-value job is frozen. Build and listing fields can overlap once auth and payments are named. Test should not wait for the last feature. Store review cannot start until the binary and listing are complete. Launch watch — crashes, sign-in, payments — starts the day the listing is live. Apple’s upcoming requirements still apply after that day. If the brief is still fuzzy, Book a free call.
Timeline by App Complexity
weeksComplex
42 weeks
7–12+ months, CodeCross planning estimate · Planning 4 · Design 6 · Development 24 · Testing 6 · Deployment 2
Weeks (CodeCross planning estimate)
- Planning
- Design
- Development
- Testing
- Deployment
The Six Phases of Mobile App Development
01 →
Scope
CodeCross estimate: 2–4 weeks
02 →
Design
CodeCross estimate: 3–6 weeks
03 →
Build
CodeCross estimate: 8–20 weeks
04 →
Test
CodeCross estimate: 3–6 weeks
05 →
Store review
Apple: 50% < 24h, 90% < 48h (typical)
06
Launch
Keep-alive after the listing is live
App Development Timeline by Platform Choice
weeksLow-code / No-code
5–8 weeks
Development weeks (CodeCross planning estimate)
App Store Review Timelines (2026)
Apple App Store
Typical review
50% < 24h
Most reviews
90% < 48h (typical)
Incomplete file
Delayed
Google Play
Closed test
12 testers, 14 days
Production access
Usually ≤ 7 days
Rejected update
Last live stays
FAQ
Does Apple’s 90% in 48 hours figure include a first upload that is missing a demo login?
Apple does not specify that exclusion. Its 90% figure describes typical review times, not a guarantee for a particular submission. Missing information may delay review or cause the submission to fail.
Does a new personal Play account start the 14-day closed test clock on internal testing?
No. Google’s testing requirements say the 12 testers must be opted in to a closed test for 14 days in a row. Internal testing is optional and does not meet that rule.
Which phase usually slips first when store seats are still on a personal email?
Store review and launch. The binary can be ready while the company still cannot submit. Move seats before you freeze the date. See who owns the consoles.
Are the month ranges on this page a store promise or a CodeCross planning estimate?
They are a CodeCross planning estimate. Apple publishes 24- and 48-hour review shares. Google publishes the 14-day closed test and a usual seven-day production-access review. Neither store publishes a 2–4 month build clock.
Does picking Flutter instead of two native teams cut store review time in half?
No. Shared UI can shorten build. Apple and Google still review each binary. See native vs Flutter / React Native.
Thirty minutes with a senior teammate — honest next steps.
Want a second pair of eyes on your app?
Tell us what you built and where it's stuck. We'll tell you what it takes to make it ready for real users.
Prefer writing? Send project details on the contact page.