Skip to content

Preparing your first app release on the App Store and Google Play

Which accounts, store listing details and reviewer access you need before your first app release, and how to set the launch date.

Katharina Weber4 min read
Smartphone in an open shipping box with three purple check marks on screen and a calendar tag on a purple string.

What has to be settled before you first submit

A finished app is not yet on the App Store or Google Play. Before it gets there, you need an account with each store, a complete product page and login details that let the reviewers use the app. A common misconception concerns the launch itself: many businesses plan to roll out the first version to only a small share of users at first. Google Play explicitly rules this out: staged rollouts there apply only to updates, not to the first release.

In the following invented example, Schreinerei Kessler GmbH, a joinery business, is launching the app "Kessler Termine". Customers use it to book appointments for measuring up and for installation. Version 1.0 is to be released for iOS and Android. An external team is building the app, and the managing director decides when it goes live.

Start with the accounts, because that is where the waiting happens. Apple requires a legal entity for an organisation account; trade names and branches are not enough. For individuals and sole traders, the person's own name appears as the seller on the App Store. Apple verifies the details and may ask for certified documents. Only then can you purchase the membership. Register both accounts in the name of the business and give the development team access.

A completed preparation checklist for version 1.0

Item

Store requirement

In the example

Apple account

Legal entity, D-U-N-S Number, person enrolling has legal authority to sign for the organisation, email address on the company domain, publicly accessible website with content

D-U-N-S Number in place; the managing director enrols with k.kessler@schreinerei-kessler.de; schreinerei-kessler.de is online

Apple product page

Description in plain text up to 4,000 characters, keywords up to 100 bytes without app or company names, screenshots, copyright with year and rights holder

Keywords "Aufmaß, Montage, Termin, Schreiner" (German for measuring, installation, appointment, joiner); copyright "2026 Schreinerei Kessler GmbH"

Support URL (Apple)

Leads to real contact information

Page /app-support with postal address, email and phone number

Privacy policy (Google)

Regular web page, specific to the app, valid SSL certificate, no login, not a PDF; also available in the app

Page /app-datenschutz, linked in the app under "Settings"

App details (Google)

Ads yes or no, target audience by age, content rating questionnaire, data safety

No ads; target audience adults; questionnaire completed

Reviewer access

Apple: demo account that does not expire, instructions in the Notes field. Google: login credentials or instructions for areas behind a login

Test customer PRUEF-01, does not expire, instructions in the Notes field; two sample appointments, invented data only

Release (Apple)

Option under "Version Release"

"Manual"

The Apple requirements are listed in the help page on the product page fields, and Google's on the page about preparing your app for review. Ask the team to confirm each row with a link or a screenshot. Keep the reviewer access valid until the app is approved; it must not expire.

Setting the launch date and planning the first update

On Apple, a version set to "Manual" waits after approval with the status "Pending Developer Release" until you release it. "Automatic, no earlier than" sets an earliest date, and "Automatic" releases the version as soon as it is approved. "Manual" suits the joinery's iOS version: the business only gives customers a launch date once both stores have approved the app and the office and phones are staffed that day. These options come from App Store Connect. For Google Play, agree with the team before submitting when the approved Android version will go live.

Releasing in stages becomes relevant on Google with the first update. You increase the percentage manually. You can halt the rollout; users who already have the version keep it. You can choose individual countries for the start, but you cannot remove them once the rollout has begun. So before the update, decide who increases the percentage, how you will spot problems and who halts the rollout. Database changes need extra care: for updates that migrate data, follow the planning for a release with a database change. How the app then reliably notifies customers of changed appointments is covered in the guide on appointment changes in an app.

Sources

Frequently asked questions

Written by

  • Katharina WeberEditor for Software and TechnologyKatharina Weber looks after the software development articles at ASES. She writes about the questions companies face when choosing software, building new applications and modernising existing systems.

Follow ASES

Read more

All articles

Software Development with ASES

Custom software, web and mobile apps