App Launch Guide

How to Launch an App on the App Store and Google Play

To launch an app on the App Store and Google Play, enroll your company in both developer programs, prepare listings and privacy disclosures, beta test through TestFlight and a Google Play testing track, submit for review with a working demo account, and release in stages. Tepia handles submissions under accounts your company owns and reserves about a month for launch, including review and staged rollout.

The essentials at a glance

Most launch delays come from accounts, privacy disclosures and review notes, not from the code.

dream-app

Your Accounts

Tepia submits under developer accounts your company owns, enrolled as an organization, so the listing never depends on an agency login.

Read: App Store and Google Play Rejection Fixes
connect-audience

Reviewers Prepared

Tepia supplies a demo account, review notes and sample data, so an app behind a login is never rejected because a reviewer got stuck.

Read: How to Develop an App From Idea to Launch (12 Steps)
smart-product

Privacy Declared

Apple's privacy details and Google's Data safety form are completed from an audit of every SDK in the build, not from memory.

Read: Mobile App Release Management and Continuous Delivery
optimize-ecommerce

Staged Release

Releases use Apple's phased release and Google's staged rollout, so a crash reaches a small share of users before it can spread.

The numbers matter.

Store figures Tepia plans around when launching mobile apps.

90%

Reviewed Within 48 Hours

Apple states that App Review typically reviews 90 percent of submissions in less than 48 hours and at least half within 24 hours.

1 in 4

Submissions Rejected

Apple's 2024 App Store Transparency Report shows 1.9 million of 7.8 million submissions were rejected, about 1 in 4.

90%

Adults With Smartphones

Pew Research Center reports about 90 percent of US adults own a smartphone, so most of your audience can install on launch day.

Before you submit: accounts and ownership

Launching starts weeks before the build is ready. Enroll your company in the Apple Developer Program as an organization, which requires a DUNS number and a verified legal entity, and create a Google Play developer account in the organization’s name. Verification on either side can take days or weeks, so Tepia asks clients to start during development rather than in launch week.

Organization accounts matter for more than speed. Your company appears as the seller on the listing, team members can be invited with specific roles, and the app never depends on one person’s login. Google also applies stricter testing rules to newer personal accounts, including a closed test before production access. Tepia publishes every client app under accounts the client owns, which also makes any future change of vendor painless.

Step by step: from finished build to live in both stores

  1. Reserve the name and identifiers. Create the app record in App Store Connect and Play Console, set the bundle ID and package name, and confirm the name is available.
  2. Complete privacy disclosures. Fill in Apple’s App Privacy details and Google’s Data safety section based on what the app and every SDK collect, and publish a privacy policy URL.
  3. Answer content and audience questions. Complete Apple’s age rating questions, Google’s content rating questionnaire and the target audience settings.
  4. Prepare the store listings. Write the name, subtitle, description and keywords, and produce screenshots for the required device sizes plus an optional preview video.
  5. Beta test. Distribute through TestFlight internal and external groups and a Google Play internal or closed testing track, and fix what testers find.
  6. Prepare review materials. Provide a working demo account, notes explaining any hardware, location or login requirements, and sample content so reviewers can reach every feature.
  7. Submit for review. Upload the iOS build from Xcode or your CI pipeline to App Store Connect and an Android App Bundle to Play Console, then submit both.
  8. Release in stages. Choose manual release on approval, then use phased release on iOS and a staged rollout percentage on Google Play while watching crash reports.

Tepia keeps a launch checklist for every client app and pushes a beta build through the same steps early, so account or listing problems surface well before the real launch date.

Common rejection reasons and how to avoid them

Most rejections are predictable. Tepia checks each of these before every first submission.

