Shipping to the App Store without the drama

App Store review has a reputation for being unpredictable. In our experience, most rejections come from the same handful of avoidable mistakes. Make launch boring by handling them before you submit.

The pre-submission checklist

• Privacy answers match reality. The App Privacy details must reflect exactly what the app does. Mismatches are the most common rejection.
• Every screen survives a cold start. Reviewers open the app fresh, often offline. Empty states and first-run flows have to be complete.
• Sign-in isn't a wall. If anything works without an account, let reviewers see it without one.
• Metadata is final. Screenshots, description, and keywords are ready and consistent before the build goes up.

"Launch day should be the least eventful day of the project."

Treat release as engineering

We script the parts that can be scripted — builds, signing, uploads — so a release is a button, not a ritual. The repeatable path means we can ship updates often and confidently, and a rejection (rare) is a quick fix rather than a crisis.

Boring launches are a feature. They mean the interesting work already happened, in the build.