Skip to content
codebrix

Launch checklist

How to publish an app on the App Store and Google Play: the launch checklist

To publish an app on the App Store and Google Play, enrol in the Apple Developer Program and create a Google Play Console account, build against the current SDK rules, complete Apple's privacy details and Play's Data safety form, test through TestFlight and Play's testing tracks, then submit for review. New personal Play accounts must first run a 14-day closed test with at least 12 testers.

Apple fee
99 USD a year (Nov 2026)
Google fee
US$25 one-time (Nov 2026)
Play closed test
12 testers, 14 days (new personal accounts)
Accounts owned by
You, not your developer

Updated · By the Codebrix team

Step 1: Developer accounts and fees

Open both accounts in your own name or your company's name, never your developer's. Whoever holds the account controls the listing, the reviews and the revenue. Your developer can be invited as a team member. Fees and rules below were checked on Apple's and Google's sites in November 2026; check the linked pages before you pay, as they change.

Apple App StoreGoogle Play
Fee99 USD per membership year, or local currency where availableUS$25 one-time registration fee
Account typesIndividual or organisationPersonal or organisation
Organisation needsA legal entity (no trade names or branches), a D-U-N-S Number, a working website on your domain and a work email on that domainA D-U-N-S number
Seller name shownIndividuals: your legal name. Organisations: the organisation's nameDepends on the account type; see Google's account type page
Extra rulesTwo-factor authentication on the Apple Account; in India, enrolment is through the Apple Developer appPersonal accounts must verify access to an Android device and meet testing requirements; organisation accounts are required for finance, health, VPN and government apps

Step 2: Build to the current technical rules

  • Apple: from 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using the iOS 26 SDK (or the matching SDK for other Apple platforms).
  • Google: from 31 August 2026, new apps and app updates must target Android 16 (API level 36) or higher. Google offered existing apps an extension to 1 November 2026, which has now passed.
  • Both stores update these rules every year. Check Apple's Upcoming Requirements page and Google's target API level page before you start the build, not the week before launch.
  • If your app lets users create an account, both stores require a way to delete it. Apple requires account deletion inside the app (guideline 5.1.1(v)). Google requires an in-app path and a web link where users can request deletion of the account and its data.

Step 3: Privacy labels and the Data safety form

Apple: App Privacy details

  • Entered in App Store Connect by the Account Holder, an Admin or an App Manager.
  • You must declare data collected by you and by third-party partners whose code is in your app: analytics tools, ad networks and SDKs.
  • A publicly accessible privacy policy URL is required.
  • You are responsible for keeping the answers accurate. They can be updated at any time without submitting a new build.

Google: Data safety form

  • Required for every app published on Google Play, including closed, open and production tracks. Apps only on internal testing are exempt.
  • Covers data collected and handled through any third-party libraries or SDKs. Check each SDK provider's own Data safety guidance.
  • A privacy policy link is required even if the app collects no user data.
  • Includes questions on data deletion; apps with accounts must give the deletion web link here.

Make a list of every SDK in the app (analytics, crash reporting, payments, push, maps, chat) and what each collects, before you fill in either form. That list is the most common thing missing at submission time, and the forms must match what the app actually does.

Step 4: Review rules that commonly trip up first submissions

Our short summary of selected App Store Review Guidelines. Read the full guidelines before submitting.
GuidelineWhat it asksHow to prepare
2.1 App completenessFinal build, working URLs, and demo account details if the app has a login, with the back end switched onCreate a reviewer account with sample data; keep the server running during review
4.2 Minimum functionalityThe app must offer more than a repackaged websiteUse device features or app-only workflows; avoid a plain web view wrapper
4.8 Login servicesIf you use a third-party or social login, offer an equivalent option that limits data to name and email and lets users keep their email privatePlan this in design, not after rejection
3.1.1 In-app purchasePaid features, subscriptions or premium content inside the app must use in-app purchaseDecide the payment model early; it affects pricing and build time
5.1.1 PrivacyA privacy policy link in App Store Connect and inside the app; account deletion in the app if accounts existAdd both to the Must Have list

Google Play applies its own Developer Program Policies. The same preparation helps on both stores: a test account with data, a privacy policy that matches your forms, no placeholder content, and every link in the app working.

Step 5: Test tracks, and Play's closed-testing requirement

TrackWho can testNotes
TestFlight internalUp to 100 team members with App Store Connect rolesFor your own team during development
TestFlight externalUp to 10,000 invited testersThe first build for external testing must be approved by App Review
Play internal testingUp to 100 testers per appMay not be subject to standard Play policy or security reviews
Play closed testingOnly testers you add by email list or Google GroupThe track used for the new-account requirement
Play open testingAnyone, via Google Play or the shared linkTesters can send private feedback
  • Recruit more than 12 testers, say 15 to 20, so one person opting out does not restart your clock.
  • Testers should actually use the app. Collect their feedback; the application asks about your testing.
  • Put the closed test on the project plan as at least three weeks before your launch date: 14 days of testing plus up to a week of review.
  • Google states this requirement for personal accounts. If you are registering as a company anyway, check the current rules for organisation accounts before planning around it.

