The app is ready, but before it reaches users it has to get through the stores. People often underestimate this step, budget a single day for it, and then watch the launch slip by a week. This guide covers how to publish an app on the App Store and Google Play: which accounts you need, what to prepare, how review works, why apps get rejected, and how to ship updates.

Developer accounts: register them to your company

To publish an app, you need a developer account in each store:

  • Apple Developer Program: $99 per year. If you do not renew, the app disappears from the App Store.
  • Google Play developer account: $25 one-time.

The main rule: register the accounts to your company, not to your contractor or an employee. In the store, the app lives in the owner’s account, and that is where ratings, reviews, statistics and users stay. You give the contractor access with the right role, and if you change contractors, you just revoke it. Moving an app out of someone else’s account is possible, but it is an extra procedure that depends on the other side’s goodwill. For what else should belong to you, see who owns your website.

For a company account, the stores verify the organization: you will need your legal entity details, a company website, a work email on the company domain, and Apple asks for a unique organization number from an international business registry. Getting that number and passing verification can take from a few days to a couple of weeks, so start registration early, while the app is still being built. Check the requirements in the stores’ own help pages before you begin.

Register your Apple and Google Play accounts to your company at the start of development, not on launch day. Organization verification can take longer than the release itself.

What to prepare to publish an app

The store listing is your shop window. Here is what it needs.

Name and descriptions

  • App name as it will appear in the store. Short and clear, without keyword stuffing.
  • Short description or subtitle: one line on the main benefit.
  • Full description: what the app does, who it is for, how to get started. Write for people, not for search.
  • Keywords for App Store search and the app category.

If the app supports several languages, you need texts and screenshots for each.

Icon and screenshots

The icon must be readable at a small size. Screenshots are needed for several screen sizes, and for tablets if the app runs on them. Screenshots with a short caption that explains the benefit work best: “Order in three taps”, not “Cart screen”. You can also add a short video.

Privacy policy and data form

A privacy policy link is required in both stores. On top of that you fill in a form: what data the app collects (phone number, location, order history), why, and whether it is shared with third parties. The answers must match what the app actually does. For complex cases, have a lawyer review the policy.

Account deletion

If the app has sign-up, users must be able to delete their account from inside the app. Both stores require this, and missing it is a common reason for rejection.

Review access

If the app requires login, prepare a test account for the reviewer and short notes: how to sign in, where the main feature is, what is needed to test payment. If login uses an SMS code, agree with your developer on a test number with a fixed code.

Contacts

A support email and website where users and the store can reach you.

How App Store and Google Play review works

Every version of the app, including updates, is reviewed before release. Review usually takes from a few hours to a few days, but there is no guaranteed timeline. A first release and major changes get closer attention.

Google Play may apply extra requirements to new accounts, such as mandatory closed testing with a group of users before a public release. The rules change from time to time, so check the current conditions when you register and build the time into your plan.

Once approved, you decide when to release: right away or at a time you choose. It is handy to submit a version early and release it on launch day. For why development timelines slip and how to plan for it, see why projects run late.

Who prepares the release: you or your developer

The work is usually split like this. The developer builds the release, uploads it to the stores, fills in the technical fields and answers the reviewer’s technical questions. On your side: company accounts, texts and decisions, such as the app name, what the description promises and what data the app collects. Screenshots are often made by the developer’s designer, but you approve them.

Agree on this early and write down who is responsible for what. Otherwise, on the last day it turns out there is no privacy policy and nobody wrote the store texts.

Why an app can be rejected

Apple and Google each have their own rules, and they change periodically, but the common rejection reasons are similar:

  • Crashes and bugs. The app crashes, buttons do nothing, screens are empty.
  • No review access. The reviewer could not sign in because there was no test account.
  • Incomplete information. Placeholder text, test data, broken links, unfinished “coming soon” sections.
  • Listing does not match the app. Screenshots or the description promise things the app does not have.
  • Data issues. No privacy policy, a data form that does not match reality, no account deletion, permission requests with no explanation of why.
  • Purchases outside the rules. Digital goods and subscriptions inside the app must be sold through the store’s in-app purchase system. Physical goods and services, such as delivery, usually do not need it.
  • Too little value. An app that just opens your website may fail review as not useful enough.

A rejection is not a disaster: it usually names the rule that was broken. Fix it, reply to the reviewer with an explanation if needed, and resubmit.

Updates after release

Release is the beginning, not the end. Every update goes through review again, so even urgent fixes take time. In Google Play you can roll out an update gradually, to a share of users first, and halt it if something goes wrong.

The stores also regularly require support for recent iOS and Android versions. An app that has not been updated for a long time may stop being shown to new users. For the recurring costs after launch, see how much a mobile app costs, and for how release fits into development, see the mobile apps page.

In short

  • You need two developer accounts: the Apple Developer Program at $99 per year and Google Play at $25 one-time. Register them to your company early.
  • For the listing, prepare a name, descriptions, icon, screenshots, a privacy policy and the data form.
  • If the app has sign-up, add account deletion and give the reviewer a test login.
  • Review takes from a few hours to a few days, and a rejection is usually fixable.
  • Every update goes through review again, and the app needs to keep up with new system versions.