How Long Does It Take to Build an iOS App? Timeline and App Store Review
Building takes months and follows the scope; Apple's review takes days. Which dates Apple fixes, which ones your decisions move, and how to count a launch calendar backwards.

Key takeaways
- Apple's App Review page says it typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours, as of November 16, 2026.
- Market figures, not ours: Clutch's 2026 pricing guide puts the usual mobile app project at about 11 months, and a practitioner article published by Clutch calls 20–40 weeks typical.
- A company developer account needs a D-U-N-S Number: Apple says up to 5 business days from Dun & Bradstreet plus up to 2 more before Apple has the data, and expediting does not shorten the wait.
- TestFlight allows up to 100 internal and up to 10,000 external testers; Apple's help says the first external build requires a full App Review, and a build can be tested for up to 90 days.
- Apple's 2025 App Store Transparency Report counts 2,093,244 rejected submissions out of 9,100,620 reviewed, about 23%; Apple says over 40% of unresolved issues fall under guideline 2.1, App Completeness.
Building an iOS app takes months; Apple's review takes days. Clutch puts the usual mobile app project at about 11 months, and a practitioner article Clutch published calls 20–40 weeks a typical timeline. Both are market figures, not our timelines. Apple says App Review typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours, so review itself rarely moves a launch date. A company account that isn't ready, or a rejection, does.
This guide is for founders and product owners in the US and the UAE who have to name a launch date. Inside: the phases of an iOS project and what the length of each depends on, Apple's steps with the timing Apple states as of November 16, 2026, the usual rejection reasons by guideline number, what shortens a launch and a calendar worked back from launch day. Vladimir Babin, our co-founder and Head of Mobile, has 10+ years of shipping production iOS and macOS apps.
How long does it take to build an iOS app?
It follows the scope. The two published numbers show why.
Clutch's pricing guide, updated September 21, 2026, says the usual mobile app project runs about 11 months, and adds that some apps take a few weeks and others take years. The 20–40 week figure comes from an article by a development firm's VP of Technology, published by Clutch and updated May 29, 2026. It is one practitioner's experience, not a survey. Neither number describes your app: both mix a booking app with one core flow and a marketplace with three roles and payouts.
A date becomes predictable once you split the project into two clocks:
- The project's clock. Discovery, design, build and testing. Its length comes from the feature list, the integrations and how fast decisions get made. Months are won or lost here.
- Apple's clock. The developer account, beta review, App Review and release. Each step is short, and several can start on day one instead of in the last week.
The fastest route to the App Store is a focused first release: one core flow, sign-in and payments, then the rest once users are in. Our guide to MVP development cost shows how to cut scope to that size, and iOS app development cost turns the same feature list into hours and budget.
App development timeline: what happens in each phase
Phases of an iOS project, what the length of each depends on, and the range the Clutch-published article gives for it. The ranges are market figures from that article, not our timelines. Checked November 16, 2026.
| Phase | What happens | What its length depends on | Published range |
|---|---|---|---|
| Discovery | Roles, screens, integrations, a clickable prototype, an agreed scope | Whether a brief exists, how many people must agree, how fast they answer | Planning: 2–3 weeks |
| Design | Interface design on top of the approved prototype | Number of unique screens, standard or custom components, rounds of review | 2–4 weeks |
| Build | iOS client, backend, admin panel, integrations | Feature count, payments, third-party APIs, whether a backend already exists | 3–6 months |
| Testing | Real devices, OS versions, edge cases, fixes | Range of devices and OS versions, how much was tested during the build, bug count | 3–6 weeks |
| TestFlight beta | Your team first, then outside users | Apple's beta review of the first external build, how fast testers respond | Not listed separately |
| App Review and release | Apple checks the build and the listing; the version goes live on the date you choose | Completeness of the submission; one more round per rejection | Deployment: 1–2 weeks |
The phases add up to roughly the article's 20–40 weeks. Three things the table can't show:
Phases overlap. Later screens are designed while the first ones are built, and testing is not a block at the end: we put a new build in TestFlight every sprint, so you use the app on your own phone as it grows.
Discovery is the cheapest place to save time. A clickable prototype you try on your iPhone before development starts forces decisions early. Our software development brief template lists what to write down before the first call.
Build time is mostly scope and stack. Each role, integration and payment flow adds time. So does the choice we compare in Swift vs Flutter vs React Native.
How long does it take to publish an app on the App Store?
Publishing is a chain of Apple steps, not one button, and for some of them Apple states no timing at all.
Apple's steps between an idea and a live app, with the timing Apple states for each. From Apple's developer pages, checked November 16, 2026.
| Apple's step | What Apple states | What you control |
|---|---|---|
| D-U-N-S Number | Free. Up to 5 business days to get it from Dun & Bradstreet, then up to 2 business days until Apple has the data | Request it on day one, with registration documents at hand |
| Organization enrollment | Apple verifies the enrollment information and emails next steps. No duration stated. 99 USD per membership year | A legal entity, a website on your domain, a person with authority to sign |
| Paid Apps Agreement | The Account Holder must sign it to sell apps or offer In-App Purchases | Sign it early, not in launch week |
| TestFlight, internal | Up to 100 testers from your App Store Connect team. A build can be tested for up to 90 days | Add yourself from the first build |
| TestFlight, external | Up to 10,000 testers. The first build requires a full review; later builds of the same version might not. No duration stated | Beta description, review information, a tester group |
| App Review | Typically at least 50% of submissions in under 24 hours, 90% in under 48 | A complete submission |
| Release | Manual, automatic, or automatic no earlier than a date. Up to 24 hours to appear after a manual release | The date |
| Phased release | For version updates: seven days, from 1% to 100% of users, pauses of up to 30 days in total | Whether to use it |
The company developer account: start it on day one
Apple enrolls an organization only as a legal entity: no DBAs, fictitious businesses, trade names or branches. The company needs a D-U-N-S Number, a public, working website on its own domain, and a person with the legal authority to sign for it. The legal entity name is what buyers see as the seller on the App Store.
D&B takes up to 5 business days, and Apple adds up to 2 more before you can start enrolling. Apple says expediting the D-U-N-S request will not shorten the wait. Then comes Apple's own verification, which has no stated length and may include a request for notarized business documents. Treat the account as a task of weeks, and start it the day the project starts.
The account matters for review too: under guideline 5.1.1(ix), apps in regulated fields such as banking, healthcare and air travel must be submitted by the legal entity that provides the service. We publish apps under the client's own company account.
TestFlight: your team first, a review for outside testers
TestFlight has two kinds of testers: internal ones from your team and external ones you invite by email or a public link.
The difference for the calendar: the first build you add to an external group goes to App Review, and later builds of the same version might not need a full review. Apple states no timing for beta review, so don't promise outside testers access on the day the build is ready.
What has to be filled in before you can submit
- Privacy details. The "nutrition label" on the product page. Apple requires it for new apps and updates, third-party code included, along with a public privacy policy URL.
- Privacy manifests. For SDKs on Apple's list, which includes Firebase, Alamofire, Flutter and OneSignal, a new app must include the SDK's privacy manifest. Since May 1, 2024, apps must also declare approved reasons for certain APIs.
- Age rating. Apple generates the rating, from 4+ to 18+, from a questionnaire, and an unrated app can't be published. Apple announced on November 2, 2026 two new descriptors from November 16, Shared Location and Dating and Relationships, which all apps must declare by January 12, 2027.
- Build tools. Since April 28, 2026, uploads must be built with Xcode 26 or later. Apple has announced the next step: starting April 2027, apps must be built with the iOS 27 SDK and target iOS 15 or later, and submissions will need screenshots for iPhone Duo.
- In-app purchases. The first In-App Purchase of each type must be submitted with a new app version, so set products up before the submission.
The SDK dates move every year; our guide to app maintenance cost covers that cycle.
How long does App Store review take?
Apple's wording: "App Review works around the clock, typically reviewing at least 50% of submissions in less than 24 hours and 90% in less than 48 hours." It adds that an incomplete submission may be delayed or may not pass.
"Typically" is not a promise. The App Store Review Guidelines name what slows a review: an app that "is complex or presents new issues", and an app that is "repeatedly rejected for the same guideline violation."
Plan for more than one round. Apple's 2025 App Store Transparency Report counts 9,100,620 app submissions reviewed and 2,093,244 rejected, about 23%, and notes that apps may be submitted several times before approval.
App Store review time before an event or the holidays
Apple accepts requests for an expedited review "if you face extenuating circumstances, such as fixing a critical bug in your app or releasing your app to coincide with an event you're directly associated with." For event apps it recommends scheduling the release in App Store Connect instead, and the guidelines warn that Apple may reject future requests from developers who abuse the system. Expedited review is a safety net, not a plan.
Late December is the other risk. In its last holiday notice, in December 2024, Apple said reviews "may take longer to complete from December 20-26." As of November 16, 2026, Apple's developer news has no notice for this season, so check before you plan a year-end release.
Why was my app rejected? The usual reasons by guideline number
Apple says that, on average, over 40% of unresolved issues relate to guideline 2.1, App Completeness. The transparency report points the same way: Performance, the section that holds 2.1, accounts for 1,354,418 rejections, more than any other section.
Apple's list of common issues includes 2.1, 2.3, 4.2 and 5.1. Those and other rules for a first release, in the guidelines as last updated October 16, 2026:
- 2.1, App Completeness. Submit a final version: no placeholder text or empty websites, tested on a device, with a demo account and the backend switched on (a). In-app purchases must be complete, visible to the reviewer and functional (b).
- 2.3, accurate metadata. Screenshots must show the app in use, not only a login page or a splash screen (2.3.3). App names are limited to 30 characters, and names, subtitles and screenshots must not include prices (2.3.7).
- 5.1.1, privacy. A privacy policy link in App Store Connect and inside the app (i), permission requests that say clearly what the data is for (ii), and account deletion inside the app if the app lets people create an account (v).
- 4.8, login services. An app that uses a third-party or social login for its primary account must also offer an equivalent option that limits data collection to name and email and lets users keep the email private.
- 3.1.1, in-app purchase. Unlocking features or digital content inside the app goes through Apple's In-App Purchase. Our guide to App Store commission covers the rule and its exceptions.
- 4.2, minimum functionality. The app must be more than a repackaged website. See taking a vibe-coded app to production if yours was assembled with AI tools.
- 2.5.19 and 2.3.1(a), hidden features. Guideline 2.5.19, added on October 16, 2026, bans hidden, dormant or undocumented features. New features must be described specifically in the Notes for Review; "generic descriptions will be rejected."
How to avoid a second round
Apple's own "Before You Submit" list is short: test for crashes, complete the metadata, give App Review a demo account or demo mode, keep backend services live during review, and explain non-obvious features and in-app purchases in the review notes.
If the app is rejected anyway, answer in App Store Connect before you rebuild: Apple says you can correspond with App Review to resolve the issues before resubmitting. Fix everything the message lists in one pass, because a repeat rejection under the same guideline slows the next review.
What shortens an iOS launch, and what doesn't
What shortens it:
- A smaller first release. One core flow, sign-in and payments. Every screen you postpone is design, build and testing you don't wait for.
- Native components. Apple's standard navigation, lists and forms come already built. Custom controls are worth it where they are the product, not everywhere.
- A ready backend and ready content. Apple reviews a working product: live backend, real texts, a published privacy policy. If the API or the content arrives late, the submission waits.
- Decisions made on time. The Clutch-published article says changing requirements during development can significantly extend the timeline. One person on your side who answers quickly is worth more than another developer.
What doesn't:
- Adding people late. The same article warns that new people added late "can inadvertently slow you down as they get up to speed." Fred Brooks made the point in 1975, in The Mythical Man-Month: adding people to a late software project makes it later.
- Skipping testing or submitting an unfinished build to get in line. Crashes and placeholder content are what guideline 2.1 rejects, and repeat rejections slow later reviews.
- Counting on expedited review. It is a request, not a right.
We have no native iOS case with a launch timeline on our site yet, so here is what carries over. For NVP, a fintech web product that pays freelance teams, we designed on the product's own components, so the first redesign ran in its code the next day and the final dashboard was delivered in 15 days, on target for a partner demo in May. On iOS, the same move is designing on Apple's standard components. ChessProfi, also a web app, shows ready parts on the backend side: it is built on Supabase and pairs rounds with the FIDE-certified bbpPairings engine.

