Launch
Founders often treat "submit to Apple" as the finish line of a launch. In practice it's closer to the midpoint. The store listing, the compliance pages, the beta test, and the review buffer all have their own lead times, and skipping any of them to hit a date usually costs more time later in the form of a rejection or a bad first-week rating.
We plan launch timelines backward from the date the app needs to be live, not forward from "whenever the code is done." A realistic runway from a feature-complete build to a live App Store listing is four to eight weeks, covering store assets, legal pages, a beta test cycle, submission, and a buffer for at least one round of review feedback. Compressing that window is possible, but it removes your margin for the inevitable first-submission note back from Apple.
The App Store Connect record needs more than an icon and a description. You need screenshots sized for each device class you support, an optional but high-converting app preview video, a 30-character subtitle, a 100-character keyword field (invisible to users, but the primary lever Apple's search algorithm reads), promotional text you can update without a new build, and a primary plus optional secondary category. The age rating questionnaire also feeds directly into what content and permissions Apple expects to see, so get it right the first time — changing it later can trigger a fresh review.
Your privacy policy URL and support URL both need to be live and reachable before submission — not "coming soon." The App Privacy nutrition label questionnaire in App Store Connect has to match what your app and its SDKs actually collect. There's also an export compliance question: most apps that only use standard HTTPS/TLS qualify for an encryption exemption, but you still have to answer the questionnaire accurately on every submission, and getting it wrong can hold up your build in "Waiting for Export Compliance."
Internal testing (up to 100 people on your team, no review required) should catch obvious breakage. External testing (up to 10,000 testers, requires a lightweight Apple review of the build itself) is where you find the crashes and confusing flows real users hit that your own team never would. Build processing after upload typically takes anywhere from a few minutes to over an hour depending on Apple's load — plan for that when you're testing close to a deadline.
Review turnaround varies and Apple makes no guarantees, though most submissions get a first response within a day or two. Give yourself buffer for at least one rejection-and-resubmit cycle regardless — even clean apps sometimes get a metadata note that needs a quick fix. You can also choose manual release, which lets an approved build sit ready until you flip the switch, useful if your launch is tied to a specific date, press embargo, or marketing push.
The work doesn't stop at "Ready for Sale." The first week is when you find out whether onboarding actually works for people who've never seen the app before, whether crash rates hold up under real device diversity, and whether App Store Connect's analytics (impressions, product page views, conversion rate, and early retention) are telling you anything you need to react to quickly.
Decide your price tier (or free-with-IAP structure) and which territories you're launching in well before submission — both are configured in App Store Connect and Play Console, and changing pricing globally after launch means navigating currency conversion tables Apple manages for you, or, on Android, adjusting per-territory prices manually if you've set them individually. If you're launching in a specific country first to test before a wider release, both stores support territory-limited availability, which is worth using deliberately rather than defaulting to "all territories" and discovering a market you weren't ready to support.
Because Apple doesn't guarantee a review turnaround time, committing to a hard public launch date before you have an approved build is a real risk. Manual release solves this cleanly: submit early, let the build sit in "Pending Developer Release" once approved, and only flip it live when your marketing, press, or partner timing is actually ready. This decouples "when Apple says yes" from "when the world finds out," which removes a surprising amount of stress from launch week.
Treat submission as one milestone in a longer sequence, not the deadline itself, and the actual launch tends to go a lot more smoothly.
More from the journal
App Store
Apple rejects a meaningful share of first-time submissions, and it's rarely the exotic reasons founders worry about. Here's what actually trips people up, and how to submit clean.
Engineering
Cross-platform frameworks have closed most of the historical gap with native — but not all of it. Here's the actual decision framework, not a philosophy war.
Strategy
Most first-time founders overscope their MVP by two or three features. Here's how to find the smallest version that actually tests your idea.