Issue Store How to prevent it
Crashes or broken links during review Both Test the exact build on physical devices and check every link in the listing
Reviewer cannot log in Both Provide a demo account with data and explain any two factor step
App is a thin website wrapper Apple Add native value such as offline access, push notifications or device features
Account creation without in app deletion Apple Let users delete their account from inside the app
Third party login without a private option Apple Offer Sign in with Apple or another login that meets Apple’s privacy rules
Digital goods sold outside in app purchase Apple Use in app purchase for digital content and subscriptions where the rules require it
Data safety form does not match SDK behavior Google Audit analytics and advertising SDKs before filling in the form
Vague permission requests Both Explain camera, location or contacts use in plain words in the prompt

If you are already stuck in a rejection loop, see App Store and Google Play rejection fixes.

After approval: rollout, monitoring and the first update

Approval is not the finish line. Apple’s phased release spreads an update to users with automatic updates over seven days, and Google Play’s staged rollout lets you choose the percentage of users who receive it; both can be paused if crash rates climb. Tepia releases first launches and major updates this way by default.

Watch these closely in the first two weeks:

  • Crash free sessions in Crashlytics or Sentry, broken down by device and OS version.
  • Store ratings and review text, with replies within a day.
  • The funnel from install to signup to first key action, set up through app analytics implementation.
  • Push notification opt in rates, which depend heavily on when you ask.

Plan the first update before launch. A small release two to three weeks later fixes what real users find and shows customers the app is maintained. Tepia’s release management practice sets up the CI pipeline so updates ship on a steady rhythm.

How Tepia approaches app launches

Launch preparation runs through all six of Tepia’s phases, not just the last one.

  1. Discovery: confirms account ownership, target OS versions and devices, features that touch sensitive review rules such as payments, location or health data, and every third party SDK. Deliverables include the Investigation Summary, Interview Summary and User Stories that the store listing later describes.
  2. Design: store screenshots, icon and preview video designed alongside the app, using the same style guide and wireframes.
  3. Development and Testing: Alpha builds through TestFlight and an internal testing track, Beta builds for a closed group of real users, and test plans for functional, user acceptance and non functional checks such as performance on older devices.
  4. Training: sessions for your team on App Store Connect, Play Console, replying to reviews and reading crash reports.
  5. Launch: privacy disclosures, listings, review notes, submission, phased release and support reps monitoring the first days.
  6. Support: issue resolution, bug tracking, readiness for each annual iOS and Android release, and feature requests for the next versions.

On a full build, Discovery typically takes 1 to 3 months and development and QA 2 to 6 months, and Tepia reserves about a month for launch itself. See our process, the full guide to developing an app, or ask Tepia to review your launch plan.

Frequently asked questions

How long does App Store review take?
Apple states that App Review typically reviews at least half of submissions within 24 hours and 90 percent within 48 hours, though first submissions and rejections add time. Tepia plans about a month for launch so review, fixes and staged rollout fit comfortably.
Do we need a DUNS number to publish an app?
Organizations enrolling in the Apple Developer Program need a DUNS number, and Google Play verifies organization details for business accounts as well. Tepia recommends starting enrollment during development because verification can take days or weeks.
Why do apps get rejected from the App Store?
Common reasons are crashes during review, reviewers unable to log in, missing in app account deletion and privacy disclosures that do not match the app’s behavior. Tepia checks each of these before every first submission.
Should our app be published under our account or the developer’s?
Under yours. Tepia publishes client apps under developer accounts the client owns as an organization, so the listing, ratings and users stay with your company if vendors change.
Can we release an app update to only some users first?
Yes. Tepia uses TestFlight and Google Play testing tracks before launch, then Apple’s phased release and Google’s staged rollout so each update reaches a small share of users first.

What Our Customers Say.

A paragraph or two with information on your product/service or describes a problem your product/service is designed to solve.

Jascotina

CEO

“They customized the website’s backend to my business' specific needs and I am absolutely thrilled with the result.”

Water Saver Solutions

Senior Project Manager

"Tepia Co was always willing to go the extra mile for us."

Onward Engineering

VP & Operations Manager

"There are no hidden things, there are no surprises. We know what's going on."

Launch on both stores without surprises