Mohamed Elgohary Release checklist
Release checklist
Before you ship an app or an update.
What to check before an iOS or Android release, from the build to the first days after launch. Tick items off as you go; your progress stays in this browser.
Store rules checked against Apple’s and Google’s pages on 28 September 2026. They change, so follow the linked official pages before you submit.
01 Build and versioning 0/5
02 Testing 0/7
Real devices, oldest to newest At least the oldest OS version you support, the newest one, a small screen and a large one.
Upgrade from the version people have now Install today’s store version, create some data, then update: sessions, saved settings and local data must survive.
Slow, offline and flaky network Loading, retry and error states work, and a repeated request never creates a duplicate order or payment.
Every permission, including “Don’t Allow” Camera, location, notifications: the app keeps working and explains why when access is refused.
Arabic, right-to-left and large text Mirrored layouts, mixed Arabic and English text, and the system font size at its largest.
A regression pass on the flows that matter most Sign-up, sign-in, checkout or booking — and anything a support call would be about.
Notifications and deep links open the right screen From a closed app, from the background, and when signed out.
04 App Store 0/8
Built with the required SDK Since 28 April 2026, iOS and iPadOS apps uploaded to App Store Connect must be built with the iOS 26 SDK or later, which comes with Xcode 26. Official page — Built with the required SDK (opens in a new tab)
App Privacy details match what the app collects Including what your SDKs collect — analytics, crash reporting and ads. Official page — App Privacy details match what the app collects (opens in a new tab)
The privacy manifest gives a reason for each required-reason API APIs such as UserDefaults and file timestamps need an approved reason in a privacy manifest, including uses inside third-party SDKs. Since 1 May 2024, App Store Connect doesn’t accept apps that leave them out. Official page — The privacy manifest gives a reason for each required-reason API (opens in a new tab)
A working demo account for App Review If the app has a login, give App Review an active demo account and keep your backend on during review. A built-in demo mode needs Apple’s prior approval, and only when legal or security obligations rule out a demo account (guideline 2.1(a)). Official page — A working demo account for App Review (opens in a new tab)
Account deletion inside the app If people can create an account, they must be able to start deleting it from within the app — if a website finishes the deletion, link straight to that page. Only deactivating the account isn’t enough (guideline 5.1.1(v)). Official page — Account deletion inside the app (opens in a new tab)
An equivalent option next to social sign-in If the main account can be created with a third-party login such as Google or Facebook, also offer an equivalent privacy-focused option such as Sign in with Apple (guideline 4.8). Official page — An equivalent option next to social sign-in (opens in a new tab)
The encryption question is answered Set ITSAppUsesNonExemptEncryption in Info.plist to the right value, so App Store Connect stops asking on every build. NO is only for apps whose code and libraries use no encryption, or only exempt encryption. Official page — The encryption question is answered (opens in a new tab)
Phased release is on for updates Apple releases the update over 7 days to people with automatic updates on, and you can pause it for 30 days in total. Anyone can still update manually from the App Store. Official page — Phased release is on for updates (opens in a new tab)
06 Launch day and after 0/4
Want a second pair of eyes before release day?
I plan and run release testing for mobile apps, and prepare store submissions.