How Long Does It Take to Build and Launch a Mobile App?

A focused first version (an MVP) of a mobile app usually takes about 2 to 4 months to build. A larger custom app takes 4 to 9 months or more. Add one to three weeks at the end for app store review and, on Google Play, a testing requirement that can catch new developers out.

These are benchmarks, not promises. Almost every published figure comes from agencies, including us, and agencies publish timelines to attract clients. We have said where each number comes from so you can weigh it.

How long does an app take, by type?

The ranges below come from agency breakdowns summarised in our research (Glance and MobiLoud among them). The differences mostly come from how each agency defines scope.

| Stage or app type | Typical time |

|---|---|

| Basic prototype | 2 to 6 weeks |

| MVP (first usable version) | 2 to 4 months |

| Standard custom app | 4 to 9 months |

| Existing website converted into an app | About 4 to 8 weeks (one source only) |

Agency estimates for an MVP run from about 6 weeks to 6 months. A range that wide tells you the number depends far more on what you ask for than on who builds it.

What does the 2026 benchmark say?

The most useful single data point we found is a 2026 benchmark by Wavect of 30 real MVP builds. It measured calendar time from signed kickoff to first live release.

• The median was 12 weeks.

• The most common band was 10 to 14 weeks.

• Mobile and web-plus-mobile builds in that sample took 12 to 26 weeks.

That is a sample of 30 projects from one source, so treat it as a sensible midpoint rather than a rule. It does match the simpler advice we give small businesses: plan for about 3 months for a focused app.

Where does the time actually go?

Building the screens is only one part. Agency breakdowns put the surrounding work at roughly this:

• **Discovery and planning:** 2 to 4 weeks. This is where you decide what the app must do and what can wait.

• **Wireframes and user flows:** 1 to 2 weeks for a simple MVP.

• **Design and development:** the bulk of the project, and the part that stretches most with scope.

• **Testing:** at least 2 to 3 weeks. Cutting this is how apps launch with bugs that users find first.

• **Store submission and review:** days to a few weeks, covered below.

People often ask only about development. In practice the planning, testing and release steps are a large share of the calendar.

What makes an app take longer?

The Wavect benchmark compared slow builds with fast ones. The slow ones differed in integrations, mobile store review, unclear decision ownership, data access, compliance questions and depth of quality testing. Notice that most of these are not coding problems.

In plain terms, these push a project toward the upper end:

• Payments, because they add security, testing and store rules.

• AI features, which add design, data and testing work.

• Integrations with other systems, especially where you do not yet have access to the data.

• Slow or split approvals. One guide we reviewed says slow client approvals delay a project more than slow development does.

• Building two separate native apps, one for iOS and one for Android.

Adding a second developer does not halve the time either. One source puts the saving at about 30 to 40 percent, because people need to coordinate.

Is a cross-platform app faster?

Usually, yes. Tools such as React Native and Flutter let one codebase serve both Android and iOS. Our research found this is faster than building separate native apps for each platform.

Native can still be the right choice when an app depends heavily on device-specific features. For most small business apps, such as bookings, orders, simple accounts and notifications, one cross-platform codebase is the sensible starting point. We build Android, iOS and cross-platform apps, and which one fits depends on what the app needs to do.

How long does Apple take to review an app?

Usually a day or less, but plan for longer on the first submission. Apple's App Review page says that on average 90% of submissions are reviewed in less than 24 hours. That is an average, not a guarantee. Third-party tracking in 2026 shows roughly 6 to 14 hours in the queue plus about an hour in review.

Secondary sources say that apps in health, finance or children's categories, and first submissions from new developer accounts, can take several days to two weeks. We have not verified that against Apple directly, so build slack into your launch date.

What is the Google Play testing requirement?

This is the step that surprises most first-time publishers. According to Google's Play Console help page, a new personal developer account must run a closed test with at least 12 testers, each opted in continuously for at least 14 days. Only then can you apply for production access.

A few details matter:

• The rule applies to personal accounts created after 13 November 2023. Some secondary sources, including Android Authority's coverage, give a slightly different cutoff, so check your own account's creation date.

• One guide says organization accounts are exempt. Confirm this against Google's current wording before relying on it.

• If a tester drops out, the 14-day clock can reset. Allow about three weeks for this step.

The practical lesson is to start this early, not at the end.

How can a small business shorten the timeline?

Most delays are decisions you control. These four changes help most:

1. **Cut features from version 1.** Launch with the one thing users need most, then add the rest once real people are using it.

2. **Use one cross-platform codebase** unless you have a clear reason for native apps.

3. **Name one person who approves decisions.** A committee reviewing every screen is a common cause of slow projects.

4. **Register your Google Play developer account early.** That way the testing clock can run alongside development instead of after it. Registering as an organization may avoid the tester requirement, so check the current rules first.

If you already have a website, you may be able to reuse its content and structure. One source puts converting an existing website into an app at about 4 to 8 weeks, though it is a single source and depends on the app.

What should I plan for realistically?

For a small business with a focused first version, we would plan like this:

• A focused MVP: about 3 months from kickoff.

• A feature-heavy app, or one with payments, AI features or several integrations: 6 months or more.

• Store release and the Google Play testing step: add 1 to 3 weeks on top.

We found no India-specific timeline data, so these figures come from general industry sources. Your own timeline will depend mostly on scope, how quickly you give feedback and how ready your content and data are.

We build and publish our own apps on Google Play, including MapSeal, a GPS map camera, and Recora, a screen recorder. That is why we put so much weight on testing and store release when we plan a client project. If you want a realistic estimate for your idea, tell us what the first version must do and we will quote it privately.

Frequently asked questions

**How long does it take to build a simple mobile app?**

A simple MVP usually takes about 2 to 4 months, and a 2026 benchmark of 30 builds found a median of 12 weeks to first live release. Add one to three weeks for store review and testing requirements.

**Is it faster to build an app for Android or iOS?**

Building one cross-platform app with a tool such as React Native or Flutter is generally faster than building separate native Android and iOS apps. The platform matters less than the scope of features you ask for.

**How long does app store approval take?**

Apple says that on average 90% of submissions are reviewed in less than 24 hours, though first submissions and sensitive categories can take days to two weeks. Google Play can add about three weeks if your account must complete the closed testing requirement.

**Can I speed up my app project?**

Yes. Reduce the features in version 1, use one cross-platform codebase, have a single person approve decisions and register your Google Play account early. Slow approvals often cost more time than slow development.

**Why do agencies give such different timelines?**

They define scope differently, and the figures are published to win business. Ask any agency exactly what is included, such as design, testing and store release, before you compare timelines.

Sources

• https://wavect.io/blog/mvp-timeline-benchmark-2026/

• https://thisisglance.com/learning-centre/how-long-does-it-take-to-build-a-mobile-app-mvp

• https://www.mobiloud.com/blog/mobile-app-development-timeline

• https://support.google.com/googleplay/android-developer/answer/14151465

• https://www.choicely.com/tutorials/how-long-does-app-review-take

• https://androidauthority.com/google-play-app-testing-requirement-3510580