Your timeline is wrong. Here's why.

Process · 6 min read

A client once told me, four weeks into the design process, that he'd expected to have a working app by now. Not a prototype. Not a design. A working, downloadable, usable app. In four weeks. From a standing start.

He wasn't being unreasonable. He'd read marketing material that implied it was possible. He'd seen ads promising rapid delivery. And nobody had sat him down and explained that "idea to app" is a pipeline with distinct phases, not a single sprint. That conversation should have happened before a single dollar was spent.

Design and development are different jobs

This is the thing most first-time founders don't know, and it causes more frustration than almost anything else. Design is when you figure out what you're building. Development is when you build it. They're sequential. You do one, then the other. Trying to do them simultaneously is like building a house while the architect is still drawing the plans. It doesn't save time. It creates chaos.

The design phase includes research, user flows, wireframes, visual design, and prototyping. For a typical app, that takes four to six weeks. The development phase includes coding, testing, iteration, and deployment. For a typical MVP, that takes another two to four months. So when someone says "six weeks," they might mean six weeks of design. The build comes after.

I've learned to be explicit about this from the very first conversation. "You'll have a prototype you can tap through on your phone in five weeks. A built app will take longer because development is a separate phase with a separate timeline and a separate budget." Clear. Honest. No room for misinterpretation.

Where the time actually goes

People imagine that most of the time goes into coding. It doesn't. A significant chunk goes into decisions. What does this button do? What happens when the list is empty? What error message should appear when the network drops? Every screen has dozens of these micro-decisions, and each one needs to be answered before or during development.

Then there's the back-and-forth. The developer builds something. You review it. Something doesn't feel right. They adjust it. You review again. That cycle is normal and necessary, but it takes time. Most projects need at least two feedback rounds, sometimes three. Each round adds a week or two.

And then there's testing. Real testing. Not just "I tapped through it and it worked." Testing on different devices. Testing with real data. Testing edge cases. Testing what happens when someone does the thing you never expected them to do. That's where the bugs live, and fixing them takes time.

How to set a realistic timeline

Start by separating the phases in your head. Design: five weeks. Developer selection and quoting: two to three weeks. Development: two to four months depending on complexity. Testing and refinement: two to four weeks. Total: four to six months from "let's go" to "it's in the App Store."

That sounds long. But compare it to what happens when you skip the design and go straight to a developer. The build takes longer because there's no spec. The rework costs more because decisions were made without research. And the thing that ships is usually worse because nobody thought about the user experience until it was too late to change it cheaply.

A clear timeline isn't a barrier. It's a plan. And a plan you can trust is worth more than a promise that sounds too good to be true. Because it usually is.

Sources
CHAOS Report (Standish Group) - Only 29% of software projects are completed on time and on budget.
UX Design Process (Nielsen Norman Group) - Why discovery and design must precede development.

Related blog posts:

The real cost of designing and building an app →

How to prepare for your first app design project →

A prototype is not an MVP →