The App Store Launch Checklist for Solo Founders

A first submission fails on small, boring things. This is the list, in the order that avoids the most rework.

1. Account and legal (start here, it is the slowest part)

• Apple Developer Program membership, $99 per year. Individual enrolment is usually same-day; organisation enrolment needs a D-U-N-S number and can take one to two weeks.
• Paid Applications agreement signed and banking plus tax forms completed in App Store Connect. Without this you cannot sell anything.
• Small Business Program enrolment if you earn under $1m — this is the difference between 15% and 30%.
• A published privacy policy at a stable URL. Required, and checked.

2. The listing

• App name (30 characters) and subtitle (30 characters). Both are indexed by App Store search — use the words people actually type, not a slogan.
• Keyword field, 100 characters, comma separated with no spaces and no repetition of words already in the name.
• Description. The first three lines are all most people read.
• Screenshots for 6.9" and 6.5" iPhone displays. Captioned screenshots outperform bare device shots almost every time.
• 1024x1024 icon, no transparency, no rounded corners applied by you.
• Support URL and marketing URL.

3. Privacy answers

• Complete the privacy questionnaire honestly — analytics, email addresses, crash logs all count as collection.
• Add usage strings for every permission the app requests. A missing NSUserTrackingUsageDescription or camera string is an instant rejection.
• Account deletion must be available in-app if users can create an account.

4. Monetisation

• Create the products in App Store Connect and attach them to the build. Every product must reach "Ready to Submit".
• Localised pricing, trial or introductory offer configured deliberately rather than by default.
• A restore purchases control that a reviewer can find without an account.
• Subscription terms, price and renewal behaviour stated on the paywall itself, plus links to terms and privacy. Missing this is the most common paywall rejection.

5. Review readiness

• A demo account that still works next week, in the App Review Information field.
• Review notes explaining anything non-obvious, including how to reach gated features.
• The app must do something native. See guideline 4.2.
• Test on a real device over cellular, not just simulator on wifi.

6. Release

• Choose manual release so you control the moment it goes public.
• Plan for review timing with slack for one rejection.
• Have the first push notification campaign and the first update ready before launch day, not after.

Shortcut

Wanilla does all of the above as a managed launch — the native build, the assets, the privacy answers, the subscription setup and the submission — typically within four working days. See how it works.