Skip to main content

Step 4: Google Configuration

This guide covers the Android-specific configuration required for your whitelabel mobile app, including app signing, Play Console setup, and Google Play services integration.

Prerequisites​

Before starting, ensure you have:

  • Active Google Play Console account (USD 25 one-time fee)
  • Your app's Package Name decided (e.g., chat.whauto.app)
  • Firebase project created (from OneSignal configuration)
  • google-services.json file downloaded

Step 1: Create App in Google Play Console​

Initial App Creation​

  1. Go to Google Play Console
  2. Click "Create app"
  3. Fill in the details:
    • App name: Your app name (e.g., "WhautoChat Business")
    • Default language: English (or your preferred language)
    • App or game: App
    • Free or paid: Free (or Paid if applicable)
  4. Accept the declarations:
    • ✅ Developer Program Policies
    • ✅ US export laws
  5. Click "Create app"

Step 2: Set Up App Signing​

Google Play App Signing is required for all new apps. This allows Google to manage your app signing key.

Enroll in Google Play App Signing​

  1. In your app's Play Console, go to Setup → App signing
  2. Review the terms and click "Continue"
  3. Choose "Let Google create and manage my app signing key" (recommended)
  4. Click "Continue"
Why Google Play App Signing?
  • Google securely stores your app signing key
  • You can recover from lost upload keys
  • Easier key management and rotation
  • Required for app bundles (AAB format)

Download Upload Certificate​

  1. After enrollment, download the Upload certificate (PEM format)
  2. This certificate will be used by WhautoChat to sign your app builds
  3. Keep this certificate secure

Step 3: Configure App Details​

Store Listing​

  1. Go to Main store listing

  2. Fill in required information:

    • App name: Your app name (30 characters max)
    • Short description: Brief tagline (80 characters max)
    • Full description: Detailed app description (4000 characters max)
    • App icon: Upload 512 x 512 px PNG
    • Feature graphic: Upload 1024 x 500 px JPG or PNG
    • Phone screenshots: Upload at least 2 screenshots
    • Tablet screenshots: Optional but recommended

  3. Add additional details:

    • App category: Select appropriate category (e.g., Business, Communication)
    • Contact details: Email, phone (optional), website
    • Privacy policy: Enter your privacy policy URL

  4. Click "Save"

App Content​

Complete the following sections under Policy → App content:

Privacy Policy​

  1. Click "Start"
  2. Enter your Privacy Policy URL
  3. Click "Save"

App Access​

  1. Click "Start"
  2. Select if your app requires login or has restricted access
  3. If restricted, provide test account credentials
  4. Click "Save"

Ads​

  1. Click "Start"
  2. Select whether your app contains ads
  3. Click "Save"

Content Ratings​

  1. Click "Start"
  2. Enter your Email address
  3. Select App category (e.g., Communication, Utility)
  4. Complete the questionnaire honestly
  5. Click "Submit"
  6. Review and "Apply rating"

Target Audience​

  1. Click "Start"
  2. Select target age groups
  3. Answer questions about child-directed content
  4. Click "Save"

News Apps (if applicable)​

  1. Click "Start"
  2. Indicate if your app is a news app
  3. Click "Save"

COVID-19 Contact Tracing and Status Apps​

  1. Click "Start"
  2. Indicate if your app is related to COVID-19
  3. Click "Save"

Data Safety​

  1. Click "Start"
  2. Answer questions about data collection and sharing
  3. Specify what data types are collected
  4. Explain how data is used and shared
  5. Click "Submit"
Data Safety Required

The Data Safety section is mandatory. Be thorough and accurate, as this information is displayed to users before they install your app.

Step 4: Set Up Countries and Pricing​

  1. Go to Production → Countries/regions
  2. Click "Add countries/regions"
  3. Select countries where you want to distribute your app
  4. Set pricing (if paid app)
  5. Click "Save"

Step 5: Configure App Releases​

  1. Go to Testing → Internal testing
  2. Click "Create new release"
  3. This will be used for initial testing before production
  4. Add testers' email addresses
  5. Click "Save"

Production Track​

  1. Go to Production → Production
  2. This is where your final app will be published
  3. You'll upload your app here after WhautoChat builds it

Required Information for WhautoChat​

Please provide the following to WhautoChat for app build:

App Details​

  • Package Name: (e.g., chat.whauto.app)
  • App Name: Your app name
  • Version Code: Start with 1
  • Version Name: Start with 1.0.0

Firebase Configuration​

  • google-services.json file (from Firebase project)

Play Console Access​

Upload Certificate (from Google Play App Signing)

  • Upload certificate (PEM format) from Play Console
Manual Upload

You will manually upload the AAB file to Play Console after WhautoChat delivers it. No service account or automated access is required.

Keystore Information​

If not using Google Play App Signing, you'll need to create a keystore:

keytool -genkey -v -keystore my-release-key.keystore \
  -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000

Provide:

  • Keystore file (.keystore or .jks)
  • Keystore password
  • Key alias
  • Key password

Configuration Checklist​

Before proceeding, ensure you have:

  • Created app in Google Play Console
  • Enrolled in Google Play App Signing
  • Downloaded upload certificate
  • Completed store listing with all assets
  • Completed all App Content sections
  • Set up countries and pricing
  • Configured internal testing track (optional)
  • Downloaded google-services.json from Firebase
  • Prepared all credentials for WhautoChat

Common Issues​

"Package name already exists"​

Solution: Each package name must be unique globally. Choose a different package name.

"App signing enrollment failed"​

Solution: Ensure you've accepted all terms and conditions. Try again in a few minutes.

"Missing content rating"​

Solution: Complete the Content Ratings questionnaire under App Content.

"Data safety section incomplete"​

Solution: Answer all questions in the Data Safety section. This is mandatory.

"Upload certificate not found"​

Solution: Make sure you've enrolled in Google Play App Signing and downloaded the upload certificate.

App Bundle vs APK​

Google Play requires Android App Bundle (AAB) format for new apps:

  • AAB (Recommended): Smaller download size, optimized for each device
  • APK: Legacy format, larger file size

WhautoChat will build your app as an AAB file for optimal performance.

Version Management​

Version Code​

  • Integer value that increases with each release
  • Not visible to users
  • Example: 1, 2, 3, 4...

Version Name​

  • User-visible version string
  • Example: 1.0.0, 1.0.1, 1.1.0, 2.0.0

Follow semantic versioning: MAJOR.MINOR.PATCH

Security Best Practices​

  • Never share your keystore password publicly
  • Keep backups of your keystore file (if not using Google Play App Signing)
  • Use strong passwords for keystores
  • Limit Play Console access to necessary personnel
  • Enable 2-factor authentication on your Google account

Next Steps​

Once you have completed the Google configuration:

  1. Submit all credentials to WhautoChat for app build
  2. Prepare for App Store Submission (iOS)
  3. Prepare for Play Store Submission (Android)
  4. Review Testing Push Notifications guide

Additional Resources​