How long does it take to build an app? Real weeks, phase by phase

How long does it take to build an app? The short answer by app type

A focused business app takes 6–10 weeks; an app with several user types, live tracking or payments between users takes 12 weeks or more. The honest answer to “how long does it take to build an app” is a range, because two apps with the same name can differ tenfold in work. A “booking app” for one salon is a different job from a “booking app” that lists 500 salons with their own logins and payouts.

The biggest single driver of how long does it take to build an app is the number of distinct user types. Each one, whether customer, staff, vendor, driver or admin, brings its own screens, permissions, notifications and edge cases. A second driver is anything real-time: live location, chat, and order status that must update on several phones at once. A third is integrations with outside systems such as payment gateways, ERP or accounting software, maps and SMS or WhatsApp providers.

Below is how we usually think about it when a client asks how long does it take to build an app of their type. These are typical ranges for a clear scope built in Flutter or React Native, including store launch. Your quote replaces the range with a week-by-week plan.

• Information or catalogue app (content, enquiry, WhatsApp button): 4–6 weeks
• Business app with login, bookings or orders and an admin panel: 6–10 weeks
• Ecommerce app with UPI/card checkout and order tracking: 8–12 weeks
• Two-sided marketplace or delivery app (customer, vendor, rider, admin): 12–20 weeks, usually in phases
• Complex platforms with heavy real-time features: planned as MVP plus releases

For a view of the money side of the same ranges, see app banane me kitna kharcha, which answers the cost question in Hinglish.

What happens in each week of an app build?

An app build moves through five phases: scope, design, build, testing, and store launch, with testing overlapping the build. Knowing what each phase produces helps you judge any answer to how long does it take to build an app, and whether a schedule is realistic or padded.

Scope (days 1–5). We turn your idea into a feature list, user roles and a rough screen map. The output is the itemised quote and a week plan. Scope is where most time is saved later, because every unclear feature becomes a question in week five.

Design (week 1–2). Screen flows and key screens in your brand colours. You approve how the app looks and moves before code is written. For simple apps we design and build in overlapping steps; for consumer apps we finish design first.

Build (weeks 2–7). One developer works on the app screens, another on the backend and admin panel, and the third runs the schedule, your feedback and testing. You get test builds on your phone from roughly the midpoint, not only at the end.

Testing (weeks 6–8). We test on a spread of Android phones, including budget models, and on iPhones. You test the real flows: sign up, book, pay, cancel. Fixes happen in short cycles.

Launch (last 1–2 weeks). Store listings, screenshots, privacy forms, review and release. This phase has waiting time you cannot code away, which is why it gets its own section below.

How long does Play Store and App Store review take?

Apple says that on average 90% of submissions are reviewed in less than 24 hours; Google says some reviews can take up to seven days or longer in exceptional cases. Both statements come from their own developer documentation, and both belong in any honest answer to how long does it take to build an app and get it live.

On the Apple side, the App Review page also explains that you can request an expedited review for a critical bug fix or an event-linked release. It is a request, not a right, so we never plan a launch around it.

On the Google side, Play Console Help notes that for certain developer accounts Google takes more time to review an app thoroughly. New accounts and apps in sensitive categories such as finance, health or apps requesting location in the background often see the longer end.

A rejection resets the clock. The most common causes we plan around are missing demo login details for the reviewer, a privacy policy that does not match what the app collects, permissions requested without a clear reason, and on Apple, an app that is little more than a website. We prepare reviewer notes and a demo account in advance so the first submission has the best chance of passing.

• Plan at least a week between “code complete” and your public launch date
• Never announce a launch date before both stores have approved the build
• Submit iOS and Android together; do not wait for one before starting the other

Why a new Play Console account can add two weeks

Google Play requires personal developer accounts created after 13 November 2023 to run a closed test with at least 12 testers, opted in continuously for at least 14 days, before the app can go to production. That rule, published in Play Console Help, surprises many first-time app owners who thought they knew how long does it take to build an app.

If you register a personal account on the day the app is ready, you are looking at a minimum of two more weeks before public release, plus review. The fix is simple: decide early. Businesses usually register an organisation account instead, which needs business verification details, and we guide you through it in week one so it is ready long before the build is.

Apple has its own paperwork. Its enrolment page says organisations need a D-U-N-S Number, must be a legal entity that can enter contracts, and need a working public website on the organisation’s domain. The membership costs US$99 a year; Google Play’s registration is a one-time US$25. Getting a D-U-N-S Number can take time if your company details are not already listed, so this is another week-one task.

