App Stores
Apple reviews your app like a strict school teacher.
▶ the lesson · narrated sketch video · tap for sound
the intro
Shipping to the stores is a process: builds with the right signing, screenshots and descriptions for the listing, then review. Apple’s review is famously strict; Google is faster. Tools like EAS Build and TestFlight make the loop humane.
fun fact ✦
The App Store opened in 2008 with just 500 apps. Now it reviews millions.
the docs
the deep dive
the ideas behind the video — concepts, diagrams, a walkthrough and the traps to avoid
An app store is three businesses wearing one logo: a gatekeeper that reviews your binary, a CDN that distributes it, and a trust mark that makes strangers willing to install you. The review is the tax — you pay it on every single build, in exchange for distribution you could never run yourself. Learn the paperwork once and review becomes boring, which is exactly the goal.
distribution with a toll booth
key terms
code signing
Every build is cryptographically signed with your keys. The store verifies it is really you.
keystore + provisioning profileversionCode
The integer the store uses to order builds. It only goes up; humans never see it.
versionCode: 14, next: 15TestFlight
Apple's beta lane: invite up to 10,000 external testers without a full App Store review.
100 internal testers, instantphased release
Ship to a growing slice of users — 1, 2, 5, 10 percent — and halt if crash rates spike.
1% → 100% over 7 dayshow it works
- 1Enroll and sign
Apple is $99 a year, Google $25 once. Create the signing keys the store will trust.
- 2Build in the cloud
EAS Build compiles the binaries with the right credentials, so your laptop stays out of it.
- 3Craft the listing
Screenshots and the first line do the selling. Show the app doing the core thing.
- 4Do the paperwork
Privacy labels, data safety forms, and a working demo login — most rejections live here.
- 5Submit, then stage it
Send for review, then roll out gradually. Watch the crash rate before you hit 100%.
the code, explained
two numbers, two audiences: machines count the build, humans read the version
side by side
App Store
- human review, famously strict
- about 90% reviewed in 24 hours
- $99 per year to ship
- rejections cite guideline numbers
Google Play
- faster, more automated checks
- new accounts: 12 testers first
- $25 once, then free
- data safety form is required
Builds get rejected for boring reasons: a privacy policy URL that 404s, a demo account that does not log in, screenshots of features that no longer exist. Reviewers test with fresh eyes and zero context, so before submitting, wipe-install your own build and walk the reviewer's path.
quick answers
How long does review take?
Apple publishes that 90% of apps are reviewed within 24 hours; budget one to three days to be safe. Google is usually faster, but brand-new developer accounts wait first.
Do updates go through review again?
Yes, every new binary. Pure web-content updates (Expo Updates OTA bundles) skip the store within Apple's limits — use them for fixes, not for changing what the app is.
My build was rejected — now what?
Read the cited guideline number, fix exactly that, reply in Resolution Center, and resubmit. Crashes on launch, missing privacy disclosures, and broken links cause most first rejections.
quick hits about App Stores
short answers · interviews, tips, trivia & hidden gems