App Store Connect & Submission

iOS Development — Production & Publishing

Chapter 6 · App Store Connect & Submission

A build that's already survived Chapter 5's own TestFlight round is genuinely close to done — but a TestFlight build and a real, public App Store listing are two different things. This chapter covers the real, remaining work: turning that tested build into an actual App Store Connect app record, complete with metadata, and submitting it for the real, full review.

Creating the App Record

Before any build can be uploaded for public release, App Store Connect needs a real app record — created directly from the same Bundle ID that Chapter 4's own App ID material already established, plus a unique SKU (an internal identifier only the developer ever sees) and the app's own public-facing name.

Required Metadata — Verified Against Apple's Own Documentation

App Name & Icon

The real, public identity shown on the App Store — the same real 1024×1024 icon source Chapter 1 already prepared

Description & Subtitle

What the app actually does, plus a short, real promotional subtitle shown near the name

Screenshots & App Previews

Real device screenshots and optional short video previews of the app in use

Keywords

Real search terms that determine what a user typing into the App Store's own search bar will find

Age Rating

A real, structured questionnaire about the app's own content, used to assign the correct real age category

Two Real Nutrition Labels

Verified directly against Apple's own App Store submission documentation, every App Store listing carries two real, structured disclosure labels — genuinely different in scope and requirement:

	Privacy Nutrition Label	Accessibility Nutrition Label
Requirement	Mandatory for every submission	Optional
What it discloses	Every real data-collection practice, including third-party code the app integrates	Real, specific accessibility features the app supports

A Real, Direct Payoff of Chapter 2

The Accessibility Nutrition Label is a real, verified App Store Connect field for disclosing exactly the kind of work Chapter 2 covered — VoiceOver support, Voice Control, larger text, captions. Every genuine accessibility improvement made back in Chapter 2 becomes something that can now actually be declared, visibly, on the app's own real public App Store listing.

A Real, Easy Mistake

The Privacy Nutrition Label must genuinely account for third-party code, not just first-party code written directly by the app's own developer — a real analytics SDK or ad framework bundled into the app still counts as a real data-collection practice that has to be disclosed, even though none of that specific code was written in-house.

Submitting for Review

With metadata complete and a real, already-TestFlight-tested build attached, the app is submitted for App Review — the real, full review every public App Store listing must pass, distinct from Chapter 5's own lighter-weight Beta App Review.

A Real, Practical Timing Note

Apple has generally guided developers to expect most review decisions within roughly a day or two, though the real, actual duration for any specific submission can vary — a genuinely useful reason to submit with real lead time before any hard external launch date, rather than assuming a same-day turnaround.

Hands-On Exercises

Exercise 1

Explain, in your own words, why the Privacy Nutrition Label must disclose third-party code's data practices, not just the app's own first-party code.

📄 View solution

Exercise 2

Explain, in your own words, how the Accessibility Nutrition Label directly builds on the real work described in Chapter 2, and why declaring it is genuinely different from simply having implemented it.

📄 View solution

Exercise 3

Explain, in your own words, why a real hard external launch date is genuinely risky to plan around a same-day App Review turnaround, and what a safer real approach looks like.

📄 View solution

Chapter 6 Quick Reference

An app record needs the real Bundle ID from Chapter 4, a unique SKU, and a public-facing name
Required metadata: name, icon, description, subtitle, screenshots, app previews, keywords, age rating
Privacy Nutrition Label — mandatory, must include third-party code's own data practices
Accessibility Nutrition Label — optional, a real, direct payoff of Chapter 2's own accessibility work
App Review is the real, full review — heavier than Chapter 5's own Beta App Review, with a genuinely variable real timeline