How long it takes to build an app depends mostly on how many real features the first version has, then on platforms, other systems and rules, and on how quickly you make decisions. As a worked example from my free MVP timeline calculator: a web app with sign-up, records, search and a dashboard, starting from an idea, comes out at about 9.5 weeks (8 to 12.5). A mobile app with booking, payments, chat, notifications and an admin panel comes out at about 18.5 weeks (15.5 to 24), including app store review. Those are the tool's model, not a promise; the rest of this post shows where the weeks go and how to move them.
I'm a design engineer: I design products and build them in production code, web apps in React and Next.js and iOS and Android apps in React Native or Flutter. My mobile app design and development work both start with the question this post answers.
Why I don't quote an average
Search this question and you'll find confident averages: "three to nine months", "four to six months for a medium app". Nearly all of them come from development companies' own blogs, they define "simple" and "complex" differently, and they rarely say what was counted. I don't repeat them. Instead, every duration below comes from one of two places, and I say which:
- Apple and Google, for store review and testing rules.
- My calculator's own model, which I can show you line by line. It assumes one senior designer and engineer working full time, with quick decisions on your side, and it's a planning guide, not a quote.
The app development timeline, phase by phase
The calculator splits a project into five phases: scope, design, build, testing and, for mobile, store review. They overlap, so they don't simply add up.
1. Scope
Scope turns an idea into a list of screens, states and integrations that everyone signs off. In the calculator, scoping takes 2 weeks when you start from an idea, 1.5 weeks for a redesign and half a week when designs are already done.
Longer: nobody owns the decisions, the feature list keeps growing, or you need data from a third party who replies slowly. Shorter: one decision maker, a written list of what's out of version one, and access to the systems you need in week one. My guide on how to scope an MVP walks through that list.
2. Design
Design covers the flows, every state of every screen and the design system: tokens and components named the same in Figma and in code. Each product type starts with its own foundation in the model (the shell, navigation, settings), and each feature adds design days and screens. The default web example above has about 15 screens to design; the mobile example has about 27.
Longer: many roles with different screens, right-to-left layouts, regulated data, or late changes to the flows. Shorter: existing designs (the model then counts only a quarter of the design work) or fewer features.
3. Build
Build is the largest phase. In the calculator it starts once design is about halfway, because the first flows are ready before the last ones. Platform changes the weight: the build work for each feature is multiplied by 1.25 for a mobile app and by 1.4 for web and mobile together. So building both doesn't double the time, but it isn't free.
Longer: integrations (each adds about half a design day and two and a half build days in the model), extra languages, payments, chat, wallets and anything with money or health data. Shorter: renting what you can (sign-in, payments, maps) and leaving the "nice on day one" features for version two.
4. Testing and launch
Testing in the model is at least a week, or about 18% of the build time if that's longer. Each extra language adds 8% to it, and regulation adds more: 20% for privacy law, 60% for health data and 80% for financial rules.
Longer: many devices, many languages, compliance checks. Shorter: testing each flow as it's built, not saving it all for the end.
5. App store review
Apple says App Review typically reviews at least 50% of submissions in under 24 hours and 90% in under 48 hours, and that incomplete submissions can be delayed or rejected (Apple, App Review). You can ask for an expedited review for a critical bug fix or an event you're tied to. External TestFlight testers can only get a build once the first one has been approved by App Review for TestFlight (Apple, TestFlight).
Google says some developer accounts and some apps get extended reviews, which can mean review times of up to seven days or longer in exceptional cases (Google Play Console Help). If your personal developer account was created after 13 November 2023, you must first run a closed test with at least 12 testers opted in for at least 14 days in a row (Google Play Console Help, testing requirements). Plan those two weeks into the schedule.
My calculator budgets 1.5 weeks of store review for every mobile plan, more than Apple's typical figure, which leaves room to fix and resubmit. My app store rejection checklist lists the design issues to fix before you submit.
Which features take the longest
These are the calculator's weeks per feature, design and build together, for one senior designer and engineer:
| Feature | Web app | Mobile app |
|---|---|---|
| Wallet or balance | 2.2 | 2.6 |
| AI assistant over your data | 1.8 | 2.1 |
| In-app chat | 1.7 | 2.0 |
| Dashboard with charts | 1.6 | 1.9 |
| Calendar or booking | 1.5 | 1.8 |
| Payments and subscriptions | 1.4 | 1.7 |
| Admin panel | 1.4 | 1.7 |
| Roles and permissions | 1.2 | 1.4 |
| Sign-up and login | 0.6 | 0.7 |
| Google or Apple sign-in | 0.4 | 0.5 |
The pattern is the point: anything that moves money, talks in real time or has many states costs weeks. Sign-in is cheap because it's mostly rented.
How long does it take to build an MVP?
The same model applies, with a smaller list. In the calculator, the mobile example above drops from 18.5 to 15 weeks when you leave social sign-in, notifications and chat for version two: 3.5 weeks sooner. Starting with finished designs takes it to 15 weeks too, by shrinking scope and design. Adding health data rules pushes it the other way, to 21.5 weeks (18.5 to 28).
A good test for each feature: what couldn't a user do on day one without it? If the answer is nothing important, it waits. The calculator marks the features that usually can (social sign-in, teams, chat, maps, invoices, notifications, AI generation, analytics and a content editor) and shows the weeks saved.
How to use the MVP timeline calculator
- Pick what you're building: web app, mobile app, web and mobile, marketplace, AI product or internal tool.
- Pick where you're starting: an idea, designs ready or a redesign. The earlier you are, the wider the range, because an idea has more unknowns. From an idea, the low end is 15% under the most likely figure and the high end 30% over.
- Tick the features, set integrations and languages, and choose any rules it must meet.
- Read the timeline phase by phase, the screens to design, the three slowest features and the lean version.
It runs in your browser with no sign-up. Copy link saves your choices in the address, and you can copy the plan, download it as Markdown or print it.
Alternatives for estimating your timeline
- A spreadsheet of your own: list every screen and state, estimate each, add a third for testing. Slower, but you'll learn your product.
- Your developer's estimate after a scope: the only number that should go in a contract.
- Published averages: useful for a first sense of scale, but check who wrote them and what they counted.
My calculator sits between the first two. It's quick and explains itself, but it can't see your integrations' documentation or your team's speed.
Frequently asked questions
How long does it take to build an app?
It depends on features, platforms and rules. In my calculator, a web app with four core features takes about 9.5 weeks from an idea, and a mobile app with booking, payments and chat about 18.5 weeks, including store review.
How long does it take to build an MVP?
As long as its smallest useful feature list takes. Leaving optional features for version two saved 3.5 weeks in the mobile example above. Try your own list in the calculator.
How long does App Store review take?
Apple says at least 50% of submissions are reviewed in under 24 hours and 90% in under 48 hours. Incomplete submissions take longer.
How long does Google Play review take?
Google says certain apps and accounts get extended reviews of up to seven days or longer in exceptional cases. New personal accounts also need a 14 day closed test with 12 testers first.
Does building for iOS and Android double the time?
No, with one codebase in React Native or Flutter. In my calculator, building a feature for mobile weighs 1.25 times the web build, and web and mobile together 1.4 times.
Can you design and build my app?
Yes. I design the product and build it, web apps in React and Next.js and mobile apps in React Native or Flutter, with a design system so the code matches the design.
Sources and method
I read every source on 1 November 2026. Durations that aren't from Apple or Google come from the logic of my MVP timeline calculator, run on the examples named in the text. I give no industry averages, because the ones I found came from development companies' blogs.
- Apple, App Review, date read 1 November 2026: developer.apple.com
- Apple, TestFlight, date read 1 November 2026: developer.apple.com
- Google, Play Console Help, prepare your app for review, date read 1 November 2026: support.google.com
- Google, Play Console Help, testing requirements for new personal developer accounts, date read 1 November 2026: support.google.com
If you're planning an app and want a timeline you can hold someone to, book a free 30 minute intro call. After it, you get a written scope and one fixed quote.
Tags: Mobile apps, MVP, Startups, App Store, Free tools



