DIGIBOY
Mobile Apps

How to Publish an App on Google Play and the Apple App Store

Developer accounts, store listings, testing tracks, review and updates. What a business owner needs to know before an app goes live.

Published · 7 min read · By the Digiboy team

To publish an app you open a developer account with each store, prepare the store listing and privacy details, test the app with real users, and submit it for review. Google Play covers Android phones and the Apple App Store covers iPhones and iPads. Review can take from hours to days and can end in rejection, so plan the launch date with room to spare.

Whose name should the developer accounts be in?

The developer accounts should be in the business’s own name. A developer account is the publisher’s account with the store, and whoever holds it controls the app, its reviews, its updates and any income from it.

If the app is published under your developer’s account, your app sits in their shop. Moving an app to another account later is possible on both stores, but it needs the current account holder to cooperate. Open the accounts yourself, then invite your developer as a user with the access they need.

Google Play Apple App Store
Account Google Play Console developer account Apple Developer Program membership
Fee at the time of writing 25 US dollars, one time 99 US dollars a year
Account types Personal or organisation Individual or organisation
Name shown on the store The developer name on the account The individual’s name or the organisation’s legal name
Testing tool Internal, closed and open testing tracks TestFlight

Check each store’s current fee page before paying, because fees and rules can change.

For an organisation account, both stores verify that the business exists. Expect to give the legal business name, address, a phone number and website, and a D-U-N-S number, which is a free business identifier issued by Dun and Bradstreet. Getting that number and passing verification can take days or weeks, so start the accounts well before the app is finished.

What do you need before you submit an app?

You need the finished app plus a set of listing materials and declarations. Missing items are a common cause of delay.

  1. App name, short description and full description. Plain, accurate text about what the app does.
  2. App icon and screenshots. Each store sets its own sizes. Screenshots must show the real app.
  3. A privacy policy. A public web page that says what data the app collects, why, and who it is shared with.
  4. Data declarations. Google Play has a Data safety form and Apple has App Privacy details. Both ask what the app collects and how the data is used, and the answers appear on the store listing.
  5. Content rating. A questionnaire about the app’s content that produces an age rating.
  6. Test access. If the app needs a login, give the reviewers a working test account and any instructions they need.
  7. Support contact. An email address, and usually a website, that users can reach.
  8. Account deletion. If users can create an account in the app, both stores expect a way for users to ask for that account to be deleted.

A website helps here. The privacy policy, support page and deletion request page all need a public address, and reviewers look at them.

How do testing tracks work?

Testing tracks let a limited group install the app from the store before the public can. Testing on the real store catches problems that never show on the developer’s own phone.

On Google Play there are three stages. Internal testing is for a small team. Closed testing is for a list of invited testers. Open testing lets anyone join from the store listing. At the time of writing, Google requires newly created personal accounts to run a closed test with a minimum number of testers for a set period before the app can go public. Check the current requirement in the Play Console, because it has changed before and it affects your timeline.

On Apple, testing runs through TestFlight. Internal testers are members of your team. External testers are invited by email or a public link, and the first build for external testers goes through a review.

Use these tracks properly. Give the app to staff and a few real customers on ordinary phones, including older mid-range Android phones on mobile data, and fix what they report.

How does app review work?

After you submit, the store checks the app against its policies using automated checks and human reviewers. The outcome is approval, or a rejection with a reason.

Review times vary. Many reviews finish within a day or two, some take a few hours, and some take a week or more, especially for a new account or an app in a sensitive category such as finance, health or children’s content. Neither store guarantees a time, and nobody outside the store can promise one. Do not print a launch date on a banner until the app is approved.

A rejection is not the end. You read the reason, fix the problem or reply with an explanation, and resubmit. Both stores have an appeal route if you believe the decision is wrong.

What are the common reasons for rejection?

Most rejections come from a short list of avoidable problems.

  • Crashes and broken features. The reviewer taps a button and nothing happens.
  • The reviewer cannot get in. No test login, an expired one, or a login that needs an OTP sent to a phone the reviewer does not have.
  • Privacy gaps. No privacy policy, or data declarations that do not match what the app actually does.
  • Unexplained permissions. Asking for location, camera or contacts without a clear reason shown to the user.
  • Misleading listing. Screenshots or descriptions that promise features the app does not have.
  • Payment rules. Both stores have rules about how digital goods and subscriptions are sold inside an app. Physical goods and real-world services are treated differently. Check the current rules for your case before building the payment flow.
  • Thin apps. Apple in particular may reject an app that is only a website in a wrapper with no added use.
  • Placeholder content. Test text, empty screens or “coming soon” sections.

What happens after launch?

After launch the app needs regular updates, and each update goes through review again. Three kinds of work continue.

Fixes and improvements. Real users find problems that testers missed. Both stores let you release an update to a share of users first, so a bad release can be caught early.

Store requirements. Google Play periodically requires apps to be built for a recent version of Android, and Apple expects apps to be built with current tools. An app left untouched for too long can be hidden from new users or removed.

Reviews and support. Reply to store reviews, especially poor ones. A calm reply and a fix often lead the user to change the rating.

Remember that the Apple membership renews every year. If it lapses, the app comes off the App Store. The guide to mobile app development cost in Kerala covers typical yearly maintenance budgets.

Do you need to be on both stores?

Not always on the first day. In Kerala most phones are Android, so many local businesses launch on Google Play first and add iPhone when the app has proved itself. If your customers include many iPhone users, for example in the GCC, plan for both from the start. A cross-platform tool builds both apps from mostly shared code, which our comparison of Flutter, React Native and native apps explains. And if you are unsure an app is needed at all, read mobile app or website first.

Where Digiboy fits

In our mobile app development work, the store accounts are opened in your name and we handle the listing, testing tracks and submission with you. We do not promise approval dates, because the stores decide those.

Questions people ask

How much does it cost to publish an app on Google Play and the App Store?

Google Play charges a one-time developer registration fee of 25 US dollars, and the Apple Developer Program costs 99 US dollars a year, at the time of writing. These are the store account fees only and do not include the cost of building the app.

How long does app review take on Google Play and the App Store?

App review on Google Play and the Apple App Store can take from a few hours to several days, and a first submission from a new account often takes longer. Neither store guarantees a review time, so leave a buffer before any launch date.

Who should own the developer account, the business or the developer?

The business should own the developer account. An app published under a developer's or agency's account is controlled by that developer, and moving it later needs their cooperation.

Why do apps get rejected by the App Store or Google Play?

Apps are commonly rejected for crashes, missing privacy details, reviewers being unable to log in, permission requests without a clear reason, misleading listings, or payment methods that break the store's rules. Most rejections can be fixed and resubmitted.

Do I need a privacy policy to publish an app?

Yes. Both Google Play and the Apple App Store ask for a privacy policy link for apps, and both ask the publisher to declare what data the app collects and how the data is used.

Can I update an app after it is published?

Yes. An app is updated by uploading a new version to the store, and each new version normally goes through review again before users receive it.

Have something to build?

Tell us the idea. We will tell you how to build it.

Start a project