What Do You Need Before Submitting an iOS App?

The central idea: Focus on the hidden blockers that delay first submissions: incomplete metadata, broken login, privacy information, screenshots, support URLs and review notes.

Key facts

• Apple Developer Program membership is currently $99 per membership year; a free account can still support learning and personal device testing. Verify the current fee when planning “what do you need before submitting an ios app.”
• Apple currently states that 90% of App Store submissions are reviewed in less than 24 hours on average, although incomplete or complex submissions can take longer.

Primary references checked for “what do you need before submitting an ios app” include Publishing workflow in App Store Connect, Apple App Review, App Review Guidelines.

Rehearse the reviewer journey

The strongest pre-submission test is not “does it work on my phone?” It is “can a reviewer with no background knowledge install this build and reach every important feature?”

Use a clean device or clean install. Create a fresh account. Test expired sessions. Test subscription restoration if relevant. Open every legal/support URL in a logged-out browser. If the app needs hardware, location, a special account or a particular sequence, explain that in App Review Information.

A short, precise review note is more useful than a marketing paragraph. Tell the reviewer what they need to access, what credentials to use and what unusual behavior is intentional.

Step-by-step: What Do You Need Before Submitting an iOS App?

1. A complete review package reduces avoidable delay.

For this submission workflow, reproduce the flow from a clean install with no developer-only assumptions. If a reviewer needs a credential, special state or explanation, provide it directly in App Review Information and verify that the credential still works.

2. Reviewers need access to gated features.

For this submission workflow, reproduce the flow from a clean install with no developer-only assumptions. If a reviewer needs a credential, special state or explanation, provide it directly in App Review Information and verify that the credential still works.

3. Metadata must describe what the app actually does.

When working on “what do you need before submitting an ios app,” treat the listing as part of the product funnel. The promise in the title/subtitle and first screenshots should match the first-use experience. A higher rank for a mismatched promise can actually create worse conversion and retention.

4. Privacy disclosures must match real data collection.

Verify the public URL and the actual behavior it describes. Privacy disclosures, account behavior and support information should reflect the shipped app, not an old template or future roadmap.

What to measure

Common mistakes

• Submitting before login/demo access works. Confirm the bottleneck with a relevant baseline before acting.
• Using misleading screenshots. Confirm the bottleneck with a relevant baseline before acting.
• Forgetting account-deletion flows where applicable. Confirm the bottleneck with a relevant baseline before acting.
• Skipping a clean install test. Confirm the bottleneck with a relevant baseline before acting.

Execution plan