Signed AAB: Uploading to Google Play Console

You've downloaded your signed .aab file. Now you need to get it into the Google Play Store so users can find and install it. This walkthrough covers the entire submission process, including the requirements that affect new developer accounts.

Before You Start

• Google Play Developer Account: $25 one-time registration at play.google.com/console. The account must be in the name of the person or organization that owns the app.
• Identity verification: Google requires identity verification for all developer accounts (mandatory since May 2024). Personal accounts need a government-issued photo ID and a verified billing address. Organization accounts additionally need a D-U-N-S number and website verification. Have these ready before registering.
• Your signed AAB: Downloaded from your WebToAppConvert dashboard after a Starter or Professional build.
• App assets: At least 2 phone screenshots (JPEG or 24-bit PNG, no transparency; 320–3,840 px per side; max 8 MB each), a feature graphic (1024×500 px JPEG or PNG), a short description, and a full description.
• Privacy policy URL: Required for all apps. Must be publicly accessible before submission. Your website's existing privacy policy page works fine.

New Account Timeline

Most apps get approved within a few days. If your Google Play developer account is brand new (created after November 2023), Google requires a closed testing period before production access. Budget extra time:

1. 14 continuous days of closed testing with at least 12 opted-in testers
2. Apply for production access once the testing requirement is met
3. Up to 7 additional days for Google's review, depending on their current queue

Established accounts with a publishing history go straight to production review and are typically live within a few days. New accounts should plan for a few weeks to be safe.

Step 1: Create a New App in Play Console

1. Sign into play.google.com/console
2. Click Create app
3. Set the App name (what users see in the Play Store: can differ from your in-app name)
4. Set the default language
5. Select App or Game
6. Select Free or Paid (most WebView apps are free)
7. Agree to the declarations and click Create app

Step 2: Internal Testing Track (Quick Device Verification)

Before going through the full submission process, use the Internal Testing track to install and verify your app on real devices immediately, with no review wait. Up to 100 specific testers can install the app within minutes of upload.

1. Navigate to Test and release → Testing → Internal testing
2. Click Create new release, upload your AAB, and add release notes
3. Click Save: the release is available within minutes, no review required
4. On the Testers tab, create a tester group, add email addresses, and share the opt-in link
5. Testers click the link to join, then find and install the app from the Play Store

Internal Testing does not satisfy the 14-day closed testing requirement for new accounts. Use Closed Testing (Alpha) for that, covered in Step 6.

Step 3: Set Up the Store Listing

Navigate to Grow → Store presence → Main store listing.

Short description (up to 80 characters): The first line users see in the Play Store. Make it specific and benefit-focused.

Full description (up to 4,000 characters): Describe what users can do in your app. Include relevant keywords naturally: this text is indexed by Play Store search. Do not claim your app is "better than" named competitors; that violates Play Store metadata policy and causes rejection.

App icon: 512×512 PNG. This is the Play Store icon: it should match your in-app icon.

Feature graphic: 1024×500 JPEG or 24-bit PNG. Appears at the top of your Play Store listing on some devices.

Screenshots: At least 2 phone screenshots. Requirements: JPEG or 24-bit PNG with no transparency, 320–3,840 px per side, longer side no more than 2× the shorter side, max 8 MB per image. Recommended size: 1080×1920 px portrait. Take screenshots from your debug build on a real device, or design them in Figma using a phone frame template.

Step 4: App Content and Ratings

Navigate to Policy → App content and complete each section. Incomplete sections are one of the most common causes of rejection.

• Privacy policy: Enter your privacy policy URL. It must be publicly accessible at submission time.
• Ads declaration: Select Yes if your app shows ads, including AdMob.
• Content rating: Complete the IARC questionnaire. Most WebView apps wrapping standard business websites receive an "Everyone" rating.
• Target audience: Select your target age group. If your app is not directed at children, select "18 and over" or "all ages."
• Data safety: Declare what data your app collects and how it is used. For a WebView app, include data collected through the WebView itself: login credentials if users sign in, location if enabled, analytics identifiers, and any data collected by AdMob or Firebase if used. An inaccurate or incomplete Data Safety form causes rejection.
• News app declaration: Declare whether your app is a news app.

Step 5: Set Up Play App Signing

Google requires all new apps to use Play App Signing (managed from Release → App integrity). Google re-signs your AAB with a Google-managed key before distributing to users. Your WebToAppConvert signing key becomes the "upload key": if you ever lose it, you can request a reset and keep publishing updates because Google holds the actual signing key.

When uploading your first release, Play Console walks you through Play App Signing enrollment automatically. Follow the prompts.

Step 6: Closed Testing for New Accounts

If you have a new developer account, complete closed testing before applying for production access:

1. Navigate to Test and release → Testing → Closed testing (Alpha)
2. Create a release and upload your AAB
3. On the Testers tab, add at least 12 testers and share the opt-in link
4. Testers must actively install the app and remain opted in for 14 continuous days
5. After 14 days with 12 or more active testers, Play Console will prompt you to apply for production access

If you already have an established developer account, skip this step and go directly to Step 7.

Step 7: Create a Production Release

1. Navigate to Release → Production
2. Click Create new release
3. If prompted for Play App Signing enrollment, complete it
4. Click Upload and select your .aab file
5. Wait for Play Console to process the AAB (1–3 minutes)
6. Add release notes: for a first release, a brief description of what the app does works well
7. Click Review release
8. Address any errors shown; most warnings are informational and not blocking
9. Click Start rollout to Production

Step 8: Wait for Review

Review timelines by account type:

• Established accounts: Most apps are reviewed within a few hours to a couple of days. Sensitive categories (health, finance) may take longer.
• New accounts: After completing the 14-day closed test and applying for production access, allow up to a week for Google's review. Plan for a few weeks total if your account is new.

You will receive an email when your app is approved and live, or if there are policy issues to address. Keep your AAB file: you will need a new build with an incremented version code for any future updates.

Common Rejection Reasons

Incomplete Data Safety form: Every section must be filled in accurately. Review what data your website, AdMob (if used), and Firebase (if used) collect and declare it all. This is the most frequent cause of first-submission rejection.

Missing or inaccessible privacy policy: The URL must resolve to a publicly readable page at submission time. A broken link or a page behind a login will cause rejection.

Spam and Minimum Functionality (updated July 2024): Google explicitly targets WebView apps that add no value beyond the mobile website. To reduce this risk: enable push notifications, handle Android's back button correctly, show a meaningful offline error message, and ensure your website has real content and functionality. Apps wrapping established businesses with genuine content consistently pass review.

Metadata policy violation: Descriptions cannot name competitors or claim to be "better than" other apps. Keep the description factual and focused on your own app's features.

Account suspended after first submission: New accounts occasionally trigger automated spam protection. If this happens, use the reinstatement appeal process linked in the Play Console notification.