Both accounts stay in your business’s name. We are added as users with the permissions needed to upload builds, which also means you can change developers later without moving the app. If your company does not yet have a website that meets Apple’s requirement, a simple site from ₹10,000 solves that and can be ready in 1–2 weeks.

What delays an app build, and how long does it take to build an app when things slip?

Most app delays come from late decisions and missing inputs, not from slow coding. When we look back at schedules that slipped, the pattern is consistent across app types.

The first cause is scope that keeps growing mid-build: “can we also add a wallet?” in week five. Each new feature is reasonable on its own, but together they push launch by weeks. We handle this by listing any addition as a separate line with its own price and week impact, and you choose whether it goes into version one or version two.

The second is waiting on third parties. Payment gateway onboarding needs your business documents and approval; SMS templates need DLT registration in India; WhatsApp Business API needs Meta verification. None of these is technically hard, but each has its own queue. We start them in week one.

The third is content: product photos, prices, descriptions, terms and privacy text. An app with an empty catalogue cannot be tested properly or approved by a store reviewer.

The fourth is slow feedback on test builds. If a build waits a week for comments, the schedule moves a week. Short WhatsApp voice notes are perfectly fine; what matters is that someone on your side tests within two days.

How long does it take to build an app with Flutter or React Native vs two native apps?

One cross-platform codebase usually ships both Android and iOS in roughly the time native development needs for one platform. With Flutter or React Native, every screen, form rule and API call is written once. Separate native apps in Kotlin and Swift mean doing most of that twice, or running two developers side by side and keeping them in step.

This is why our 6–10 week answer to how long does it take to build an app covers both stores. The platform-specific part of a cross-platform build is small: permissions text, push notification certificates, a few screens that should behave the iOS way, and two sets of store listings.

There are exceptions. Apps built around AR, heavy 3D, advanced camera processing or unusual Bluetooth hardware can need native code, and some need fully native development. If your idea falls there, we will say so at scope stage; the detailed trade-off lives on our native vs hybrid app page.

Another timing question is which store to launch first. Launching Android alone first is sometimes suggested to save time, but with one codebase the saving is mostly the iOS review and listing work, a few days at most. It can still make sense for budget or audience reasons; Android or iOS first covers that decision.

Finally, a progressive web app can go live in less time than a store app because there is no review, but it has limits on iPhone. If speed to market beats app-store presence, read that comparison before deciding.

How long does it take to build an app like a marketplace, delivery or taxi platform?

A two- or three-sided platform typically takes 12–20 weeks for a sensible first release, and it should launch in phases rather than all at once. When people ask how long does it take to build an app “like Swiggy” or “like Ola”, they are asking about products built over years by large teams. The useful version of how long does it take to build an app here is: how long does a first release for your city or niche take?

Each side of a marketplace is effectively its own app. Customers browse, order and pay; vendors manage menus, stock and orders; riders or drivers accept jobs and share live location; admins handle payouts, disputes and commissions. Real-time order status across all these phones is where most of the complexity sits.

A phased plan might look like this. Phase one launches the customer app and a simple vendor web panel, with your own staff handling delivery. Phase two adds the rider app with live tracking. Phase three adds wallets, coupons and ratings. Each phase goes live and earns feedback before the next is built.

This approach also makes costs more manageable. Budgets for these projects are covered on food delivery app development cost and clone app development cost.

• Phase 1 (8–10 weeks): customer app, vendor panel, admin, one payment method
• Phase 2 (4–6 weeks): rider or driver app, live tracking, assignment rules
• Phase 3 (4–6 weeks): wallet, offers, ratings, analytics

How to launch faster with an MVP: what to cut and what to keep

An MVP (minimum viable product) is the smallest version of your app that real users can use to complete the core task, and it is the most reliable way to shorten an app timeline. It is not a prototype or a demo; it goes into the stores and handles real customers, and it changes how long does it take to build an app from months to weeks.

The trick is choosing what to cut. Keep the one flow that creates value: for a tuition app that is enrol, attend, pay; for a salon app that is pick service, pick time, confirm. Cut everything that serves growth you do not have yet: referral programmes, multiple languages beyond the first two, complex dashboards, loyalty points, social logins beyond phone OTP.

Keep quality where it matters. A fast, stable core flow on a budget Android phone is worth more than ten half-finished features. Also keep the basics stores expect: a privacy policy, account deletion if you offer sign-up, and honest permission requests.

