How to Launch an iOS App: App Review, TestFlight and Free Promotion
To launch an iOS app, join the Apple Developer Program, run a TestFlight beta, then submit a finished build with a working demo account and clear notes for review. Most first rejections come from a few guidelines: an unfinished build, an app that is only a website, a missing login alternative or account deletion, and payments outside in-app purchase. Promotion around the store can be free.
What is different about launching on the App Store?
Every iPhone app goes through App Review before the public can download it, so your launch date is not entirely yours. Apple’s reviewers, working from its published guidelines, decide whether the build goes out. That is the main difference from a web app and from Android’s test-then-publish path, and it argues for submitting early with a build you consider finished, then using the waiting time for everything else.
Apple’s program page, read on 13 November 2026, lists an annual membership of $99, and says a free developer account gives access to tools such as Xcode and beta operating systems, with the membership needed to distribute. Plan that as your one fixed cost.
Which guidelines reject new apps most often?
Apple’s App Store Review Guidelines are public. We read the page on 13 November 2026 and picked the clauses that catch first-time submissions. Read the live text before you submit; it changes.
| Guideline | What it says, in short | What to do |
|---|---|---|
| 2.1 App Completeness | Submit a final version with working URLs and no placeholder text. Include demo account info and turn on your back end if there is a login | Create a reviewer account that never expires, and keep servers running |
| 4.2 Minimum Functionality | An app should offer features, content and UI beyond a repackaged website | Show something native: offline use, notifications, device features |
| 4.3 Spam | Do not submit several bundle IDs of the same app | Ship one app, with variations inside it |
| 4.8 Login Services | An app that uses a third-party or social login for its primary account must also offer an equivalent login option with privacy features | Add the compliant alternative if you use social sign-in |
| 5.1.1 Data collection | An app that supports account creation must offer account deletion within the app | Build the delete-account button before the first submission |
| 3.1.1 In-App Purchase | Features and content that are paid for inside the app use in-app purchase, not your own license keys or similar | Plan pricing for the store route |
| 1.2 User-Generated Content | Apps that let people generate or share content, including AI content creation apps, need filtering, a report mechanism, the ability to block users and published contact information | Add those four before you submit an AI or social app |
Guideline 5.1.2 adds a rule worth noting for AI features: it asks you to disclose when personal data is shared with third parties, including third-party AI, and to obtain explicit permission first. See the AI app playbook for the cost and trust side.
How do you prepare a submission that gets through?
- Test the release build on a real device, on the oldest system version you support, on a poor connection.
- Create a demo account and write its details in the review notes. If a login is impossible to share, build a demo mode, which the guidelines allow.
- Describe in the notes the features a reviewer might not find, and how to reach each. The guidelines ask for new features to be described with specificity, and generic notes are rejected.
- Make the screenshots and description match what the app does today. The guidelines treat misleading marketing as grounds for removal.
- Fill in privacy details honestly, including every SDK that collects data.
Sizes and counts for screenshots change by device, so use the App Store screenshot sizes page and Apple’s own pages to check them before you upload, and the app store launch checklist for the rest.
How should you use TestFlight before launch?
TestFlight is Apple’s beta tool. Its page says you can invite up to 10,000 external testers, but that the first build for external testing has to be approved by App Review for TestFlight, and that a beta app description and beta app review information are required. Internal testers can start sooner. So use it twice: first with a few friends on internal builds to find crashes, then with an external group drawn from your market.
- Send each tester a short note on what to try, not just a link.
- Ask for the first thirty seconds on video or a screen recording; where they hesitate is your next fix.
- Keep the external group small enough to read every comment, which for most first apps means fewer than a hundred people.
The private beta playbook has a fuller plan for this stage.
How do you promote an iPhone app for free?
Do the free things in parallel with review. Put a page for the app on the free launch board, where the link to your own site is a followed link and nothing is queued. Prepare a short screen recording of the main flow, a landing page that links to the store once approved, and a message for the communities where the problem comes up. The iOS app places and mobile app showcases lists show other sites that accept apps; check each site’s fees before you submit.
When approved, ask your TestFlight testers for ratings, since early reviews affect whether a stranger installs. If you are searching for a concept, the iOS app ideas page has a long list, and the board’s productivity ideas are posted by people who will not build them.
What should you do if the app is rejected?
Read the cited guideline number, reply in the resolution center only if you can add facts the reviewer missed, and otherwise fix the item and resubmit. A rejection is a normal part of a first launch, not a verdict. Keep a log of each one and its fix; the same notes will save you time on the next app. For the plan after approval, use the post-launch checklist.
Frequently asked questions
Is it free to publish an iOS app?
No. Apple’s program page, read on 13 November 2026, lists an annual membership, and it says a free developer account gives access to tools but the membership opens distribution. Your promotion can be free: a launch board page, communities, a landing page and a beta, but the store account is a fixed cost.
How many testers can TestFlight handle?
Apple’s TestFlight page says you can invite up to 10,000 external testers, and that your first build for external testing must be approved by App Review for TestFlight. It also requires a beta app description and beta app review information. Internal testers do not go through that step.
Why was my first iOS app rejected?
Common causes in the guidelines are an incomplete build or no demo account, an app that is only a website, social login with no equivalent option, no in-app account deletion when accounts exist, and paid features outside in-app purchase. The rejection message cites a guideline number, so start by reading that clause.
Can I launch an iOS app on a free board before it is approved?
Yes. Put a page up that links to your website and says the app is coming, with a way to join a TestFlight beta or a waitlist. Update the page with the store link after approval. A public page is useful even while the build is in review.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.