How Long Does It Take to Build an App?

Six to ten weeks. That’s a real window for a focused first version: one platform, one core flow, one or two integrations, launched to real users. Not a marketing number, just what the phases add up to when nothing pads them.

Here’s where those weeks go.

The five phases

1. Scope — a few days to a week. Agree on the one job v1 does, write the feature list, and write the “not in v1” list. Teams that skip this week routinely lose a month later.
2. Design the flow — 1–2 weeks. The handful of screens on the core journey. Not a brand system, not a component library. The path a user takes, made obvious.
3. Build — 3–6 weeks. Front end, back end, and whichever integration made the cut. Most of the calendar lives here, which is why the feature list decides the timeline.
4. Test and harden — overlapping, about a week’s worth. Testing as the build goes, not a phase stapled to the end.
5. Launch — days. Ship to real users, watch the first sessions, fix what actually breaks rather than what you feared would.

A fuller product with more platforms, integrations, and reporting scales up from this baseline. That trade is covered in MVP vs full product.

What turns six weeks into six months

Not slow engineers. These:

• “While we’re at it.” Every mid-build addition carries a design, build, and test tail. Three harmless-sounding additions can eat a month.
• Unanswered questions. A build waiting three days for one decision loses three days, invisibly. Multiply by ten decisions.
• Integrations assumed to be easy. Payment gateways and government APIs come with sandbox access, approval steps, and edge cases nobody demos. Budget calendar for them, not just money.
• Three platforms at once. iOS, Android, and web triple the build-and-test surface before one user has confirmed the idea. Pick one; the reasoning is in web vs mobile first.

Keeping the calendar honest

Freeze the v1 scope and keep a visible “later” list. Name one decider who answers within a day. Defer any integration you can run manually for the first month. None of this trades quality for speed; it trades scope for speed, which is the only version of that trade that works.

Timeline questions are scope questions wearing a disguise, and scope is yours to set. If you want the phases mapped against your actual idea, that’s a short conversation — it’s how every MVP we build starts.