An MVP can often go live in 5–7 weeks where the full wish list would take 12. The saved weeks are not lost; they become version 1.1, planned with real usage data instead of guesses. Our MVP development cost in India guide shows how that changes the budget.

How long does it take to build an app backend and admin panel?

For a typical business app, the backend and admin panel are built alongside the app screens and add little calendar time; for platforms with complex rules, they can take as long as the app itself. Many first-time buyers forget this part exists, then wonder why an app with eight screens takes eight weeks.

The backend holds your data (users, orders, bookings), enforces rules (who can see what, what happens when a payment fails), and sends notifications. The admin panel is the web dashboard your staff use to manage everything. In our team, one developer builds this while another builds the app, so the two meet in the middle.

Things that lengthen backend work are reports that need exact accounting logic, integrations with Tally, Zoho or existing ERP, role-based access for many staff types, and anything involving money moving between parties. Things that shorten it are an existing website or system with a usable API, and choosing a managed backend such as Firebase or Supabase where it fits.

If the admin side is large enough to be its own product, we quote it as a web app from ₹60,000. See web application development for what that covers.

Can an app be built in 2 weeks or 30 days?

A genuinely simple app can be built in about a month, but a two-week store launch is rarely realistic once design, testing and review are counted. Offers of an app “in 7 days” usually mean a template with your logo, which may be fine for some needs and wrong for others.

Here is what a realistic 30-day app looks like: one user type, five to eight screens, content managed from a simple admin panel, phone OTP login, enquiry or booking form, push notifications, and no payments between users. Scope is agreed in the first days and approvals come within a day. Store accounts already exist and are verified.

What makes 30 days impossible: several user types, payments, live tracking, integrations with your existing software, or content that is not ready. Also, if your Play Console is a new personal account, the 14-day closed-test rule alone uses half the month.

Rushing also has a cost. Skipped testing shows up as one-star reviews, and a rejected submission can cost more days than careful preparation would have. If a hard date is fixed by an event, we would rather cut features than cut testing.

If your need is really “customers should be able to book or order from their phone by next month”, a mobile-first website or PWA may be the faster route. See how long a website takes to build for comparison.

How long does it take to build an app if you already have a website?

An existing website can shorten an app project by several weeks if its data and logins can be reused through an API, but it rarely lets you skip app work entirely. What matters is what sits behind the website, not how it looks.

If your site runs on WooCommerce, Shopify or a custom backend with an API, the app can read the same products, orders and customers. That removes most backend work and keeps stock and prices in one place. We then build native-feeling app screens on top.

If the site is a static brochure, it offers little to reuse beyond content and branding, and the app needs its own backend. If the site is an old custom PHP build without an API, we may need to add one first, which adds a week or two but gives you a cleaner setup for the long run.

A shortcut to avoid: wrapping your mobile website in an app shell and submitting it. Apple’s App Review Guidelines, under 4.2 Minimum Functionality, say an app should offer features, content and interface beyond a repackaged website, and apps that are not app-like get rejected. That rejection costs time you thought you had saved.

For the broader question of whether you need an app or a better website, website or app for your business walks through it.

Your side of the timeline: decisions, content and testing you own

About half of any app schedule depends on the client: decisions, documents, content and testing. This is not a complaint; it is simply how app projects work, and knowing it lets you protect your launch date.

Name one decision-maker. Apps stall when three partners each have opinions on the home screen. One person approves design and features, and consults others before replying.

Prepare documents early: business registration for store organisation accounts, GST and bank details for payment gateway onboarding, and brand assets such as logo files and colours. These are week-one tasks.

Plan the content. Product lists with photos, service menus, prices, FAQs, privacy policy and terms should be ready before the build is complete. A spreadsheet is fine; we import it.

Book testing time. When a test build arrives, try it within two days on your own phone and on a staff member’s budget Android phone. Send feedback as a list, screenshots or voice notes on WhatsApp.

• Week 1: approve scope, register or verify store accounts, start payment onboarding
• Week 2: approve design, send logo, colours and first content
• Midpoint: test the first build, share feedback within 48 hours
• Final fortnight: approve store text and screenshots, test the release candidate

Worked example: a week-by-week plan for a hypothetical clinic app

Here is a hypothetical example of how long it takes to build an app for a small healthcare business, week by week. Say a physiotherapy clinic with two branches in Indore wants patients to book sessions, pay online, see exercise videos and get reminders. Staff need to manage slots and see the day’s bookings.