How long before launch should you submit? A calendar worked backwards
Start from the launch date and walk back. The buffers below are how we'd plan around Apple's stated rules, not delivery promises.
A launch calendar counted back from launch day, with the Apple rule behind each line. Checked November 16, 2026.
| When | What must be true | The rule behind it |
|---|---|---|
| Launch day | The approved version is released manually or on a scheduled date | A manual release can take up to 24 hours to appear, so release the day before an announcement |
| One to two weeks before | The final build is submitted to App Review, release set to manual | Typically 90% of reviews finish within 48 hours; leave room for a rejection, a fix and a second review |
| Before submission | Listing, screenshots, privacy details, age rating, review notes, demo account and in-app purchases are complete | An incomplete submission may be delayed or may not pass |
| Several weeks before | The first external TestFlight build has passed beta review and testers are using it | The first external build needs a full review; a build can be tested for up to 90 days |
| From the first sprint | Internal TestFlight builds reach you and the team | Up to 100 internal testers; a build may require review once you invite external ones |
| Day one of the project | D-U-N-S requested, enrollment started, Paid Apps Agreement on the list | Up to 5 plus 2 business days before enrollment can start; verification time is not stated |
iOS launch checklist: next steps
- Scope. Write down the one core flow of the first release and what waits for the second.
- Account. Request the D-U-N-S Number and start organization enrollment today, in your company's name. If the app sells anything, have the Account Holder sign the Paid Apps Agreement.
- Prototype. Approve a clickable prototype on your own iPhone before development starts.
- Builds. Ask for a TestFlight build every sprint and name the people who test it.
- Store materials. Prepare the privacy policy, privacy details, age rating answers, screenshots and review notes while the app is being built.
- Reviews. Send the first external build weeks before launch, then submit the final one with room for two review rounds.
Our iOS development service covers discovery, design, the build, TestFlight and the App Store launch, led by a partner. To go through your launch date with a partner, book a call.
Questions we get asked
How long does App Store review take in 2026?
Apple says App Review typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours. That is Apple's wording as of November 16, 2026, not a guarantee: an incomplete submission may be delayed or may not pass, and complex apps or repeated rejections under the same guideline take longer. Plan one to two weeks between submission and launch so a rejection, a fix and a second review still fit.
How long does it take to get an Apple developer account for a company?
Plan for weeks, not days. An organization needs a D-U-N-S Number: Apple says Dun & Bradstreet takes up to 5 business days to issue one, and up to 2 more business days pass before Apple has the data. After that Apple verifies the enrollment and states no duration for it. Membership costs 99 USD per year. Start on the first day of the project, because none of it needs code.
Can I ask Apple for a faster app review?
Yes. Apple accepts expedited review requests for extenuating circumstances, such as fixing a critical bug or releasing an app for an event you are directly associated with. It is a request, not a right, and the App Store Review Guidelines warn that developers who abuse the system may have future requests rejected. For an event app, Apple recommends planning ahead and scheduling the release date in App Store Connect.
Does a TestFlight build need App Review?
For external testers, yes. Apple's TestFlight help says a beta build may require review if you invite external testers. TestFlight allows up to 10,000 of them, and Apple says the first build you add to an external group requires a full review. Later builds of the same version might not. Up to 100 internal testers from your App Store Connect team can test builds too, and the help names no review step for them. Apple states no timing for beta review, and a build can be tested for up to 90 days.
Why do apps get rejected by the App Store?
Most often because they are unfinished. Apple says that, on average, over 40% of unresolved issues fall under guideline 2.1, App Completeness: crashes, placeholder content, no demo account, a backend that is off during review. Apple's 2025 App Store Transparency Report counts 2,093,244 rejected submissions out of 9,100,620 reviewed, about 23%. Apple's list of common issues also names inaccurate screenshots and apps that do not perform as advertised (2.3), privacy policy issues (5.1) and websites served inside an app (4.2).
Should the app be published under my company's account or the developer's?
Under your company's account. The legal entity that enrolls is the seller buyers see on the App Store, and Apple enrolls organizations only as legal entities with a D-U-N-S Number. Guideline 5.1.1(ix) also requires apps in regulated fields such as banking, healthcare and air travel to be submitted by the legal entity that provides the service. We publish apps under the client's own company account, so the listing stays with the client.
Sources
- Mobile App Pricing Guide 2026 · Clutch, 2026
- How Long Is a Typical Mobile App Development Timeline? · Clutch, 2026
- App Review · Apple Developer, 2026
- D-U-N-S Number · Apple Developer Account Help, 2026
- Enrollment · Apple Developer Program, 2026
- Program enrollment · Apple Developer Account Help, 2026
- Sign and update agreements · App Store Connect Help, 2026
- TestFlight overview · App Store Connect Help, 2026
- Invite external testers · App Store Connect Help, 2026
- Select an App Store version release option · App Store Connect Help, 2026
- Release a version update in phases · App Store Connect Help, 2026
- TestFlight · Apple Developer, 2026
- App privacy details on the App Store · Apple Developer, 2026
- Third-party SDK requirements · Apple Developer Support, 2026
- Upcoming Requirements · Apple Developer News, 2026
- Age ratings values and definitions · App Store Connect Help, 2026
- Upcoming: New age rating content descriptors in App Store Connect · Apple Developer News, 2026
- Submitting · Apple Developer, 2026
- Prepare and submit your apps for iPhone Duo · Apple Developer News, 2026
- Submit an In-App Purchase · App Store Connect Help, 2026
- App Store Review Guidelines · Apple Developer, 2026
- 2025 App Store Transparency Report · Apple, 2026
- Get your apps and games ready for the holidays · Apple Developer News, 2024
- The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition · Addison-Wesley Professional (Frederick P. Brooks), 1995
Share this article

About the author
Vladimir Babin
Co-founder, Head of Mobile
Leads native iOS and mobile apps, from idea to App Store.


