Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I have an app built and I do not know how to get it into the stores

Short answer

A first release needs a developer account in your own name, a signed build, a store listing, a privacy policy and the store's questionnaires. Google also sets testing requirements for newer personal accounts. You can prepare the accounts, texts and images yourself; building, signing and uploading are the technical part.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • My app works on my phone but I have no idea how to put it on the App Store or Google Play.
  • My developer says it is ready and asks me for accounts, logos and texts.
  • I started creating the store pages and got stuck at a question I did not understand.
  • I am afraid of a rejection on the first try.
  • My developer offered to publish it under their own account.

Why does this happen?

  1. Publishing is a separate job from building

    The store needs more than a working app: an account, a signed build, a listing with screenshots and descriptions, and declarations about content and data. Each is its own checklist.

  2. Google needs a bundle, a package name and a signing set-up

    Google's guide says to upload an Android App Bundle, that the package name is permanent and cannot be reused or deleted, that Play App Signing is configured with your first release, and that every update must increase the version code. The bundle must also meet the current target API level requirement.

  3. New personal accounts on Google have extra testing

    The same guide says new personal developer accounts must meet testing requirements before the app can be made available.

  4. Apple reviews every submission

    Apple's help says each platform can have one app version under review at a time, and that submissions may not be reviewed in the order you submit them.

  5. The first release is where signing mistakes show up

    Certificates, profiles and keys are created once and then needed for every update. A first release done in a hurry on a developer's own account is the usual reason an app later needs to be transferred.

What can I do about it today?

  1. Open the accounts in your company nameEnrol in the Apple Developer Program and register a Google Play Console account yourself, with a company email address you control. Do not let anyone publish the app under their own account.
  2. Choose the app name and write a short descriptionGoogle's guide lists an app name limit of 30 characters, a short description of 80 and a full description of 4,000. Draft the words in your own language of business.
  3. Prepare images and a support contactCollect a logo and screenshots, and decide the support email shown to users. Google requires a support email address in the listing.
  4. Publish a privacy policy on your websiteA real page on your own site, written for your app. Both stores expect a link. Have it checked by the person who handles your legal matters.
  5. List what the app collectsSign-up details, location, payments, analytics and any other tools. You will need it for Apple's App Privacy answers and Google's Data safety form.
  6. Write down who holds the keysAsk your developer where the source code, signing keys and server access are kept, and make sure your company can reach all of them.

When should I bring someone in?

  • You are told the app will be released from the developer's own account.
  • You are unsure about the forms and fear a rejection.
  • The app has payments, accounts or sign-in, which have extra store rules.

How do I handle it?

  1. Review the app against both storesI go through the guidelines that apply to your app type and flag what a reviewer would stop on.
  2. Set up signing in your accountsCertificates, keys and app records are created under your company's accounts, and stored so your company keeps access.
  3. Prepare the listing and the forms with youYou approve the texts and images; I fill the technical fields and the privacy forms from what the app really does.
  4. Release to testers firstA test build goes to testers on both platforms before anything is sent for review.
  5. Submit and handle review feedbackI submit, respond to reviewer messages and prepare the next small update, so a second release is routine.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can my developer publish from their account and transfer it later?

Stores allow transfers, but they add steps and conditions. It is simpler to publish from your own accounts from the start.

How long does review take?

Google's guide does not state a review time and Apple says submissions may not be reviewed in the order sent. The decision is the store's, so I cannot promise a date.

Do I need both stores?

No. You can start with one. Each store has its own account, forms and review.

What will cause a rejection?

Common reasons are a missing privacy policy, forms that do not match the app, crashes and a listing that does not describe the app. I check these before submitting.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.