Google Play Submission Guide

This guide walks you through the entire process of getting your Primio app listed on Google Play, from creating a developer account to your first public release.

Prerequisites

Before you start, you need:

• A Google Play Developer account ($25 one-time fee) — Sign up here
• An AAB build from Primio — see Android Builds
• An app icon set in Primio — see App Icon

Setting up your developer account

When creating your account, Google asks whether you’re registering as an individual (personal) or an organization:

• Personal account — Requires identity verification (government-issued ID). Verification usually takes 1-3 days. You must complete a 14-day closed testing period before publishing to production.
• Organization account — Requires a D-U-N-S number or other business verification. Verification can take up to a week. Organization accounts can publish directly to production without closed testing.

Tip

Start the account registration process before your app is ready. Verification can take several days, and you don’t want to wait when you’re ready to publish. You can register and complete verification without having an app ready to upload.

Closed testing requirement (personal accounts)

This applies to individual/personal developer accounts

If you registered as an individual (personal account), Google Play requires you to run a closed test with at least 12 testers who have been opted in for 14 continuous days before you can publish to production.

Organization accounts are exempt from this requirement.

This means your app won’t go live immediately. Plan for at least 2-3 weeks from your first AAB upload to public availability.

Setting up closed testing

1. Create a closed testing track

   In Google Play Console, go to your app → Testing → Closed testing. Click “Create new track.”

2. Upload your AAB

   Add your AAB file from Primio as the release artifact.

3. Create a testers list

   Add at least 12 Google email addresses. These must be real people who will opt in.

4. Share the opt-in link

   Google Play generates an opt-in URL. Send it to all your testers.

5. Testers must opt in and install

   Each tester needs to click the opt-in link, accept, and install your app via Google Play. Just adding their email is not enough — they must actively opt in.

6. Wait 14 days

   All 12 testers must remain opted in for 14 continuous days.

7. Apply for production access

   After the 14-day period, you can submit your app for production release.

Tips for finding testers:

• Friends and family with Android devices
• Online communities (Reddit, Discord, product testing forums)
• Colleagues or classmates

Tip

Organization/company developer accounts skip the closed testing requirement entirely and can publish to production directly after review. The registration fee is the same ($25) for both account types. If you have a registered business, consider signing up as an organization.

Closed testing troubleshooting

“I have 12 testers but Play Console says I’m not eligible”

Adding emails to the testers list is not enough. Each tester must:

1. Click the opt-in link you shared
2. Accept the testing invitation on the Google Play page
3. Download and install the app from Google Play

The Play Console counts opted-in testers who have installed the app, not just emails on the list. Check your closed testing track → Testers tab to see who has actually opted in.

Testers aren’t opting in

Send the opt-in link directly (not just the email invitation). The link looks like https://play.google.com/apps/testing/com.your.app. Remind testers they need a Google account and must open the link on their Android device or in a browser signed into the same Google account.

The 14-day timer

The 14-day count starts from the date your 12th tester opts in. If a tester opts out during the 14 days, and you drop below 12, the timer does not reset — but you must get back to 12 opted-in testers to remain eligible. Recruit a few extra testers (15-20) to have a buffer.

Realistic timeline

Plan for 3-4 weeks from your first AAB upload to production eligibility. It takes time to recruit testers, get them to opt in, wait the 14 days, and then go through production review.

Creating your store listing

1. Open the store listing editor

   In Play Console, go to your app → Store presence → Main store listing.

2. App name

   Up to 30 characters. This is what users see in search results and on your app’s page.

3. Short description

   Up to 80 characters. Appears in search results below your app name.

4. Full description

   Up to 4,000 characters. Describe your app’s features, purpose, and value in detail.

5. Screenshots

   Upload at least 2 phone screenshots. Recommended: 4-8 showing your app’s key screens. Take screenshots from your APK running on a device, or use the Primio workspace preview.

6. Feature graphic

   A 1024x500px banner image displayed at the top of your store listing. Use a design tool like Figma or Canva to create one.

7. App icon

   512x512px. Primio sets this from your project icon automatically when you build the AAB.

Content rating

The IARC content rating questionnaire determines the age rating shown on your app’s listing. Getting it wrong can lead to your app being removed later — a wrong “Everyone” rating on an app with chat features, for example.

1. Open the content rating section

   Go to App content → Content rating → Start questionnaire.

2. Answer each question carefully

   The questionnaire asks about specific types of content. Here are the questions that trip up most developers:

   • “Does the app allow users to interact or exchange information?” — Answer Yes if your app has any chat, comments, messaging, forums, multiplayer, or user profiles visible to others. This includes social features even if they’re secondary.
   • “Does the app share the user’s current location with other users?” — Answer Yes if your app shows users on a map or shares location in any form with other users. Answer No if location is only used locally (e.g., finding nearby restaurants without sharing your position).
   • “Does the app enable users to purchase digital goods or premium content?” — Answer Yes if you have any in-app purchases, subscriptions, or premium unlocks.
   • “Does the app contain user-generated content?” — Answer Yes if users can post text, images, or any content visible to other users.
   • “Does the app contain ads?” — Answer Yes if you use AdMob or any ad network.

3. Review your rating and submit

   The questionnaire assigns ratings for different regions automatically (ESRB, PEGI, etc.). Review them and click Apply.

Caution

If you add new features later (e.g., chat, ads, in-app purchases), you must update your content rating. Go back to App content → Content rating and complete the questionnaire again. An outdated rating that doesn’t match your app’s actual content can result in removal from the store.

Pricing and distribution

• Choose whether your app is free or paid. Note: you cannot change a free app to paid later.
• Select the countries where the app will be available.
• Accept the developer distribution agreement.

Uploading the AAB

1. Create a new release

   Go to Release → Production (or your testing track). Click “Create new release.”

2. Upload the AAB file

   Drag your AAB from Primio into the upload area.

3. Add release notes

   Describe what’s new in this version. For your first release, summarize the app’s main features.

4. Review and roll out

   Review the release summary and click “Start rollout to production.”

Review process

• Google Play reviews typically take a few hours to a few days.
• First submissions may take longer — up to 7 days.
• You’ll receive an email when your app is approved or if changes are needed.
• If rejected, Google explains the reason. Fix the issue, rebuild in Primio if needed, and resubmit.

Common issues

App crashes after install Test thoroughly on a real device with the APK before submitting the AAB. The web preview may not catch device-specific issues.

Missing or default app icon Set a custom app icon in Primio (Workspace → App Icon) before building the AAB. Google Play rejects apps without a proper icon, and apps using the default Primio template icon will also be rejected. Your icon must reflect your actual app.

Version number not incremented Each new AAB you upload to Google Play must have a higher version number than the previous one. If you rebuild in Primio and upload again, the version code is incremented automatically. However, if you see a “version code already exists” error, you may need to rebuild to get a fresh version number.

Signing key problems Primio signs your builds automatically. If you accidentally let Google Play manage your signing key and later need to change it, your app is treated as a new app and existing users can’t update. Contact Primio support if you run into signing issues.

Content policy violations Google has strict policies on content, permissions, and data safety. Read the Google Play Developer Policy Center if your app handles sensitive data or uses device permissions.