Prepare an iOS release on the App Store
Steps and best practices for publishing an App Store update — with HyperRelease.
Publishing on the App Store involves more than uploading a build: metadata, screenshots, What's New notes, Apple review, and often multiple locales. HyperRelease structures that preparation without replacing App Store Connect.
Before submission
Build uploaded via Xcode or CI, TestFlight testing validated, metadata and screenshots up to date for each locale, release notes written. The HyperRelease checklist captures these prerequisites.
During Apple review
Review can take anywhere from a few hours to several days. The iOS status in HyperRelease reflects that wait — Ready for submission, then tracked through to Published.
After publication
Confirm the version is live, update the public changelog, and inform support. Status moves to Published in HyperRelease.
In summary
The App Store is demanding. HyperRelease does not shorten Apple review — but it ensures you never submit an incomplete release.
Read more
iOS propagation
HyperRelease documentation
Next article
Propagate content to Android with HyperRelease
HyperRelease propagation flow for Google Play Console.