Before you submit the app to App Store review.

Product readiness

• The first-run experience explains the value without relying on test data.
• Every primary flow has empty, loading, failure and retry states.
• Links to privacy, support and terms open real public pages.
• If users create accounts, account deletion is available where required.
• Placeholder text, debug menus and development credentials are removed.

Technical release

• The production bundle identifier, signing team and capabilities are correct.
• The archive uses the intended production environment and API endpoints.
• Crash reporting and essential diagnostics respect consent and privacy choices.
• Push notification, universal link, background mode and associated-domain entitlements match the shipped features.
• The app was tested on the smallest supported screen and current iOS versions.

Privacy and permissions

Permission prompts need clear usage descriptions and should appear only when the user starts a feature that needs access. App Privacy answers must match the actual SDKs and data flows in the binary. Review third-party analytics, advertising, login and payment libraries rather than describing only your own code.

Subscriptions and purchases

• Products are created, cleared for sale and attached to the submitted version.
• Prices, billing periods, trial terms and renewal language are visible before purchase.
• Restore purchases works for a returning customer.
• Expired, refunded and revoked entitlements produce a sensible state.
• A reviewer can reach and test the paywall without hidden setup.

Store listing

• App name, subtitle and description explain the real use case.
• Keywords do not repeat the app name unnecessarily.
• Screenshots show shipped screens and readable benefits.
• The support URL reaches a page with a working contact method.
• Category, age rating, copyright and content rights are accurate.

Review access

If sign-in is required, provide a stable review account and explain any non-obvious path. If the product depends on hardware, location, a paid service or a specific role, add concise notes and a demonstration video when useful. Reviewers should not have to guess how to reach the core feature.

Release strategy

Choose manual release when timing matters or when marketing and support teams need coordination. Phased release reduces exposure for automatic updates, but it does not replace monitoring. Prepare a rollback or hotfix decision path before the release becomes urgent.

After approval

• Run a production smoke test from the public App Store build.
• Watch crashes, authentication, purchases and the core API flow.
• Confirm analytics events arrive without collecting unnecessary data.
• Capture user friction for the first maintenance release.