Google Play and App Store Launch Checklist for 2026

To launch an app on Google Play and the App Store in 2026, start eight weeks out: set up store accounts in the company's name, begin Google Play's mandatory 14-day closed test with at least 12 testers if you use a newer personal account, meet the Android 16 and Xcode 26 build requirements, complete privacy and health declarations, and build in-app account deletion. Most first launches slip because one of these surfaces late, not because the code is unfinished. The checklist below is ordered by when each task should start. Rules change often, so verify each item in the console on the day.

What should you set up eight weeks before launch?

Set up both store accounts in the business's legal name, complete identity verification and add payment and tax details. Account ownership is the hardest thing to fix later.

• Choose individual or organisation. Organisation accounts keep the asset with the business and avoid the personal-account testing rule below. Never let a freelancer or agency own your listing.
• Google Play Console: pay the one-time US$25 registration fee and complete identity verification. Google does not accept prepaid cards, and the fee is not refunded if your identity information is found invalid.
• Apple Developer Program: enrol at US$99 per year. Organisation enrolment takes longer because Apple verifies the legal entity, so start early.
• Payments and tax: set up payments profiles, bank details and tax information in both consoles if you sell anything.

How does Google Play closed testing work for new accounts?

Personal Play accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in continuously for 14 days before applying for production access. Organisation accounts are not subject to this rule.

The 12 testers, 14 days rule

This catches most indie developers and startups. Per Google's testing requirements, testers must be opted in for the preceding 14 days; anyone who opts out early does not count. After the test, you answer questions about it and Google reviews the application, which adds time.

Practical advice: recruit 15 to 20 real testers rather than the bare minimum, ask them to keep the app installed and use it, collect feedback in a simple form, and ship at least one update during the test that responds to what they said.

TestFlight for iOS

Apple has no equivalent mandatory test, but use TestFlight anyway. Internal testers get builds quickly; external testers need a lighter beta review. Test on the oldest iPhone you intend to support.

Which technical requirements apply in 2026?

Android apps must target API level 36 and ship as signed App Bundles; iOS apps must be built with Xcode 26 and include privacy manifests for listed third-party SDKs.

• Android target API level: from 31 August 2026, new apps and updates must target Android 16 (API level 36) or higher, with lower levels for Wear OS, Automotive, TV and XR. Extensions could be requested only until 1 November 2026. Existing apps must target at least API 35 to stay available to new users on newer Android versions.
• Android App Bundle and signing: upload an AAB and enrol in Play App Signing. Back up your upload key somewhere other than one laptop.
• iOS build tooling: since 28 April 2026, App Store Connect uploads must be built with Xcode 26 or later using the iOS 26 SDK. From 9 September 2026, iOS and iPadOS apps must also target iOS 13 or later.
• Privacy manifests: since 1 May 2024, Apple requires privacy manifests, approved reasons for "required reason" APIs and valid signatures for newly added SDKs on its list of commonly used third-party SDKs. A privacy manifest declares what data an app or SDK collects and why it uses certain system APIs. Apple says the requirement will expand to the whole app binary, so declare your own uses too.
• Performance on real devices: test cold start, app size and memory on an entry-level Android phone. In India, Android held 94.84% of mobile OS usage in October 2026 according to StatCounter, and much of that audience uses budget handsets.

Which privacy and policy declarations do the stores require?

Both stores require a privacy disclosure on the listing, a privacy policy URL, account deletion and a content rating. Google also requires a health apps declaration from every app and in-app reporting for AI output.

• Privacy nutrition labels must cover data collected by your code and every third-party SDK, whether each type is linked to the user, and whether it is used for tracking. If your analytics or ads SDK collects device identifiers, the label must say so. Ask each SDK vendor for its disclosure guidance, as Adjust publishes for its SDK.
• Account deletion: Google's deletion requirements apply if users can create an account anywhere in the app. Apple's guideline 5.1.1(v) says apps outside highly regulated industries should not make people call, email or use a support chat to delete.
• Health declaration: Google's health apps declaration separates "Stress Management, Relaxation, Mental Acuity" under Health and fitness from "Mental and Behavioral Health" under Medical. Choose honestly; it shapes review. Our article on responsible wellbeing apps goes further.
• Generative AI: Google's AI-generated content policy requires in-app reporting that users can reach without exiting the app. Build it as a real feature, not a hidden email link.

What India-specific points should you check before launch?

Plan for DPDP consent and deletion standards, consider Google user choice billing, complete SMS OTP registration, localise listings, and watch Android developer verification if you distribute APKs directly.

• DPDP readiness: India's DPDP Rules were notified in November 2025, and most duties on businesses, including notice, security safeguards, breach reporting and verifiable parental consent for children, apply from 13 May 2027, per Privacy Labs. Design consent screens and deletion flows to that standard now. Our DPDP compliance guide goes deeper.
• Billing: for digital goods, Google offers user choice billing to developers in India, with a 4 percentage point lower Play fee when users pay through the alternative system. Physical goods and services use your own gateway. Our app development cost guide covers commission rates.
• Android developer verification: Google opened registration to all developers in March 2026 and began enforcing it on certified devices in Brazil, Indonesia, Singapore and Thailand on 30 September 2026, with a global rollout expected in 2027, according to The Hacker News. If you distribute APKs directly, for example to field staff, register early.
• Localised listings: Play supports store listings per language. Translating the short description and screenshots into Hindi or a regional language can matter more than translating the app on day one. See our regional language content guide.
• OTP and SMS: if you use SMS one-time passwords, confirm sender ID and template registration with your provider before launch day, or logins will fail.

What should you do in launch week?

Finalise the listing, give reviewers working access, and release gradually so you can halt if crashes climb.

1. Final listing: title, short and full description, screenshots for each required device size, feature graphic, preview video if you have one.
2. Support email, website and privacy policy URLs live and correct.
3. Reviewer access: demo credentials and notes explaining non-obvious features, especially AI, payments or health content.
4. Staged rollout on Play and phased release on iOS.
5. Crash reporting and analytics verified on production builds, with consent handled correctly.
6. Review response templates, and one person reading reviews daily for the first two weeks.

Common mistakes we see: a Data safety form copied from an earlier build, a demo account that expires during review, and screenshots that show features not in the release.

What recurring store deadlines follow launch?

Store compliance is annual: a new Android target API deadline each August, a new Xcode and SDK minimum each spring, updated declarations whenever you add an SDK, and Apple membership renewal every year. Put them in a shared calendar owned by one person, and budget for them as maintenance.

How we approach this at Old Port

We treat store compliance as part of the build, not a task for launch week. On our projects the closed test starts as soon as a stable build exists, declarations are drafted from the actual SDK list rather than from memory, and the client owns every account from day one. We publish our own apps, including MindHarbor, so the same checklist runs on our releases. Our app development service covers store setup, testing tracks and declarations, and our SEO and GEO team can optimise listings for discovery. For apps launching in the Gulf as well, our UAE app development team follows the same process.