The scope has two user types (patient and staff), an admin panel, UPI and card payment, video content and push notifications. That places it in the 6–10 week band. The clinic already has a registered business and a website, so store accounts can be set up in week one without delay.

In week one we agree the feature list, the clinic registers its Google Play organisation account and Apple Developer membership, and payment onboarding starts. Weeks two and three cover design approval and the first screens. By week four, the owner is booking test appointments on his own phone. Weeks five and six add payments, videos and reminders; staff test the admin panel. Week seven is fixing and store preparation; in week eight, both apps go to review and then live.

What could stretch this? The owner wanting a Hindi version mid-way, videos not being recorded in time, or payment onboarding waiting on documents. Each would be visible on the week plan the day it happened, with a choice to absorb it or move it to the next release.

Red flags when a developer tells you how long it takes to build an app

A trustworthy app timeline names phases, dates and dependencies; a vague one promises a finish date without showing how it gets there. When you compare developers, the schedule tells you as much as the price.

Be careful with any plan that shows no design approval step, no testing phase or no store review buffer. Those phases always happen; leaving them out just means they happen as surprises. Equally, be wary of a quote that claims a marketplace in three weeks, or one that cannot tell you who writes the backend.

Ask when you will first see a working build on your phone. If the answer is “at the end”, you lose the chance to correct direction early. Ask whose accounts the app will be published under. If it is the developer’s account, moving it later is slow and sometimes impossible without re-publishing.

Ask what happens if the developer disappears. Projects abandoned half-way usually take longer to rescue than to restart; our page on a developer who left a project midway covers recovery. For a full list of questions, see questions to ask an app developer.

Finally, check how change requests are handled. A contract model that prices additions openly keeps timelines honest; the trade-offs are laid out on fixed price vs time and material.

India-specific factors that change how long it takes to build an app

Building for Indian users adds a few specific tasks: UPI checkout, SMS rules, regional languages and testing on budget Android phones. None is difficult, but each changes how long does it take to build an app for India, so each needs time in the plan.

UPI and card payments go through a payment gateway, and onboarding requires your business documents; approval time varies by provider. OTP and transactional SMS in India require DLT registration of your sender ID and templates, which is done by you with a telecom operator portal before the app goes live. WhatsApp OTP or updates through the Business API need Meta business verification.

Language adds time in proportion to text. A Hindi and English app needs translated copy for every button, message and notification; you supply or approve the translations, and we handle layout and fonts. Adding a third language later is simpler if the app is built for multiple languages from day one.

Device testing matters more here than in many markets. Plenty of customers use entry-level Android phones with limited memory and patchy networks. We test on budget devices and keep app size and images small, which avoids a slow app that gets uninstalled in the first week.

After launch: how long updates, fixes and version 2 take once the app is live

Small fixes after launch usually reach users within days; a new feature release takes one to four weeks depending on size. The clock includes store review every time, so even a one-line fix is not instant; after launch, how long does it take to build an app turns into a question of release size and testing.

The first month after launch is the busiest. Real users find paths no test covered, and analytics show where they drop off. We fix bugs and ship small improvements during this period at no extra cost, because the first two months after launch include free maintenance.

OS updates add scheduled work. Apple and Google release major OS versions every year, and Google Play sets target API level deadlines that apps must meet to keep receiving updates. Planning a short update cycle around these avoids a last-minute scramble.

Version 2 is where the features you cut from the MVP return, now prioritised by real data. It is planned and quoted like the first release, with its own week plan. After the free period, ongoing care starts from ₹8,000/mo; our app maintenance cost in India page explains what that covers.

Checklist: be ready before you ask how long it takes to build an app

A developer can only give a reliable timeline when you can answer a handful of basic questions. Use this list before your first call; even partial answers make our reply to how long does it take to build an app far more accurate.

You do not need technical words. “Customers book a slot, pay, and get a reminder; my staff see bookings on a laptop” is a perfectly good description. Share screenshots of apps you like and say what you like about them.

• Who uses the app? List every user type: customers, staff, vendors, drivers, admins
• What is the one task each user must complete?
• Do you need payments, and who pays whom?
• Must it work offline, or with live location?
• Which languages, and who writes or approves the translations?
• Do you have a website or software whose data the app should use?
• Are your Google Play and Apple accounts registered, and in whose name?
• Is there a hard date (event, season, investor meeting), and what is essential by then?

Send these answers on WhatsApp and you will get an itemised quote with a week plan in about two working days. Our starting prices for every service are on the pricing page.