Overview: Two Very Different Distribution Channels
When shipping an iOS application, developers frequently ask: "Can I just share my app via TestFlight instead of going through the full App Store review?" or "If Apple approves my TestFlight build, is it automatically ready for public release?"
TestFlight and the public App Store are two fundamentally distinct distribution channels governed by different rules, audiences, review standards, and lifecycles:
- TestFlight is Apple's pre-release testing platform. It allows you to distribute development and beta builds to internal team members (bypassing Beta App Review once Apple processing and compliance checks complete) or up to 10,000 external testers via email or public link. Every build distributed through TestFlight has a strict 90-day lifespan.
- The App Store is Apple's commercial marketplace. It makes your app publicly searchable, purchasable, and downloadable by hundreds of millions of users worldwide. Public releases require full App Review against the complete App Store Review Guidelines and remain live indefinitely.
Independent Review Separation: An approved TestFlight external beta build is NOT automatically approved for the public App Store. Beta App Review is a lightweight check for basic functionality and prohibited content. Full App Review conducts rigorous verification of privacy labels, in-app purchases, demo credentials, business models, and platform completeness.
The Seven Stages of Apple Release Availability
Developers often confuse upload success with user availability. To set realistic expectations, distinguish between these seven sequential gates:
- Successful Binary Upload: The
.ipaarchive is chunk-uploaded and hashed into Apple's ingestion pipeline. - Apple Ingestion Processing: Apple's servers inspect the binary, perform automated static analysis, strip architectures, and transcode assets. This typically takes 10 to 60 minutes depending on binary complexity and server load.
- Internal TestFlight Eligibility: Once processing state reaches
VALIDand export compliance is declared, the build becomes immediately available to internal testers (up to 100 App Store Connect team members) without human review. - External Beta App Review: Attaching the build to an external beta testing group triggers Apple's Beta App Review for the first build of a new marketing version. External testers cannot access the build until review is approved.
- External Distribution: Once approved, external testers receive invitations or access the build via public link. The build remains installable until the 90-day expiration timer elapses.
- Public App Review: Full evaluation by Apple reviewers verifying Guideline compliance, privacy nutrition labels, in-app purchase functionality, and reviewer demo credentials.
- Public App Store Release: The approved app transitions to
Ready for Sale(either automatically or upon manual developer release).
Side-by-Side Comparison: TestFlight vs. App Store
This matrix details the operational and technical differences between both channels:
| Dimension | TestFlight Internal Testing | TestFlight External Beta Testing | Public App Store Release |
|---|---|---|---|
| Primary Purpose | Rapid internal developer validation | User feedback & public beta testing | General availability & commercial sales |
| Audience Scope | Direct team members & QA engineers | Customers, beta communities, VIPs | Any iOS user worldwide |
| Maximum Tester Limit | Up to 100 internal testers | Up to 10,000 external testers | Unlimited public downloads |
| Apple Review Required? | NO. No Beta Review; requires Apple ingestion processing & compliance. | Light Beta App Review per build series | Full App Review against all Guidelines |
| Build Lifespan | Strictly 90 days from upload | Strictly 90 days from upload | Indefinite until superseded |
| App Store Discoverability | Not searchable; private access only | Private link or email invitation only | Fully indexed in Search, Categories & Charts |
| In-App Purchases / StoreKit | Free simulated purchases (Sandbox) | Free simulated purchases (Sandbox) | Live production StoreKit billing |
| Required Storefront Metadata | None required | "What to Test" release notes | Full descriptions, 100-char keywords, URLs |
| Screenshot Requirements | None required | None required | Mandatory 6.7" iPhone & 12.9" iPad display sets |
| Export Compliance Attestation | Required (ITSAppUsesNonExempt...) |
Required | Required |
| Impact of Review Rejection | N/A (Build runs after processing) | Only external testing blocked | Public launch delayed until resolved |
When to Use Each Distribution Path
Path 1: Use Internal TestFlight When...
- You just compiled a new build and want to test it immediately on physical iPhones without waiting for Apple review.
- You need to debug crash logs, push notifications, or camera/sensor integrations with up to 100 internal team members.
- You are actively iterating and uploading multiple builds per day.
Path 2: Use External TestFlight When...
- You want to run a public beta campaign (using a TestFlight Public Link) with up to 10,000 real users.
- You need to gather feedback on usability, edge cases, and performance before commercial release.
- You want users to test StoreKit In-App Purchases without paying real money (TestFlight purchases always execute in Apple's sandbox environment for free).
Path 3: Use the Public App Store When...
- Your application is feature-complete, stable, and ready for commercial distribution.
- You want users to discover your app via App Store search and category listings.
- You are ready to process real transactions, subscriptions, and upfront app purchases through StoreKit.
Orchestrating Both Paths with FlightDeck Prompts
FlightDeck allows you to manage both TestFlight beta distribution and App Store production releases using natural-language instructions.
Workflow A: Adding a Processed Build to TestFlight
Follow this 10-step protocol to discover, inspect, and stage a build for TestFlight distribution:
Using FlightDeck:
1. Discover our intended app and list its current builds.
2. Identify the latest uploaded build and inspect its processing and compliance status.
3. List our available TestFlight beta groups and confirm whether our internal or external group exists.
4. Determine whether Apple Beta App Review is required for this build.
5. Explain any outstanding prerequisites (e.g. export compliance or missing test notes).
6. Show the proposed build-to-group association.
7. Stage the group association for my developer review in the Approval Center.
8. Do not submit to public App Store review.
9. Execute only after I approve the staged mutation card in FlightDeck Desktop.
10. Read back the updated beta build state and confirm tester access.
What FlightDeck Executes
- Queries
apps_listandbuilds_listto identify the most recent build inVALIDstate. - Queries
beta_groups_listto find target group identifiers. - Stages a
build_add_to_beta_groupcard in the Approval Center. - Once you click Approve Mutation, the mutation is dispatched to Apple.
- Issues a readback query to confirm that the build is attached and reports whether Beta App Review has been initiated or whether internal testers can install immediately.
Workflow B: Staging an App Store Production Release Draft
When you are ready to prepare a public production release:
Using FlightDeck, inspect our editable App Store version draft for [App Name]. Attach our tested build [Build Number], populate the English (US) release notes with our changelog, and run a pre-flight readiness audit. Do not submit to Apple yet.
What FlightDeck Executes
- Queries
app_store_versions_listto find the editable version draft (or creates one viaapp_store_version_create). - Associates the specified build using
release_build_select. - Updates storefront release notes using
app_store_version_localization_update. - Executes
release_readiness_checkto verify that all screenshots, support URLs, and privacy declarations are complete.
Common Misconceptions and Critical Gotchas
Gotcha 1: The 90-Day Build Expiration Cliff
Every TestFlight build automatically expires 90 days after its upload timestamp. When a build expires:
- Testers cannot install or update to it.
- Testers who already have it installed will see the app crash or display an expiration dialog upon launch.
- If you use TestFlight for long-term beta testing, your AI assistant can help you re-upload fresh builds periodically to reset the 90-day counter.
Gotcha 2: In-App Purchases Never Charge in TestFlight
In-App Purchases and Auto-Renewable Subscriptions are completely free in TestFlight. Apple automatically routes all StoreKit transactions in TestFlight to the Apple Sandbox environment. Testers will see a standard system confirmation dialog labeled [Environment: Sandbox], and no charges are applied to their Apple ID.
Gotcha 3: Prohibited "Beta" References in App Store Metadata
While TestFlight encourages release notes detailing beta bugs, Apple's Guideline 2.2 strictly forbids references to "beta," "test," or placeholder text in your public App Store title, subtitle, or description. Always review your public storefront metadata to ensure test terminology is removed.
Decision Flowchart: Choosing Your Release Route
Is this build meant for public, commercial App Store launch?
│
├── NO ──► Do you need immediate testing on your own team's devices?
│ │
│ ├── YES ─► Distribute via Internal TestFlight (No Beta Review; Processing Required; Max 100 Testers)
│ └── NO ─► Distribute via External TestFlight (Beta App Review, Max 10,000 Testers)
│
└── YES ─► Has the build been tested on real devices and cleared Pre-Flight Readiness?
│
├── NO ─► Deploy to TestFlight first; run release_readiness_check
└── YES ─► Create Review Submission Draft; Stage for App Review in Approval Center
Related Guides
- Automating TestFlight Beta Distribution with an AI Agent — Full beta distribution pipeline.
- How to Retract or Expire a Broken TestFlight Build Immediately — Managing build retirement.
- Pre-Flight App Store Submission Readiness Check — Verifying submission completeness.
- From Vibe Coding to App Store: The Complete Step-by-Step Publishing Guide — End-to-end publishing tutorial.