Mobile App Launch Checklist: What Changed Since 2020 and What to Fix First

Archi5 min read

mobileappsprivacycompliance

Contents
  1. The launch checklist is not the same one you used in 2020
  2. 1. Map every data collection point before you write the privacy labels
  3. 2. Declare permissions at the point of use, not at first launch
  4. 3. Audit third-party SDK privacy manifests
  5. 4. Test the subscription flow against current store rules
  6. 5. Set up crash and performance monitoring before the first build goes to testers
  7. 6. Verify account deletion and data export paths
  8. 7. Run a final build on the oldest supported OS version
  9. 8. Check the store listing against the binary
  10. 9. Schedule the release window around review times
  11. What to fix first

The launch checklist is not the same one you used in 2020#

Five years ago, a mobile app launch often meant a store listing, a privacy policy link, and a crash reporting SDK. The checklist was short because the platform rules were simpler and the tooling was less opinionated. In 2026, the same launch involves permission declarations, data safety forms, subscription disclosure rules, and a privacy manifest that Apple began enforcing in 2024. The work has not doubled, but the order matters more than it used to. Below is a practical checklist ordered by what breaks first if you skip it, with notes on how each item compares to the 2020 equivalent.

1. Map every data collection point before you write the privacy labels#

In 2020, a privacy policy was mostly a legal document. Today the store forms ask specific questions: which data types you collect, whether they are linked to identity, and whether they are used for tracking. Apple's App Tracking Transparency prompt and Google's Data Safety section both require answers that must match your actual code.

The common failure is a mismatch between the label and the SDK. Analytics and ad SDKs collect identifiers you may not have listed. Start by inventorying every SDK and every network call that leaves the device. Compare that list to your store forms. If a third-party SDK added a new data type in a recent version, the form is now wrong. Fix it before submission, not after a rejection.

2. Declare permissions at the point of use, not at first launch#

Five years ago, many apps asked for camera, location, and contacts access on first open. Users accepted it because the alternative was a nonfunctional app. In 2026, both stores penalize permission requests that appear before the user understands why they are needed. iOS requires purpose strings in Info.plist, and reviewers reject vague ones like "to improve your experience."

The checklist item: for each permission, write a one-sentence reason that names the feature. Then trigger the request only when the user taps that feature. This reduces denial rates and avoids the review flag that comes from a wall of permission dialogs on launch.

3. Audit third-party SDK privacy manifests#

This is the biggest new item compared with 2020. Apple requires privacy manifests for commonly used SDKs, and the list has grown since the requirement took effect. If an SDK you depend on does not include a manifest or a signature, your build can fail validation.

Practical step: list every SDK by version, check the vendor's documentation for a privacy manifest, and update anything older than the current major release. If a vendor has not shipped one, replace the SDK or isolate it. Do not assume the build will pass because it passed six months ago.

4. Test the subscription flow against current store rules#

Subscription rules have tightened every year since 2020. The store now expects clear pricing, a visible renewal term, and an easy cancellation path. A paywall that hides the annual price behind a toggle, or that defaults to the most expensive plan, draws scrutiny.

The checklist item is a manual test on a real device with a real sandbox account: purchase, upgrade, downgrade, cancel, and restore. Confirm that the price shown in the app matches the price in the store sheet. Mismatches are a common rejection reason and a common source of refund requests.

5. Set up crash and performance monitoring before the first build goes to testers#

In 2020, many teams added crash reporting after launch. In 2026, the first internal build should already report crashes, ANRs on Android, and slow screen loads. The reason is simple: store review can reject apps that crash on launch, and the fix cycle is faster if you see the crash before a reviewer does.

Use a staged rollout. Ship to 5% of users, watch the crash-free rate for 24 hours, then expand. A crash-free rate below 99.5% on the first day is a signal to pause, not to push forward.

6. Verify account deletion and data export paths#

Both stores now require apps that offer account creation to offer account deletion inside the app. This was not a universal rule in 2020. The checklist item is to test deletion end to end: the account, the server-side data, and any backup copies.

A related item is data export. If your app holds user-generated content, confirm that users can retrieve it. Reviewers have rejected apps that delete data without any export path when the app stores meaningful user content.

7. Run a final build on the oldest supported OS version#

Five years ago, supporting Android 8 and iOS 13 was common. The floor has moved, but the failure mode has not: a library that works on the latest OS can break on the oldest one you claim to support. Test on a physical device or a cloud device farm at the minimum OS version listed in the store.

8. Check the store listing against the binary#

The listing is part of the product. Screenshots that show features not in the build, or a description that promises a feature behind a waitlist, are rejection risks. Compare the listing text to the current build, update the screenshots if the UI changed, and confirm the age rating matches the content.

9. Schedule the release window around review times#

Review times vary, but the practical lesson from the past five years is that Friday releases leave you without support over the weekend if a rejection lands. Submit early in the week, keep a phased rollout plan, and have a rollback build ready. The store tools for staged rollout are better than they were in 2020, but they only help if the build is already approved.

What to fix first#

If you have limited time, fix the privacy labels and SDK manifests first. They are the items most likely to block a submission outright, and they take the longest to correct because they depend on third-party vendors. Permissions and subscription flows come next, then monitoring and staged rollout. The rest can follow in the first update after launch.

More articles