1. Home
  2. Blog
  3. Apps

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

A step-by-step guide to publish an app on the App Store and Google Play: developer accounts, store listings, privacy forms, testing and common rejections.

Apps

To publish an app you need three things: developer accounts with Apple and Google, an app build with a complete store listing, and approval from each platform's review. The technical part is usually the fastest. What delays launches is company verification, the privacy policy and rejections for details you could have seen coming.

First: the right account, under the right name

Apple charges an annual fee for the Apple Developer Program and Google charges a one-time registration fee for the Google Play Console. Amounts and conditions change, so check the official pages before you set your budget.

The most important decision here is whose name the account goes under. If the app belongs to a company, the account should be an organization account registered to that company, not to an individual developer or to the agency you hired. The seller name shown in the store comes from that account, and moving an app to another account later is possible but bureaucratic.

Organization accounts go through verification. Both stores usually ask for the company's D-U-N-S number, a free international business identifier that can take several days to be issued. Request it at the start of the project, in parallel with development, so it does not become the bottleneck at the end.

Once the account is open, give your technical team access through each platform's user roles. That way nobody needs the owner's password, and access can be revoked when the contract ends.

What to prepare before you submit

Many rejections come from incomplete or inconsistent materials. Put this list together ahead of time:

  • App name, subtitle or short description, and full description.
  • Icon and screenshots in the sizes each store requires, for phones and, if relevant, tablets.
  • A privacy policy published on a public page of your website.
  • Data collection disclosures: the App Privacy section on the App Store and the Data safety section on Google Play.
  • The content rating questionnaire, answered honestly.
  • A support email and page that actually work.
  • A test account with sample data for the reviewer, if the app has a login.
  • A way to delete the account from inside the app, if users can create one. Both stores now require it.

Your privacy disclosures must match what the app really does. If you use an analytics or advertising SDK that collects data, it belongs in the disclosure, even if your own code stores nothing.

Publishing on the App Store

Apple's flow runs through Xcode and App Store Connect:

  1. Set up signing certificates and provisioning profiles, then create the distribution build in Xcode.
  2. Upload the build to App Store Connect, where it goes through automatic processing.
  3. Distribute it through TestFlight to internal testers and, if you want, external ones. External testing gets a short review before it opens.
  4. Fill in the product page, privacy details, age rating and pricing.
  5. Select the build and submit it for review.
  6. Choose whether the approved version goes live automatically, when you release it manually, or gradually to users with automatic updates turned on.

Building and uploading iOS apps requires Xcode, which runs on macOS. If you do not have a Mac, cloud build services can fill the gap, but the account and App Store Connect remain yours.

Publishing on Google Play

On Google's side, everything happens in the Play Console:

  1. Create the app in the console and fill in the basic details.
  2. Generate a signed Android App Bundle, the format required for new apps, and enable Play App Signing.
  3. Use the testing tracks: internal, closed and open. New personal accounts may be required to run a closed test with a minimum number of testers for a set period before production access is granted. Check the current rule.
  4. Complete the store listing, Data safety section, content rating and target audience.
  5. Release to production, ideally as a staged rollout that reaches a share of users before everyone.

Google also requires apps to target a recent Android API level and raises that requirement on a regular schedule. An app left without updates for too long stops being shown to users on newer devices.

Why apps get rejected

The most common rejections are predictable. Use this table as a pre-submission review:

Rejection reasonHow to avoid it
The app crashes or shows an obvious bug during reviewTest the release build on real devices, not only on emulators
The reviewer cannot log inProvide test credentials with populated sample data
Minimum functionality, such as a website in an app shellOffer real app features and useful content
Declared privacy does not match actual behaviorInclude data collected by third-party SDKs
Selling digital content outside the store's payment systemCheck the in-app purchase rules for your case and country
Permissions without a clear reasonExplain in the prompt why the app needs camera, location or contacts
Description or screenshots promising features that do not existShow real screens and describe only what is there

When a rejection arrives, read it carefully and reply through the store's own channel. Often a clarification or a text change is enough, with no new build.

After approval

Going live is the start of your work in the store, and a few routines matter from week one:

  • Track crashes and freezes in the store dashboards and with an error monitoring tool.
  • Reply to reviews, especially negative ones that point to concrete problems.
  • Work on app store optimization: name, description, keywords and screenshots that help people find the app.
  • Plan regular updates and a way to ask users on old versions to update when a change is mandatory.

When Bridgemoon builds an app, publishing is part of the job: setting up accounts, store materials, testing and updates, with the accounts registered to the company that owns the product. That keeps the effort to publish an app from becoming an improvised step at the end of the project.

Frequently asked questions

How long does app store review take?

It varies a lot, from a few hours to a few days, and a first submission usually takes longer than updates. Apps that handle payments, sensitive data or content for children tend to get extra scrutiny. Leave a buffer of several days before any launch date you announce publicly.

Do I need a Mac to publish on the App Store?

To compile and upload the iOS build you need Xcode, which only runs on macOS. Cloud build services solve this if you do not own a Mac, and the rest of the process happens in the browser through App Store Connect. For proper testing, it still helps to have at least one real iPhone available.

Can I publish the app under the agency's account?

Technically yes, but it is not a good idea. The app, its reviews and its history stay tied to another company's account, and moving it later requires a formal transfer in both stores. Open the account under your own company from the start and add the vendor as a user.