Step 6: Store listing and submission checklist

  1. App name, subtitle or short description, and full description written for people, not keywords.
  2. Screenshots for each required device size, showing the core features in order.
  3. App icon in the required sizes, matching the in-app icon.
  4. Category, age rating questionnaire answered, and content rights confirmed.
  5. Privacy policy URL, support URL and support email that someone monitors.
  6. App Privacy details and Data safety form completed and matching each other.
  7. Reviewer demo account with sample data, plus notes explaining anything unusual.
  8. In-app purchases or subscriptions created and submitted with the build, if used.
  9. Release option chosen: publish automatically on approval or release manually.
  10. Crash reporting and analytics confirmed working on the release build.

Apple says App Review typically reviews at least half of submissions within 24 hours and 90 per cent within 48 hours, and slower if a submission is incomplete. You can request an expedited review for a critical bug fix or a dated event, and appeal to the App Review Board if you think a rejection was wrong.

Who does what at launch

You hold the accounts, approve the listing text and accept the store agreements, because only the account holder can. Your development team prepares the builds, the SDK list for the privacy forms, the reviewer account and the screenshots, and handles any rejection.

When Codebrix builds a mobile app, store submission is part of the launch milestone and every account stays in your name. Our indicative range for an iOS and Android app is ₹2,50,000 to ₹9,00,000 ($9,000 to $33,000) over 8 to 20 weeks; the fixed quote comes after a discovery call. Read more about our mobile app development service, compare React Native and Flutter, or see the mobile app cost guide.

Frequently asked questions

How much does it cost to publish an app on the App Store and Google Play?

As of November 2026, the Apple Developer Program is 99 USD per membership year, or the local-currency equivalent where available, and Google Play charges a US$25 one-time registration fee. Eligible non-profits, educational institutions and government bodies can request an Apple fee waiver. Check both official pages before paying, as fees can change.

What is Google Play's 12 testers requirement?

Personal Google Play developer accounts created after 13 November 2023 must run a closed test before publishing to production. At least 12 testers must be opted in when you apply for production access, and they must have been opted in continuously for the previous 14 days. Google usually reviews the application within seven days.

How long does App Store review take?

Apple says it typically reviews at least 50 per cent of submissions in under 24 hours and 90 per cent in under 48 hours. Incomplete submissions take longer or fail review. You can request an expedited review for a critical bug fix or a release tied to an event you are directly associated with.

Should the developer accounts be in my name or my developer's?

Yours, or your company's. The account holder controls the listing, reviews, revenue and the ability to publish updates. If your developer holds the account, moving the app later is extra work and depends on their cooperation. Open the accounts yourself and invite your developer as a team member.

Do I need a privacy policy if my app collects no data?

Yes, on both stores. Google requires a privacy policy link with the Data safety form even when an app collects no user data, and Apple requires a privacy policy URL in App Store Connect and an easily accessible link inside the app. Have your legal adviser review it against what the app actually does.

Do I need an organisation account for a health or finance app?

On Google Play, yes: organisation accounts are required for financial products and services, health apps, VPN apps and government apps. Organisation accounts on both stores need a D-U-N-S number. Apple also shows an individual developer's legal name as the seller, so most businesses register as an organisation anyway.

Sources

  • Mobile apps

    A mobile app development company in India for iOS and Android

    Mobile app development company in India building iOS and Android apps with React Native or Flutter. Fixed quote, weekly test builds, store launch handled.

    Read more
  • Cost guide

    What does mobile app development cost in 2026?

    Mobile app development cost broken down: build drivers, our indicative ranges, Apple and Google store fees, recurring costs and how to get a fixed quote.

    Read more
  • React Native apps

    React Native app development: one Expo codebase for iOS and Android

    React Native app development company building iOS and Android apps from one TypeScript codebase with Expo, OTA updates and native modules where needed.

    Read more
  • Flutter apps

    Flutter app development for iOS and Android from a single Dart codebase

    Flutter app development company building iOS and Android apps in Dart from one codebase, with custom UI, vetted plugins and native code where needed.

    Read more
  • Comparison

    React Native vs Flutter: choosing a framework for your app

    React Native vs Flutter compared on UI, language, performance, hiring and cost, with a decision list and when to skip both for native apps.

    Read more
  • Hire developers

    Hire React Native developers for your iOS and Android team

    Hire React Native developers who work in your repo and release pipeline. Expo and New Architecture skills, a paid first milestone, and you own the code.

    Read more
Estimate Call WhatsApp