How to launch an app on the App Store and Google Play, step by step
How to launch an app comes down to seven steps: set up the store accounts in your company's name, test with real users, meet the technical rules of each store, write a listing that converts, fill in privacy and legal details correctly, pass review, and release in a controlled way. Most launch delays come from things that could have been prepared weeks earlier. This guide walks through each step for Apple's App Store and Google Play, with the current rules and the checks we run before every submission.
Store rules were read on 12 November 2026 on Apple's App Review Guidelines and App Review pages, Apple's notice on EU trader requirements, and Google Play Console Help pages on testing requirements and target API levels. Stores change their rules often: check the current pages before each launch.
Step 1: accounts in your company's name
Both stores publish apps under an account, and that account owns the listing, the ratings, the download history and the revenue. Create the accounts as an organisation, not as an individual, and in your company's name rather than your agency's. Both stores verify an organisation before it can publish, so start early, and add your agency as a user with the right role instead of handing over passwords.
The organisation account also matters on Google Play: personal accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in continuously for at least 14 days before they can apply for production access. That requirement alone can delay a launch by three weeks.
Step 2: test before the public does
- Internal testing. TestFlight on iOS and internal testing on Google Play get builds to your team within minutes.
- Closed beta. A group of real users from the target audience, for two to four weeks, with a simple way to report problems.
- Devices. The oldest supported phone, a small screen, a large screen, a tablet if you support one, both light and dark mode, large text sizes.
- Poor conditions. Slow network, no network, low battery, interrupted purchases, a phone that was offline for a week.
- Crash reporting and analytics in place before the beta, so problems are seen, not only reported.
Our mobile app testing service covers this phase, and the mobile app development process guide shows where testing fits in the whole project.
Step 3: meet the technical requirements
Google Play sets a minimum target API level. On 12 November 2026 its help page states that new apps and app updates must target Android 16 (API level 36) or higher, with exceptions for Wear OS, Android Automotive OS, Android TV and Android XR apps, and that existing apps must target Android 15 (API level 35) or higher to remain available to new users on newer Android versions. Apple sets its own minimum Xcode and SDK versions for new submissions; check its current requirements before each launch.
Beyond the minimums: app icons and screenshots in every required size, a stable bundle identifier, signing keys stored safely in your company's systems, in-app purchases configured and tested in the sandbox if you sell anything, and a support website and privacy policy that load.
Step 4: write the store listing
The listing is the sales page that decides whether a visitor installs. It has a few fields with strict length limits, and each one works hard:
- Name and subtitle (iOS) or short description (Google Play): what the app does, in the words people search for.
- Screenshots: the first two do most of the work. Show the result for the user, with a short caption, not the login screen.
- Preview video: optional, short, and showing the app itself in use.
- Description: benefits first, then features, then what is included in the paid tier.
- Keywords (iOS) and description text (Google Play) researched for real search volume in each target country.
- Localisation for every market you target; a listing in the local language converts better.
Step 5: privacy details, age rating and trader status
Both stores ask you to declare what data the app collects and why: App Privacy details on the App Store, the Data safety section on Google Play. The declaration must match what the app and every SDK inside it actually do, including analytics and advertising libraries. A mismatch is a common reason for rejection and, worse, a public statement that is not true. Your privacy policy and, for an EU audience, your GDPR documentation must say the same.
Apple's guidelines (section 5.1.1) state that if your app supports account creation, you must also offer account deletion within the app. Both stores ask for an age rating questionnaire. In the EU, Apple requires trader status under the Digital Services Act: starting 17 February 2025, apps without trader status have been removed from the App Store in the European Union until trader status is provided and verified. Apple's help page explains that Articles 30 and 31 of the DSA require it to verify and display trader contact information, including an address, phone number and email address, on App Store product pages in the EU. Use company contact details set up for the purpose.
Step 6: submit and pass review
Apple states that App Review typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours. Google Play reviews can take from hours to several days, longer for new accounts. The most frequent reasons for rejection are avoidable:
- Incomplete app. Apple's guideline 2.1 asks for final versions with all metadata and working URLs; placeholder text and temporary content must be removed.
- No access for the reviewer. If the app has account-based features, provide an active demo account or a fully featured demo mode.
- Too little functionality. Apple's guideline 4.2 on minimum functionality rejects apps that are little more than a website in a wrapper.
- Purchases and subscriptions without clear terms, a restore button, or links to the terms of use and privacy policy.
- Crashes on the reviewer's device, often on the newest OS version or an iPad.
If the app is rejected, read the message carefully, fix exactly what it says, and reply in the Resolution Center if something was misunderstood. A calm, specific reply often resolves a rejection faster than a new build.
Step 7: release in a controlled way
Do not release to everyone at once. Both stores let you release an update gradually (a phased release on the App Store, a staged rollout by percentage on Google Play). For the first version, choose a manual release after approval, so you control the day and can prepare announcements, support and monitoring. Watch crash rates, reviews and the key funnel (install, sign-up, first meaningful action, payment) daily for the first two weeks.
After the launch: the first weeks
- Answer every review in the first weeks, especially the negative ones; it shows future users someone is listening.
- Fix the first crash and the first confusion quickly; a fast first update builds trust in the stores and with users.
- Measure what matters: retention after one day, seven days and thirty days says more than downloads.
- Plan updates for each new iOS and Android version; see mobile app maintenance.
- Work on distribution: your website, newsletter, partners and search. The store alone rarely brings enough users.
How we launch apps
We run launches as part of every app development project, for iPhone and Android: accounts set up in your company's name, a pre-submission check against the current store rules, listing copy and screenshots, privacy declarations checked against the code, and a staged release with monitoring. We publish our own apps through the same process. The code, signing keys and store accounts are yours from the first day.
Questions people ask
How long does Apple's App Review take?
Apple states that App Review typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours. A rejection adds another round, so plan a launch date with at least a week of margin after the first submission.
Do we need testers before publishing on Google Play?
If the Google Play account is a personal account created after 13 November 2023, yes: the app must run a closed test with at least 12 testers opted in continuously for at least 14 days before you can apply for production access. Organisation accounts do not have this requirement, which is one more reason to publish under your company.
What is EU trader status in the App Store?
Under the EU Digital Services Act, the App Store asks every account to declare whether it is a trader. Since 17 February 2025, apps without trader status have been removed from the App Store in the EU until the status is provided and verified. A company publishing apps is a trader, and its contact details are shown to users in the EU.
Why do apps get rejected?
The most common reasons are crashes and incomplete features, missing demo credentials for the reviewer, placeholder content, privacy details that do not match what the app does, account creation without in-app account deletion, and apps that offer too little beyond a website. Each is avoidable with a pre-submission check.
Should the app be published under our company or the agency's account?
Under your company's account, always. The store listing, reviews, download history and payments belong to the account that publishes the app. Moving an app between accounts later is possible but slow. We publish in our clients' own accounts as a standard term.
Sources
- Apple, App Review Guidelines, sections 2.1, 4.2 and 5.1.1 (read 12 November 2026)
- Apple, App Review (read 12 November 2026)
- Apple, notice on trader requirements in the EU under the Digital Services Act (read 12 November 2026)
- Apple, App Store Connect Help, EU Digital Services Act trader requirements (read 12 November 2026)
- Google Play Console Help, testing requirements for new personal accounts (read 12 November 2026)
- Google Play Console Help, target API level requirements (read 12 November 2026)