How long does it take to build an app? A realistic timeline

Three to six months from kick-off to both app stores for a first version, as of October 2026. Each phase, what delays apps, and how to go faster.

By Sohail Hussain21 November 20265 min read

A first version of a business app takes three to six months from kick-off to live in both the App Store and Google Play, as of October 2026. A simple app with accounts, a handful of screens and a straightforward backend takes ten to fourteen weeks. An app with payments, notifications, maps and an admin panel takes four to six months. Apps with real-time features, offline sync or several integrations take six months or more. The screens are rarely what sets the pace; the backend, the integrations and the speed of decisions are.

How long does each phase take?

PhaseTypical lengthWhat happens
Discovery and scope1 to 3 weeksBrief, core flows, feature list split into launch and later, estimate
Design4 to 6 weeksUser flows, every screen for both platforms, a clickable prototype, approval
Build8 to 16 weeksApp, backend and admin panel in parallel, with a test build every week or two
Testing and beta2 to 4 weeksYour team uses real builds through TestFlight and Google Play testing tracks
Store review and launch1 to 2 weeksListings, submission, usually at least one rejection to fix, release

Phases overlap. Backend work starts while the last screens are being designed, and beta testing begins before the final features are finished, which is why the total is shorter than the sum of the columns.

In hours, a medium app with accounts, payments, push, a backend and an admin panel is usually 800 to 1,800 hours of work, as covered in how much a mobile app costs. A small team of a designer, two developers and part of a project manager's week gets through that in roughly three to five months.

Our mobile app development projects follow this sequence, with a build on your own phone every week or two from the middle of the build phase so there are no surprises at the end.

How long do simple, mid and complex apps take?

TypeExampleKick-off to both stores
SimpleAccounts, five to ten screens, one user type, a straightforward backend10 to 14 weeks
MidPayments or subscriptions, push, maps or camera, two user types, an admin panel4 to 6 months
ComplexReal-time features, offline sync, integrations with existing systems, several roles6 months and up

Two features move an app up a row on their own. Offline sync adds 100 to 250 hours because every screen needs a plan for what happens without a connection and when two people change the same record; offline-first apps explains why. In-app purchases and subscriptions add 60 to 120 hours, much of it testing purchase, renewal, cancellation and restore flows on both stores.

What makes app projects run late?

Decisions. Every screen needs approving, every flow has edge cases someone must rule on. A project with one decision-maker who replies within two working days runs to plan. A committee that meets weekly adds weeks.

The backend and integrations. Connecting to an existing ERP, CRM or booking system is where estimates go wrong, because the other system's API is often undocumented, slow or missing what you need. Ask for access and documentation in week one.

Store accounts. Apple's organisation enrolment needs a D-U-N-S number and a verification check, and the Apple Developer Program can take days to a few weeks to approve a new company. Google Play requires new personal developer accounts to run a closed test with at least 12 testers for 14 continuous days before an app can go to production, according to Google's testing requirements. An organisation account avoids that test, but has its own verification. Open both accounts in your company's name in the first week of the project.

Store review. Apple says it reviews at least half of submissions within 24 hours and 90 percent within 48, on its App Review page. The delay is rejections: a missing demo account, a privacy declaration that does not match the app, or a payment flow that breaks the rules. Budget a week, and read App Store rejection reasons before you submit.

Content. Product data, help text, legal pages, store screenshots and descriptions. They are always someone's job and always late.

Scope that grows. "While we're at it" is the most expensive phrase in app development. Write new ideas on a list for version two.

Can you build an app faster?

Yes, by cutting work, not by adding people. More developers on a small app add coordination, not speed.

  • Cut the first version to one core flow. The thing your users must do, working well, on both stores. Everything else waits for evidence it is needed.
  • Use an existing backend. If your website or system already has an API, the app becomes a client of it and the build shrinks substantially.
  • Launch one platform first. If your users are overwhelmingly on Android or on iPhone, ship there and add the other a few weeks later. With a cross-platform codebase the second platform is a fraction of the first.
  • Decide fast. Name one approver and agree a reply time.

Some things are not worth rushing. Skipping the beta to hit a date usually means launching with bugs your own team would have found, and the first store reviews are written by the people who hit them.

Our project timeline calculator lays out the phases against a launch date, and the app cost calculator shows how each feature affects the budget, which moves in step with the timeline.

What happens after launch?

The first four to six weeks are for fixes and small changes based on how real users behave. After that, apps settle into a cycle of updates: Apple releases a new iOS each September, Google releases Android versions and raises its target API requirement each year, and libraries move on. Each needs testing and often changes. App maintenance: what it involves and costs covers the yearly calendar and the budget, typically 15 to 25 percent of the build cost a year.

If you are still planning, a written mobile app brief is the fastest way to get a timeline you can trust, because every developer quotes the same app. The mobile app development guide covers the rest of the decisions in order.

Was this guide useful?

Questions

Frequently asked.

Can an app be built in a month?

A prototype can, and so can a very small app with a few screens on an existing backend. A first version with accounts, a new backend, an admin panel and both store launches cannot be done well in a month. Design, review cycles and store setup alone take several weeks, however many developers you add.

Does building for both iOS and Android take twice as long?

Not with a cross-platform framework such as React Native or Flutter. One codebase serves both, and the second platform adds testing, platform-specific fixes and a second store submission, usually a few weeks rather than double. Two separate native apps do take close to twice the effort, though the two teams can work in parallel.

How long do app updates take after launch?

A small fix can be built, tested and through review in a few days. A new feature follows the same cycle as the original build at a smaller scale: a week or two of design, two to six weeks of development, then testing and review. Small JavaScript fixes in React Native apps can also ship over the air without a store review.

Sohail Hussain

Founder, MSH Technologies

Sohail has designed and built websites, web apps and AI products for over 12 years, for clients from Singapore-based industrial groups to early-stage SaaS startups. He writes about what actually worked.

Keep reading

Related guides.

All posts

Your next move

Like what you see? Tell us about it.

A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.

India · Working with clients worldwide

Sohail, Founder, replies within 1 working day (Mon–Sat, IST). Free and no obligation.