Submission
Build and required metadata
Prepare technical, legal and product-page information together.
Use these guides to prepare App Store assets, reduce preventable review problems and coordinate the first weeks around an iOS launch.
Direct answer
Publishing an iOS app requires a valid developer account, a tested build, complete App Store Connect information, review-ready privacy details and a deliberate release plan. This hub separates submission requirements from launch and growth work.
Submission
Build and required metadata
Prepare technical, legal and product-page information together.
Review
Evidence and completeness
Test review paths and explain non-obvious functionality.
Launch
Baseline before changes
Record metadata, keywords and rankings before promotion begins.
| Resource | Why it matters | Open |
|---|---|---|
| Apple Developer News | Recent official updates relevant to App Store teams. | Open |
| Free Metadata Analyzer | Audit public listing fields and storefront signals. | Open |
| New Releases | Inspect recently observed releases and category context. | Open |
| App Store Rankings Hub | Create a ranking baseline for the launch period. | Open |
Published articles in this topic, reviewed by Tobias Krenn.
Publishing and App Review · 5 min read
You need a production-ready build, Apple Developer Program membership, App Store Connect setup, required metadata/privacy information, screenshots, reviewer access where needed and a release configuration.
Read guidePublishing and App Review · 5 min read
Apple supports individual developers. An LLC is not a universal Apple requirement; choose account/entity structure based on ownership, public seller identity and business needs.
Read guidePublishing and App Review · 5 min read
Apple supports individual developers. An LLC is not a universal Apple requirement; choose account/entity structure based on ownership, public seller identity and business needs.
Read guidePublishing and App Review · 5 min read
Apple supports individual developers. An LLC is not a universal Apple requirement; choose account/entity structure based on ownership, public seller identity and business needs.
Read guidePublishing and App Review · 5 min read
A clean first submission combines a stable build with complete metadata, correct privacy/age information, working reviewer access, accurate screenshots and enough schedule buffer.
Read guideiOS App Launch · 5 min read
Prepare product quality, TestFlight feedback, ASO, conversion assets, analytics and support before release; use launch week to learn which part of the funnel needs work.
Read guideiOS App Launch · 5 min read
Prepare product quality, TestFlight feedback, ASO, conversion assets, analytics and support before release; use launch week to learn which part of the funnel needs work.
Read guideiOS App Launch · 5 min read
Prepare product quality, TestFlight feedback, ASO, conversion assets, analytics and support before release; use launch week to learn which part of the funnel needs work.
Read guideiOS App Launch · 5 min read
Prepare product quality, TestFlight feedback, ASO, conversion assets, analytics and support before release; use launch week to learn which part of the funnel needs work.
Read guidePrepare a tested build, app information, privacy answers, product-page assets, support details and any review credentials or explanatory notes.
No. Review timing varies by app and context, so teams should plan buffer rather than promising a fixed review duration.
Create a baseline before the listing changes or promotion begins so later movement can be compared with a known starting point.
Use current first-party Apple Developer and App Store Connect documentation because requirements can change.