# How to Launch an App on the App Store: Review, Release and Launch Steps

> How to launch an app on the App Store: developer enrolment, TestFlight, App Review timing, pricing, release options and the launch itself.

- Canonical: https://zeroraised.com/blog/how-to-launch-an-app-on-the-app-store
- Published: 2026-10-20
- Updated: 2026-10-20
- Author: Jay Mokashi (https://zeroraised.com/blog/authors/jaymokashi)
- Publisher: ZeroRaised (https://zeroraised.com/)
- Section: Growth
- Tags: indie-apps, marketplaces, app-launch, product-launch

How to launch an app on the App Store, in short: join the Apple Developer Program, create the app record in App Store Connect, test with TestFlight, fill in the product page and privacy answers, set a price, submit for App Review with manual release switched on, and only then pick launch day. The upload is the easy part. What trips up solo makers is review timing they cannot control, and a launch announced before Apple has said yes.

**Disclosure:** ZeroRaised publishes this guide and appears in the final section. The rules below follow Apple's linked developer documentation as checked on 18 Oct 2026, and this guide makes no promise of downloads, rankings, traffic or revenue from the App Store or any launch site.

## TL;DR

Most of the calendar risk sits in two places: enrolment, if you sign up as an organisation, and App Review, where you control very little. The rest is forms, if you know which fields Apple checks.

The single most useful setting is the release option. Set the version to release manually, or automatically but no earlier than a chosen date, before you press submit. Then approval becomes a private event, and launch day is a date you announce once the app is ready to download.

| Stage | Where | Apple's rule | Common snag |
|---|---|---|---|
| Enrol | Apple Developer app or website | 99 USD per membership year; two-factor authentication on your Apple Account | Organisations need a D-U-N-S Number and a working website |
| Create the record | App Store Connect | Bundle ID, name, primary language, SKU | An app name can be used for one app per localisation |
| Paid Apps Agreement | Tax and Banking section of App Store Connect | Needed to sell anything | Without it you can only offer the app free, and sandbox purchases wait |
| Upload a build | Xcode, Transporter or Xcode Cloud | Built with Xcode 26 or later on an iOS 26 SDK | Old CI images fail the SDK minimum |
| Beta test | TestFlight | 100 internal and 10,000 external testers | The first external build goes through review too |
| Product page | App Store Connect version page | Name 30 characters, up to 10 screenshots | Placeholder text gets rejected under Guideline 2.1 |
| Privacy | App Privacy section | Privacy policy URL plus data collection answers | Third-party SDKs count as your data collection |
| Review | App Review | Apple's target: 50% in 24 hours, 90% in 48 | Three makers this month report two days to about a month for new apps |
| Release | Version page | Manual, automatic, or automatic after a date | Up to 24 hours to appear after a manual release |

## This week's example: a month in the review queue, then two days

On 14 Oct 2026, Andrew Arrow published "Anecdotal, but my iOS App got approved much faster with new assets!" on the mainbrella engineering blog ([Andrew's post](https://mainbrella.com/blog/ios-app-review-new-assets/), checked 18 Oct 2026). It opens with a problem Andrew had been living with: "For the past few months, getting a new iOS app reviewed has been taking me about a month. It used to take a few days." Then the change: "Today, a submission with one of Apple's new image assets sailed through in two days."

Andrew is careful not to oversell it. "It's also one submission. I don't know whether the image helped, whether the queue got shorter, or whether I just got lucky." The post also states the cost of the wait plainly: "A month makes it hard to decide when to tell anyone your app exists."

The image in question is new. Apple's [App Store Connect release notes](https://developer.apple.com/help/app-store-connect/release-notes/) for 5 October 2026 introduced creative assets "to highlight your brand identity, promote seasonal updates, and showcase new app or game across the App Store", including product page headers and search results, plus a new Asset Library. Andrew added a header and a search result image to the version page, and notes that "Nothing in that workflow promises a faster app review." The decision still makes sense for other reasons: "I'll include these assets in future submissions because I want the listing to have them anyway."

Two other makers wrote about the same stage this week, from very different angles.

Pragathi Jayaram's DEV post on 12 Oct 2026 describes a nutrition app that "went into App Review on 27 July and came out approved on 6 August. First submission, no rejection, nothing in Resolution Center." ([Pragathi's post](https://dev.to/pragathijayaram/approved-on-the-first-submission-what-it-took-to-get-a-wellness-app-through-app-review-50je), checked 18 Oct 2026). That clean result came after weeks of preparation, an audit written in May and a full subscription test run. One line is worth taping above your desk: "A checklist written under deadline pressure is a checklist written to pass."

Matt Busel's DEV post on 18 Oct 2026 counts every App Review decision on one developer account: 64 decisions across 21 iPhone apps, with a median wait of 73 hours by Matt's own measurement ([Matt's post](https://dev.to/mattbusel/app-store-review-time-64-real-decisions-median-73-hours-4a52), checked 18 Oct 2026). Matt's advice for a new app on a new account is to plan for an extra round, "because the first one usually comes back with a question." Matt's figures cover 21 apps between 10 September and 12 October, including two batches rejected as spam, which is not how most solo launches look.

None of these timelines predicts yours. The shared lesson: review time is the one stage you cannot schedule, so the rest of the launch has to be built around not knowing it.

## How to launch an app on the App Store, step by step

This is the order that keeps waiting time from stacking up. Start the slow paperwork first, and build while it clears.

**1. Enrol in the Apple Developer Program.** Apple's [enrolment page](https://developer.apple.com/programs/enroll/) sets the price: "The Apple Developer Program is 99 USD per membership year. Prices may vary by region and are listed in local currency during the enrollment process." As an individual you need "an Apple Account with two-factor authentication turned on" and must use your legal name, because "Using an alias, nickname, or company name as your first or last name will cause a delay in the approval of your enrollment."

Decide early whether to enrol as yourself or as a company. Apple's [enrolment support page](https://developer.apple.com/support/enrollment/) explains that for an individual or sole proprietor, "your personal legal name will be listed as the seller on the App Store." An organisation shows its legal entity name instead, but needs a D-U-N-S Number, legal binding authority, a work email on the company domain and a website that is "publicly available and functional". Without a company already set up, enrolling as an individual is usually the quickest start. Apple's [enrolment page](https://developer.apple.com/programs/enroll/) notes a fee waiver route for nonprofits, accredited educational institutions and government entities.

**2. Sign the Paid Apps Agreement, even if launch is weeks away.** Apple's [pricing help page](https://developer.apple.com/help/app-store-connect/manage-app-pricing/set-a-price) says the Account Holder has to accept it in the Tax and Banking section, and "If the most recent version of this agreement hasn't been accepted, you can only offer your app for free." Pragathi's post shows why to start early: "sandbox purchases require an active Paid Apps Agreement", and that agreement was in turn waiting on a business bank account and a tax number.

**3. Create the app record.** In App Store Connect you add a new app with its platform, name, primary language, bundle ID and SKU. Apple's [help page on adding a new app](https://developer.apple.com/help/app-store-connect/create-an-app-record/add-a-new-app) says an app name can be used for one app per localisation, so if your first choice is taken you will find out here, not on launch day. Claim the name early.

**4. Upload a build.** Most solo makers upload from Xcode; Apple's [upload builds page](https://developer.apple.com/help/app-store-connect/manage-builds/upload-builds) also lists Transporter, altool and Swift Playground, and Xcode Cloud can build and upload for you. Check Apple's [upcoming requirements page](https://developer.apple.com/news/upcoming-requirements/) before your first upload. Since 28 April 2026, "Apps uploaded to App Store Connect must be built with Xcode 26 or later using an SDK for iOS 26", and since 9 September 2026 iOS apps "must target iOS 13 or later."

**5. Test with TestFlight, fill in the product page and privacy answers, set the price.** Each gets its own section below.

**6. Pick a release option, then submit.** Write review notes, add a demo account if your app has sign-in, and submit the version. Then wait, and use the wait well.

## Run a TestFlight beta before you submit

Guideline 2.2 of the [App Review Guidelines](https://developer.apple.com/app-store/review/guidelines/) is blunt: "Demos, betas, and trial versions of your app don't belong on the App Store", and it points you to TestFlight instead. The [TestFlight overview](https://developer.apple.com/help/app-store-connect/test-a-beta-version/testflight-overview) gives the limits: "external testers (up to 10,000 people) and internal testers (up to 100 App Store Connect users with access to your content)".

Two details shape a launch plan. First, external testing is not instant. The same overview says "When you add the first build of your app to a group, the build gets sent to App Review", so your first public beta is also your first contact with review. Treat its feedback as a preview of what the full submission might hit. Second, builds expire: "Your build becomes unavailable for testers after 90 days."

Testers can join through an invitation email or a public link, and a public link is the easiest way to turn a waitlist into testers before approval. If you are still collecting interest, the guide on [how to build a waitlist before launch](https://zeroraised.com/blog/how-to-build-a-waitlist-before-launch) covers the sign-up side.

Guideline 2.2 also forbids rewarding testers: TestFlight apps "cannot be distributed to testers in exchange for compensation of any kind".

## Build the product page while you test

The product page is your launch page inside the store, and most of it is editable only when you submit a new version. Apple's [product page guidance](https://developer.apple.com/app-store/product-page/) sets the limits.

| Field | Limit (Apple's wording) | Editable without a new version? | What to put there |
|---|---|---|---|
| App name | "up to 30 characters long" | No | The name plus, if room, the job it does |
| Subtitle | A concise phrase under the name | No | The main use, not "world's best app" |
| Promotional text | "up to 170 characters long" | Yes, any time | Launch news, a limited offer |
| Keywords | "limited to 100 characters total" | No | Search terms not already in the name |
| Screenshots | Up to 10 on the product page | No | The first one to three appear in search results when no app preview is available |
| App previews | Up to 30 seconds, up to three | No | The core action in the first seconds |
| Creative assets (new) | Header 3840 x 1646; search image 1920 x 1280 to 3840 x 2560 (Apple's specs as listed in Andrew's post) | Can be submitted on their own, per Andrew's post | Brand image for header and search placements |

On screenshots, Apple's product page guidance says "the first one to three images will appear in search results when no app preview is available, so make sure these highlight the essence of your app." The ZeroRaised guide to [App Store screenshots for launch](https://zeroraised.com/blog/app-store-screenshots-for-launch) covers captions and order, and [App Store keyword research for indie apps](https://zeroraised.com/blog/app-store-keyword-research-for-indie-apps) covers the 100-character keyword field. This guide will not repeat either.

The creative assets from Andrew's story are worth a look even without any review benefit. As Andrew's post summarises Apple's documentation, they are optional and "separate from the screenshots that show the app in use", they can be submitted with a version or on their own, and "Apple accepts PNG or JPEG for these sizes and says images can't have transparency."

Pragathi's warning about this stage, from one first launch: "Budget a fortnight rather than an afternoon, because the listing is not a form."

## Privacy labels and the guidelines that stop new apps

Every iOS app needs a privacy policy URL and a set of answers about data collection. Guideline 5.1.1(i) says apps "must include a link to their privacy policy in the App Store Connect metadata field and within the app in an easily accessible manner." A link only on your website is not enough.

The privacy nutrition label is where solo makers most often under-declare. Apple's [app privacy details page](https://developer.apple.com/app-store/app-privacy-details/) says "You need to identify all of the data you or your third-party partners collect", and defines third-party partners as "analytics tools, advertising networks, third-party SDKs, or other external vendors whose code you've added to your app." So the crash reporter and analytics package you added in an afternoon belong in your answers. The good news: "You may update your answers at any time, and you do not need to submit an app update in order to change your answers."

Three guidelines come up in the posts above and are worth reading before a first submission:

- **2.1 App Completeness.** Submissions "should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission." If the app has accounts, the guidelines ask for "either an active demo account or fully-featured demo mode". Pragathi provisioned the demo account as a paying subscriber so the reviewer could reach every paid feature, then found the restore button was unreachable in exactly that state.
- **4.2 Minimum Functionality.** An app that is not particularly useful, unique or app-like "doesn't belong on the App Store", in Apple's words. A thin wrapper around a website is the classic case.
- **4.3 Spam.** "Don't create multiple Bundle IDs of the same app", and do not submit apps "that are indistinguishable from what's already widely available." Matt's data shows what this looks like at volume: by Matt's count, "every wait longer than 5.1 days except one ended in a guideline 4.3 spam rejection."

Since early 2026 Apple has also used a new age rating system. The [upcoming requirements page](https://developer.apple.com/news/upcoming-requirements/) says ratings for all apps were updated and asked developers to answer the updated age rating questions, so expect that questionnaire on a new record. If your app sends personal data to a third-party AI service, read Guideline 5.1.2(i) closely. Pragathi quotes the current text: "You must clearly disclose where personal data will be shared with third parties, including with third-party AI, and obtain explicit permission before doing so."

## Price it: free, paid, subscription and the 15% rate

Pricing is set before submission. Apple's [pricing guide](https://developer.apple.com/help/app-store-connect/manage-app-pricing/set-a-price) says "You'll need to set pricing for your app before you submit it for review. Choose from up to 800 price points by default". You choose a base country or region, and Apple uses it "to provide comparable prices on the other 174 storefronts", adjusting those prices as taxes and exchange rates change.

Then join the [App Store Small Business Program](https://developer.apple.com/app-store/small-business-program/) before your first sale. It "features a reduced commission rate of 15% on paid apps and Apple In-App Purchases", and "developers new to the App Store, can qualify for the program and the reduced commission." You must list any Associated Developer Accounts, and the lower rate is not instant: "Your proceeds will be adjusted fifteen (15) days after the end of the fiscal calendar month in which your enrollment is approved." Enrol the week you join the Developer Program, not the week of launch.

| Model | What Apple requires | Commission (Small Business Program) | Fits when |
|---|---|---|---|
| Free, nothing to buy | Membership only | None described for free apps | Lead generation, a companion app, a portfolio piece |
| Paid upfront | Paid Apps Agreement, a price point | 15% on paid apps | A finished tool with a clear one-off value |
| Free with In-App Purchases or subscriptions | Paid Apps Agreement, IAP products submitted for review | 15% on In-App Purchases | Most indie apps that need ongoing revenue |
| Pre-order, then paid | Release manually; buyers not charged until release | 15% once sales happen | A launch date you want to build towards |

If you choose subscriptions, test the whole lifecycle in sandbox. Pragathi's single day of sandbox testing found four defects in a payment layer that had only been runnable against a real transaction that morning.

## App Review timing: what Apple says and what makers report

Apple's [App Review page](https://developer.apple.com/distribute/app-review/) says it works "around the clock, typically reviewing at least 50% of submissions in less than 24 hours and 90% in less than 48 hours." The [review status guide](https://developer.apple.com/help/app-review/after-submitting-for-review/review-status/) adds a qualifier that matters for a first launch: "While updates with minor changes and bug fixes typically move through review quickly, other submissions may take longer to verify."

Apple does not say which submissions take longer, but a brand new app is not a minor update. The makers above measured very different things: Andrew saw about a month per new app before a two day approval, Pragathi waited ten days, and Matt's median across 64 decisions was 73 hours. These are individual reports, not a measurement of the queue. They are enough to say: do not put a launch date in public until you have approval.

While you wait, the status tells you what you can still change. In "Waiting for Review" you can edit some information, "though you can't upload or edit screenshots and app previews." If Apple has questions, reply in App Store Connect. A rejection on the build means a new upload, and Apple says that "starts a full review of the new build", so fix everything flagged in one go.

Expedited review exists, but it is narrow. Apple lists "fixing a critical bug in your app or releasing your app to coincide with an event you're directly associated with." A launch on a community site is not an event in that sense. For timing that does depend on you, see Apple's advice on events: "we recommend you plan and schedule the release of your app in App Store Connect."

## Pick a release option before you press submit

The [release option guide](https://developer.apple.com/help/app-store-connect/manage-your-apps-availability/select-an-app-store-version-release-option) offers three choices on the version page, plus two related tools for later.

| Option | What happens after approval | Best for | Watch out for |
|---|---|---|---|
| Manually release this version | Waits in Pending Developer Release until you press release | Most first launches | Apple emails a reminder after 30 days in that status |
| Automatically release this version | Goes live as soon as it is approved | Bug fixes and small updates | Launch day is set by the review queue, not by you |
| Automatically release after a date | Goes live after approval, no earlier than your date and time | A launch date you have already announced | The date is a floor only; Apple's option says "no earlier than" the date you enter |
| Pre-order | Product page visible and orderable before release | Building towards a fixed date | Must be released manually; In-App Purchases cannot be pre-ordered |
| Phased release | An update rolls out to automatic-update users over 7 days | Updates after launch | Not for first versions; pauses capped at 30 days in total |

For a first launch, manual release is the safest default. One more detail from Apple: "After manually releasing your app version, it may take up to 24 hours for it to appear on the App Store." Release the evening before launch day, check the live product page link works in your region, and only then post.

Pre-orders suit makers with an audience to bring. Apple's [pre-order guide](https://developer.apple.com/help/app-store-connect/manage-your-apps-availability/publish-for-pre-order) says "Both free and paid apps across all Apple platforms are eligible for pre-orders", and "Customers who pre-order a paid app won't be charged until the app's official download release date." When the app is released, customers get a notification and it downloads automatically.

[Phased release](https://developer.apple.com/help/app-store-connect/update-your-app/release-a-version-update-in-phases) is for the first update after launch, when real users find what testers missed. It moves through 1%, 2%, 5%, 10%, 20%, 50% and 100% of users with automatic updates, and "you may pause the release for up to 30 days". Write clear notes for each version too; the guide on [how to write release notes](https://zeroraised.com/blog/how-to-write-release-notes) applies to the App Store's "What's New" text as much as a changelog.

## The launch outside the store

Approval puts the app in the catalogue. It does not tell anyone it exists. A new app with no ratings competes with established apps for the same search terms, so, as editorial judgement rather than a measured rule, the first downloads usually come from places where you already have attention.

A simple launch week for a solo maker:

1. **Approval day.** Keep quiet. Check the version page, the price in a second storefront and the privacy label preview.
2. **Evening before launch.** Release manually, then confirm the store link opens the product page.
3. **Launch day.** Post where your users already are. A Show HN works for apps with a technical story; see [how to write a Show HN post](https://zeroraised.com/blog/how-to-write-a-show-hn-post). For Product Hunt, read [how to launch on Product Hunt](https://zeroraised.com/blog/how-to-launch-on-product-hunt) first, and use the [launch time tool](https://zeroraised.com/tools/launch-time) to pick an hour.
4. **The following week.** Spread out further listings rather than firing them all at once. The [launch sites directory](https://zeroraised.com/launch-sites) lists venues by audience, and the [product launch checklist for bootstrapped makers](https://zeroraised.com/blog/product-launch-checklist-for-bootstrapped-makers) covers the parts that are not store specific.

Use promotional text for launch news, since it can change without a new version, and reply to every early review.

## Where a launch listing fits after App Review

An approved app gives you real launch material: a store link that works, screenshots, a price and a privacy label anyone can check. None of that guarantees anyone turns up, and no launch site can promise downloads.

[ZeroRaised](https://zeroraised.com/) is a free launch site for bootstrapped makers whose products have no institutional VC or accelerator equity. If your app is live on the App Store and fits, you can [submit it for review](https://zeroraised.com/submit), ideally once the store link is working rather than while Apple is still deciding. The [maker perks page](https://zeroraised.com/perks) is a separate resource for eligible makers. Neither replaces a clear product page or a fast reply to the first one-star review.

So, how to launch an app on the App Store: enrol early, sign the agreements early, test in TestFlight, fill in the product page and privacy answers honestly, set a price and join the Small Business Program, then submit with manual release on. Let Apple take as long as it takes, and pick launch day once the app can actually be downloaded.

## Frequently asked questions

### How much does it cost to launch an app on the App Store?

The fixed cost is the Apple Developer Program at 99 USD per membership year, shown in local currency where available. Nonprofits, accredited educational institutions and government entities can request a fee waiver. If you sell the app or In-App Purchases, Apple takes a commission, which is 15% for members of the App Store Small Business Program.

### How long does it take to launch an app on the App Store?

Apple says App Review typically handles at least 50% of submissions in under 24 hours and 90% in under 48 hours, and that minor updates move quickly while other submissions may take longer. Three makers writing this month describe their own new app reviews taking from two days to about a month, so plan for at least one rejection round and leave buffer before any announced date.

### Can I launch an app on the App Store for free?

Distributing a free app still needs a paid Apple Developer Program membership unless your organisation qualifies for a fee waiver. Apple describes its commission as applying to paid apps and In-App Purchases, so a free app with nothing to buy pays only the membership.

### Should I release my app automatically or manually after approval?

Manual release, or automatic release no earlier than a set date, lets you pick launch day instead of letting review timing pick it. After a manual release Apple says it may take up to 24 hours for the app to appear on the App Store, so release the evening before you tell anyone.

### Can I put an iPhone app on pre-order before launch?

Yes. Free and paid apps can be offered for pre-order in any country or region where they have not yet been released. Customers who pre-order a paid app are not charged until release day, In-App Purchases cannot be pre-ordered, and a pre-order app must be released manually.