Hendeca Labs

How Long Does It Take to Build an MVP?

Realistic timelines for a first version of your product, from a one-week web app to a phone app in the App Store, and what makes the difference.

Izzy Young · Founder, Hendeca Labs

5 min read

When someone tells me they have an idea for an app, the second question after "how much?" is almost always "how long?"

The honest answer is shorter than most people expect, as long as the first version is the right size.

A focused MVP usually takes 1–3 weeks as a web app, and about 4–10 weeks as an iPhone or Android app that goes through the app stores. Most of the variation comes from how much the first version tries to do.

Here's where those numbers come from, what happens during that time, and how to get your first version out sooner.

1. What Is an MVP?

MVP stands for minimum viable product: the smallest version of your product that real people can use to solve a real problem.

The point of an MVP is to learn. You put something in front of customers and find out whether they use it, whether they'd pay for it, and what they wish it did, before you spend money building everything else.

That means an MVP is not a cheap, broken version of the final product. It does fewer things, but the things it does should work well.

A good MVP for a dog-walking business might let customers book a walk and pay. It doesn't need walker profiles, route maps, reviews, a loyalty scheme and a chat feature. Those can come later, once you know people book.

2. The Short Answer: How Long Does an MVP Take?

Here are typical timelines for the first version, by the kind of product.

Kind of MVP Typical timeline
Single-purpose web app or internal tool (built with Lovable) 1–2 weeks
Multi-page web app with sign-in and simple data 2–3 weeks
Simple iPhone, Android or cross-platform app About 4–6 weeks
Multi-screen phone app connected to a backend About 6–10 weeks
Apps with payments, several user roles or heavy integrations 10 weeks or more

These are build times once the scope is agreed. Planning beforehand and app store review afterwards add to the calendar, as described below.

If you already know you need a phone app, here's how I build mobile apps.

Phone apps take longer for a few reasons. They usually need a backend for accounts and data, they have to be tested on real devices, and Apple and Google both review every app before it goes live.

3. What Happens During Those Weeks?

Every project is different, but most follow the same shape.

Discovery (a few days to a week)

We agree on what the first version does and, just as importantly, what it doesn't. This ends with a written scope and a quote. It's the shortest phase and the one that saves the most time later.

Design (often overlaps with the build)

The main screens and how people move between them. For an MVP this is usually lighter than for a finished product: clear and usable beats elaborate.

Build

The bulk of the timeline. You should see working progress regularly, not a big reveal at the end. I share builds as I go, so you can try the product on your own phone or computer and steer it early.

Testing

Checking that everything works on different devices, screen sizes and browsers, and fixing what doesn't. For phone apps this includes real-device testing.

Launch

For a web app, launch can be the same day. For a phone app, Apple and Google review it first. Reviews often take a day or two, but a rejection means fixing the issue and submitting again, so it's wise to leave a buffer of a week before any launch date you announce.

4. What Makes an MVP Take Longer?

When a project runs long, it's usually one of these.

The scope keeps growing. "While we're at it, could it also…" is the most common reason projects slip. Each addition seems small, but together they can double a timeline.

Decisions wait. If every screen needs approval from several people, the build stops while it waits. One decision-maker with the authority to say yes keeps things moving.

Content arrives late. Text, images, prices, terms and privacy policies are often left until the end, and the launch waits for them.

Payments and accounts. Taking money and managing user accounts properly is real work, and on phones there are app store rules to follow. If your MVP can launch without payments, it will launch faster.

Integrations. Each outside system you connect to, such as a calendar, a CRM or accounting software, adds time. Some are quick. Others aren't.

App store review. Most apps are approved quickly. Apps that take payments, collect personal data or let people sign in get more scrutiny, and a rejection adds days.

5. How Can You Launch Sooner?

These are the things that make the biggest difference, roughly in order.

Cut the first version down to one job. Write down every feature you want, then ask of each one: would someone still use the product without this? If the answer is yes, it waits for version two.

Start with a web app. A web app works on every phone and computer, needs no app store approval, and can be updated instantly. Unless your idea needs something only a phone app can do, such as notifications, offline use or the camera, a web app is often the fastest way to learn whether people want it.

Use tools that are fast to build with. AI-assisted tools like Lovable can produce a working web app in days. They need someone experienced to scope, review and test the result, but for an MVP they can save weeks.

Choose cross-platform if you need both phones. One shared codebase for iPhone and Android is faster than building two separate native apps.

Have your content ready before the build starts. It costs nothing and removes one of the most common delays.

6. How Fast Is Too Fast?

It's possible to rush an MVP, and the cost shows up later.

The things worth taking time over, even in a first version, are the ones that are hard to fix afterwards: how user data is stored and protected, whether the app works on the phones your customers actually use, and whether the code can be built on once the MVP proves itself.

A first version that's quick to build but has to be thrown away and rebuilt from scratch isn't really faster. The goal is to build less, not to build carelessly.

7. A Final Thought: Launch Is the Start, Not the Finish

The best thing about an MVP is what happens after it launches. Real people use it, and you learn things no amount of planning would have told you.

Some of the features you were sure you needed turn out not to matter. Something you hadn't thought of turns out to be what people want most.

So the right question isn't only "how long until it's done?" It's "how soon can we start learning?" For most ideas, the answer is a matter of weeks.

You can see apps and products I've shipped. If you have an idea and want to know how quickly a first version could be in people's hands, I'd be happy to talk it through and give you a realistic timeline with your quote.