How long does it take to build an app?
How long does it take to build an app?
About five weeks for the smallest useful product, about ten weeks for a typical MVP and about 13 weeks for the same product as an iOS and Android app. A marketplace on the web and in both app stores takes about 17 weeks with three developers. Those are the timelines our calculators give, counted from kick-off to the first real users.
The calculators count the work in developer-weeks, design and testing included, divide it across a team, and add a week for the written scope at the start and the launch at the end. A typical MVP is about 18 developer-weeks: two developers, nine weeks of building, ten weeks in all.
How long do different kinds of app take to build?
These are the timelines our MVP cost calculator and app development cost calculator give for common shapes of product, each on a proven design system, with the team size and the fixed-scope price range beside it. A bigger build gets a bigger team, which is why the calendar grows more slowly than the work. For the money side, see how much an MVP costs.
- The smallest useful web product — one kind of user, sign-in, hosting and the core screens: about 5 weeks with one developer ($12k–$16k).
- A simple iOS and Android app with one kind of user, on an API you already have: about 5 weeks with one developer; about 6 if the backend has to be built too ($12k–$16k).
- A simple internal web tool with an admin panel and email notifications: about 10 weeks with one developer ($12k–$16k).
- A typical MVP — a web app for customers and staff with an admin panel, payments, notifications and file uploads, connected to one or two other systems: about 10 weeks with two developers ($23k–$34k).
- The same product as an iOS and Android app: about 13 weeks with two developers ($29k–$42k).
- The same product on the web and in both app stores: about 12 weeks with three developers ($40k–$59k).
- An internal tool that replaces spreadsheets — staff and managers, an admin panel, dashboards and reports, file uploads and three or more systems to connect: about 11 weeks with two developers ($24k–$36k).
- A field app for staff on the road — iOS and Android, offline use, photos, push notifications, maps, a web admin panel and one outside system: about 14 weeks with two developers ($32k–$47k).
- A marketplace on the web — buyers, sellers and admins, with payments, search, uploads, notifications and chat: about 14 weeks with two developers ($33k–$49k).
- The same marketplace on the web and in both app stores: about 17 weeks with three developers ($58k–$85k).
What are the phases of building an app?
Every product goes through the same four phases. In our calculators the scope and the launch together take about a week whatever the size; the build is the part that grows.
- Scope. One call, no slides: what breaks today, who it hurts and what the product must do. Then a written plan with a price and a date. If we don't believe it can be done for that, we say so before you sign anything.
- Design. On a proven design system, design happens inside each slice rather than as a separate phase up front. A custom brand design is extra work: in the calculator it takes the typical MVP from about ten weeks to about 12.
- Build in two-week slices. The first slice is on a live URL in week one, and there is a clickable demo every Friday. The typical MVP is about nine weeks of building with two developers — four or five slices, each ending in something you can click.
- Launch. Real users go in, and a fixed-scope build includes 30 days of fixes once they do. For a mobile app, Apple and Google both review it before it goes live, and a rejection means a fix and a new submission, so leave room for that in the plan.
What makes an app take longer to build?
Starting from the typical MVP — about ten weeks with two developers — these are the answers that stretch the calendar most in our calculators:
- More platforms. The same product as an iOS and Android app takes about 13 weeks. On the web and in both app stores it is about 12 weeks, but only because the calculator puts three developers on it instead of two: the work itself is about three-quarters larger.
- Outside systems. With three or more integrations — a CRM, an accounting tool, a bank, a carrier — it takes about 12 weeks. Their documentation, test environments and support are out of your control, so they are the hardest part of any timeline to predict.
- Sensitive data. Health, money or children's data mean more security work, reviews and testing: about 12 weeks.
- Heavier features. Chat or live updates, bookings and calendars, or AI features each take it to about 12 weeks. On the iOS and Android version, working offline or talking to Bluetooth or NFC hardware takes it from about 13 weeks to about 15.
- A custom brand design instead of a proven design system: about 12 weeks.
What delays an app that no estimate can see?
Some delays come from outside the code, and no calculator counts them. These are the ones to plan around:
- Slow answers. A slice that waits a week for a decision is a slice that isn't moving. Name one person on your side who can say yes, and have them at the Friday demo.
- Scope that grows without being re-scoped. Changing your mind early is cheap; adding features quietly in the last month is how dates slip.
- Accounts and approvals. An Apple developer account, a Google Play account, your payment provider's checks on your business and access to the systems we connect to all take time on your side. Start them in week one.
- Content and legal texts. Product copy, prices, terms of use and a privacy policy are yours to write or approve. A finished screen full of placeholder text isn't ready for real users.
How can you build an app faster without cutting corners?
Cut scope, not quality. Each of these shortens the calendar in our calculators:
- Launch on the web first. The typical MVP on the web and in both stores takes about 12 weeks with three developers; on the web alone it is about ten weeks with two, and the calculator says it saves about $20k. Add the apps in a second release.
- Build on an API you already have. The typical iOS and Android app takes about 12 weeks instead of 13 when its backend already exists.
- Leave the heaviest feature for release two. A web marketplace without chat takes about 13 weeks instead of 14 and costs about $5k less.
- Connect only what you must. The typical MVP with no integrations takes about nine weeks; data from other systems can be imported by hand until the connection is worth building.
- Start in one store only if you must. From one codebase the second store costs little: one store takes the typical app from about 13 weeks to about 12.
- Start from a proven design system and brand it later.
How does team size change the timeline?
In our calculators the team grows with the work: one developer for up to about ten developer-weeks, two for up to 30, three for up to 60 and four beyond that. That is why the smallest products and a simple internal tool take five to ten weeks with one person, and why most of the MVPs above land between ten and 14 weeks with two.
A bigger team lets a bigger product arrive in about the same time; it rarely makes the same product arrive much sooner. The typical MVP on the web is about 18 developer-weeks: ten calendar weeks with two developers. Built for the web and both app stores it is about 31 developer-weeks, three-quarters more work, and the calculator puts three developers on it to land in about 12 weeks.
When does adding developers stop helping?
Sooner than most people expect. Brooks's law, from Fred Brooks's 1975 book The Mythical Man-Month, says that adding people to a late software project makes it later. New people need the existing team's time before they are useful, and the lines of communication grow faster than the team: two people have one, four have six, six have fifteen.
Some work also can't be split. The payment flow has to exist before the screens that use it, and the data model has to settle before reports are built on it. Past a point, extra developers wait on each other instead of building.
Our calculators never put more than four developers on one product. The largest build we priced for this article — a marketplace on the web and both app stores with a custom design, sensitive data and three or more integrations — is about 65 developer-weeks: four developers, about 18 weeks. The same marketplace with only the custom design is about 51 developer-weeks with three developers, and also about 18 weeks. The fourth developer absorbs the extra work; they don't buy an earlier date.
How do you hold a development team to a date?
Write it down. A fixed-scope build gives you one price, one date and one deliverable, agreed in a written scope before work starts. Bigger changes are re-scoped in writing before any work on them starts, so a new date is a decision you make, not a surprise you discover.
If you expect the scope to move once real users try the product, a dedicated team that plans in two-week slices fits better — the trade-offs are in fixed price, time and materials or a dedicated team. Either way, a clear software project brief is the quickest route to a date you can trust.
How long does it take to build an MVP?
Our typical MVP reaches its first real users in about ten weeks with two developers: a web app for customers and staff with an admin panel, payments, notifications and file uploads, connected to one or two other systems. Smaller products take five to ten weeks with one developer. See how we run MVP development.
How long does it take to build an iOS and Android app?
The typical MVP as an iOS and Android app takes about 13 weeks with two developers. A simple app with one kind of user, on an API you already have, takes about five weeks with one developer, or about six if the backend is built too. We build both platforms from one codebase with Flutter, so they launch together — see mobile app development.
Can an app be built in a month?
Only the smallest. In our calculators the smallest useful web product — one kind of user, sign-in, hosting and the core screens — takes about five weeks with one developer, and so does a simple app on an existing API. Anything with payments, an admin panel or several kinds of user takes longer; if someone promises it in four weeks, ask what they have left out.
Does adding more developers make an app faster?
Up to a point. A bigger team lets a bigger product land in about the same time, but the same product rarely arrives much sooner with more people: newcomers cost the team time, and some work has to happen in order. Our calculators never put more than four developers on one product.
How do I get a firm timeline for my app?
A few paragraphs are enough: what the app should do, who uses it and what happens today instead. Send us the brief and we reply within one working day; you get a written scope with what we'd build first, what it costs and the date it ships.