The short answer: three realistic timelines
How long an app takes depends less on the developer's speed and more on which of three routes you take. A branded ready-made app reuses screens that already exist; a white-label app adds your own features on top; a custom app is designed and coded from a blank page.
| Route | Typical build time | Where the figure comes from |
|---|---|---|
| Branded ready-made app | 2–4 weeks | Growmoon's ready-made food and restaurant apps (from $1,500) |
| White-label app with your changes | 2–8 weeks | Growmoon's white-label guide (about $2,500–$15,000) |
| Custom app | 3–8 months; Clutch's guide says 20–40 weeks | Growmoon's white-label vs custom guide; Clutch app development guide |
Those numbers cover design, build and testing. They do not automatically include the slowest part for a first-time owner: getting developer accounts verified and the app approved by Apple and Google. That part runs on its own clock, and nobody can speed it up by working weekends. The rest of this guide shows where those weeks go and how to stop them landing at the end of your project.
If you are still choosing a route, the white-label vs custom comparison covers cost and trade-offs in detail.
The approval steps nobody on your team controls
These are the waits that sit outside the build. Each one is set by Apple, Google, Dun & Bradstreet or your payment gateway, and each one can be started before the first screen is designed.
| Step | Published wait | Who it applies to |
|---|---|---|
| D-U-N-S number for Apple | Up to 5 business days from D&B, then up to 2 business days for Apple to receive it | Companies enrolling as an organisation with Apple |
| D-U-N-S number for Google Play | Google warns processing can take up to 30 days | Organisation accounts on Google Play (required, with rare exceptions) |
| Google Play closed test | At least 12 testers opted in continuously for 14 days before you can apply for production | Personal Play accounts created after 13 November 2023 |
| Google Play production-access review | Usually 7 days or less, sometimes longer | The same personal accounts, after the 14-day test |
| Apple App Review | On average 90% of submissions reviewed in under 24 hours | Every iPhone app and update |
| Razorpay account activation | Typically 3–4 business days after you submit KYC | Indian businesses taking online payments in the app |
Two points stand out. First, Apple does not publish a time for reviewing an organisation's enrolment itself, and developers on Apple's forums describe waits of several weeks when company details do not match the D-U-N-S record exactly. Second, the Google numbers stack: a new personal account can lose three weeks or more between a finished app and a public listing, even if nothing goes wrong.
One more change is on the way. Google began rolling out Android developer verification in 2026, enforced from 30 September 2026 in Brazil, Indonesia, Singapore and Thailand, with a global rollout planned for 2027. If you plan to share an Android app outside the Play Store, for example as an APK for staff, budget time for that verification too.
Week by week: an 8-week launch with two tracks
The fix is to run the paperwork as a second track from week one, alongside the build. Here is an example for a white-label ordering or booking app with a few custom changes. Your developer owns the build track; you own the business track.
| Week | Build track (developer) | Business track (you) |
|---|---|---|
| 1 | Confirm the feature list, screens and what counts as done | Apply for D-U-N-S; open Apple and Google developer accounts in your company's name; start payment gateway KYC |
| 2 | Brand the app: logo, colours, menu or service data | Send final content: photos, prices, policies, privacy policy text |
| 3–4 | Build the agreed changes; first demo on real phones | Test the demo with two or three staff members and write down every issue |
| 5 | Fix issues; connect live payments and notifications | Recruit testers if you are on a personal Play account (aim for more than 12) |
| 6 | Upload test builds to TestFlight and the Play closed test | Prepare store listings: screenshots, description, support email, demo login for reviewers |
| 7 | Fix anything testers or reviewers flag | Approve the final build in writing |
| 8 | Submit to both stores; release when approved | Tell existing customers; put the app link on your counter, website and receipts |
Notice that nothing in the business track needs the app to be finished. Owners who leave it until week 6 usually find the build was on time and the launch was not. A ready-made app with almost no changes can compress weeks 2 to 5 into one or two weeks; a custom app stretches weeks 3 to 5 into several months, but the business track stays about the same.
Worked example: the same app, started two ways
Take one Indian business launching the same Android app built in 6 weeks. The only difference is when the owner starts the Google Play account, and which kind of account they use. The waits below use the published maximums or typical figures from the table above, so treat them as a planning buffer, not a promise.
| Scenario | How the weeks add up | Live in |
|---|---|---|
| A. Personal account, opened after the build | 6 weeks build + 2 weeks closed test (14 days) + up to 1 week production review | About 9 weeks |
| B. Organisation account, D-U-N-S requested after the build | 6 weeks build + up to about 4 weeks for D-U-N-S (30 days) + about 1 week for account checks and review | About 11 weeks |
| C. Organisation account, D-U-N-S requested in week 1 | D-U-N-S finishes by about week 5, while the build runs; submit in week 6 + about 1 week review | About 7 weeks |
Scenario C is the same app as B, launched roughly four weeks sooner, simply because the paperwork overlapped with the build. Scenario A looks quicker than B, but it needs 12 real testers to stay opted in for two weeks, and the app is listed under a personal name rather than the business. For most companies, scenario C is the one to plan for.
If you also want to know what the app will cost to keep running after launch, see the guide to yearly app maintenance costs.
Personal or organisation developer account?
This single choice changes your timeline more than any feature does, so decide it in week one.
| Question | Personal account | Organisation account |
|---|---|---|
| Extra step before launch | Google: 12 testers for 14 days, then a production review | D-U-N-S number for both Apple and Google |
| Name shown on the store | Your own name | Your registered company name |
| Who owns the account | One individual | The business, with team members added |
| Best for | Sole traders testing an idea | Registered businesses, clinics, institutes, restaurants with a company |
Whichever you choose, open the accounts yourself, in your own or your company's name, and invite the developer as a team member. An app published from a developer's account is hard to move later, and you will need it again for every update. The company's legal name and address must match the D-U-N-S record and the payments profile exactly; Google gives 28 days to fix a mismatch before it removes the account and its apps.
If you only need customers to order or book, and do not need store listing on day one, a web app can go live without any store review. The native app vs PWA guide explains when that is enough.
What to check in the contract before you sign
A quoted timeline is only as good as the conditions behind it. Before signing with any developer, freelancer or agency, ask for these in writing:
- A date per milestone, not one launch date. For example: first demo, test build, store submission. A single end date hides slippage until it is too late.
- What the clock excludes. Does the timeline include store approval, D-U-N-S and payment KYC, or stop at "build delivered"? Both are fair, but you need to know which.
- Your own deadlines. Good contracts list what you must supply (content, logins, feedback) and by when. If your photos arrive two weeks late, the launch moves two weeks; that is reasonable and should be stated.
- Rejection fixes. Are changes Apple or Google ask for during review covered by the price, or billed as extra work?
- How changes are handled. New features after sign-off should come with a written price and a new date before anyone starts them.
- Weekly demos on a real phone. Seeing progress every week is the cheapest early warning there is.
The guide on scoping a project and comparing proposals helps you write the feature list these milestones depend on, and fixed price vs hourly contracts explains how each pricing model handles changes.
Why app launches slip, and how to see it early
- The feature list keeps growing. Agency write-ups across the industry name mid-build additions as the most common cause of delay, because each one reopens design and testing. Keep a "version 2" list and park ideas there.
- Reviewers cannot get in. Apple says more than 40% of unresolved review issues fall under guideline 2.1, app completeness, which covers crashes, placeholder content and missing information. A frequent trigger is a login the reviewer cannot use, so give a working demo account and make sure OTP or location checks do not block it.
- Testers drop out. On a personal Play account the 14 days must be continuous with at least 12 testers opted in. Recruit a few more than 12 and remind them not to leave the test.
- Company details do not match. A spelling difference between your GST or incorporation papers, the D-U-N-S record and the store account can stall verification. Copy the exact legal name everywhere.
- Feedback is slow. If a demo waits a week for your comments, the project waits a week. Block 30 minutes after each weekly demo.
Warning signs worth acting on: demos skipped two weeks running, vague status updates without a build you can install, and a new developer on the project without notice. To sense-check the budget side of your plan, try the app development cost calculator.
Talk to Growmoon
Growmoon builds branded ready-made apps from $1,500 that can be live in 2–4 weeks for food and restaurant businesses, white-label apps in about 2–8 weeks, and custom apps when nothing ready-made fits. Ask us, as you would ask anyone, exactly which approval steps a quoted timeline includes. If a web app or a simple WhatsApp ordering flow would test your idea faster and cheaper, we will say so. See the ready-made food apps or how we run projects.
Questions people ask
How long does it take to build a simple app in 2026?
A branded ready-made app can be ready in about 2–4 weeks and a white-label app with changes in 2–8 weeks. A custom app usually takes several months; Clutch's guide puts it at 20–40 weeks.
How long does Apple take to approve an app?
Apple says that on average 90% of submissions are reviewed in under 24 hours. Rejections, often for missing demo logins or incomplete content, add a new round each time.
Why does Google Play need 12 testers?
Personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in continuously for 14 days before applying for production. Organisation accounts need a D-U-N-S number instead.
Can I launch faster without the app stores?
Yes. A progressive web app opens in the browser and needs no store review, so it can go live as soon as it is built and tested. You can add store apps later.
Should the developer open the store accounts for me?
It is safer to open them yourself in your company's name and add the developer as a team member, so you keep control of the app and its updates.
Sources
- Google Play Console Help: App testing requirements for new personal developer accounts
- Google Play Console Help: Required information to create a developer account (D-U-N-S)
- Apple Developer: App Review
- Apple Developer: D-U-N-S Number
- Android Developers Blog: Android developer verification rolling out to all developers (March 2026)
- Razorpay Docs: Payments FAQs (account activation)
- Clutch: How long does a mobile app development project take?
- LearnDash: Configure Google Play closed testing (production review time)
WhatsApp
