Guide to publishing your Apps on Google store

Step-by-Step Guide to Submitting Your App

Step 1: Create Your App in the Console

  1. Log in to your Google Play Console.
  2. On the “All apps” page, click the Create app button.
  3. Fill in the initial details:
  4. App name: The name that will appear on Google Play.
  5. Default language: The primary language for your app’s listing.
  6. App or game: Choose which category your creation falls into.
  7. Free or paid: This decision is permanent! You can change a paid app to free later, but you can never 8. change a free app to a paid one.
  8. Check the boxes to accept the Developer Program Policies and US export laws.
  9. Click Create app. You’ll be taken to your app’s dashboard.

Step 2: Set Up Your Store Listing

This is what users will see on the Play Store. Navigate to the “Grow” section in the left-hand menu, then go to Store presence > Main store listing.

  1. App details: Enter the short and full descriptions you prepared earlier.
  2. Graphics: Upload your app icon, feature graphic, and screenshots. You can also add a link to a promo video.
  3. Contact details: Provide an email address, website, and phone number so users can contact you.

Step 3: Complete the App Content Sections

This is a crucial step to ensure your app complies with Google’s policies. In the left-hand menu under the “Policy and programs” section, go to App content. You’ll need to complete several questionnaires:

  1. Privacy Policy: Add the URL to your privacy policy.
  2. Ads: Declare whether your app contains ads.
  3. App access: If your app has logins or restricted parts, you must provide instructions and credentials so Google can review it.
  4. Content ratings: Fill out a questionnaire about your app’s content. This will generate an official rating (like ESRB, PEGI) for different regions. Be honest here to avoid rejection.
  5. Target audience and content: Specify the target age group for your app. This is very important, especially if your app could appeal to children.
  6. Data safety: This is a very important form. You must declare what kind of user data your app collects, shares, and for what purpose. Be thorough and accurate.

Step 4: Prepare and Upload Your Release

This is where you upload your actual app file (.aab).

  1. In the left menu, go to Release > Production.
  2. Click Create new release.
  3. App bundles: In the “App bundles” section, upload your .aab file. The console will process it and show details like the version code and size.
  4. Release name: This is for your own reference (e.g., 1.0.0-initial-release).
  5. Release notes: Write down what’s new in this version. This is what users will see in the “What’s new” section on the Play Store.
  6. Click Save, and then click Review release.

Step 5: Configure Countries and Pricing

  1. Countries/regions: Go to Reach and devices > Countries / regions. Click Add countries / regions and select all the locations where you want your app to be available.
  2. Pricing (for paid apps): If you set your app as paid, go to Monetize > App pricing to set the price.

**Step 6: Review and Roll Out **

  1. Go back to Release > Production.
  2. If you have completed all the previous steps, the “Review release” page will show no errors. The dashboard will have green checkmarks next to all the required sections.
  3. If everything looks good, a button labeled Start rollout to Production will be active.
  4. Click it!

What Happens Next? Your app is now submitted for review by the Google Play team. Review Time: This can take anywhere from a few hours to a week or more, especially for new developers. Approval: You’ll receive an email and a notification in the Play Console once your app is approved. It will then become available on the Google Play Store within a few hours. Rejection: If your app is rejected, Google will send you an email explaining the policy violation. You’ll need to fix the issue, create a new release, and resubmit it for review. Pro Tip: Before releasing to “Production”, it’s highly recommended to use the “Internal testing” or “Closed testing” tracks first. This allows you and a select group of testers to find bugs before your app goes live to the public.


Write a comment
No comments yet.