Prerequisites

Step 1: Developer Account Setup

Visit Google Play Console to create a Google Play Console and complete the developer account setup process.

Choose Account Type

• Individual Developer (additional testing requirements)
• Organization Account (requires D-U-N-S Number)

Complete Registration

1. Pay the $25 one-time registration fee
2. Verify your identity
3. Set up payment profile
4. Provide contact information
5. Accept Google Play Developer Agreement

For Organization Accounts

• Obtain D-U-N-S Number (may take 1-30 business days)
• Submit business verification documents
• Provide organization details

Step 2: App Configuration

Before building your Flutter application, update the required configuration files.

Update pubspec.yaml

Open the following file:

Update the application version:

version: 1.0.0+1 # Format: version_name+version_code

Example Version Sequence

Configure Android Manifest

Navigate to:

Update your application name and icon configuration:

<manifest xmlns:android="http://schemas.android.com/apk/res/android">
    <application
        android:label="Your App Name"
        android:icon="@mipmap/ic_launcher">

        <!-- Your app configuration -->

    </application>
</manifest>

Step 3: Generate App Signing Key

Open terminal in your Flutter project root directory and execute the following command to generate a release signing key.

For macOS/Linux

keytool -genkey -v -keystore YOUR-KEYSTORE-FILE.jks -keyalg RSA -keysize 2048 -validity 10000 -alias YOUR-ALIAS

For Windows

keytool -genkey -v -keystore YOUR-KEYSTORE-FILE.jks -storetype JKS -keyalg RSA -keysize 2048 -validity 10000 -alias YOUR-ALIAS

Follow the Prompt Instructions

1. Enter a secure keystore password
2. Provide your name and organization details
3. Confirm all entered information
4. Wait for keystore generation to complete

Generated File

After successful execution, a .jks keystore file will be generated.

YOUR-KEYSTORE-FILE.jks

Step 4: Configure Key Properties

Create a file named key.properties inside the android folder.

storePassword=YOUR_KEYSTORE_PASSWORD 
 keyPassword=YOUR_KEY_PASSWORD 
 keyAlias=upload 
 storeFile=YOUR-KEYSTORE-FILE.jks

Android Developer Verification

Once your signing key is generated, you may need to register your package name and signing key with Google for developer verification. See Android Developer Verification - Package Name Registration for the full process.

Update build.gradle Configuration

Open the following file:

Load Keystore Properties

Look for the following code block inside your build.gradle.kts file.

✅ If already present, no changes are required.
❌ If missing, add the following code manually:

def keystoreProperties = new Properties()
def keystorePropertiesFile = rootProject.file('key.properties')

if (keystorePropertiesFile.exists()) {
    keystoreProperties.load(
        new FileInputStream(keystorePropertiesFile)
    )
}

Add Release Signing Configuration

Add the following signing configuration inside the signingConfigs block:

signingConfigs {
    release {
        keyAlias keystoreProperties['keyAlias']
        keyPassword keystoreProperties['keyPassword']
        storeFile keystoreProperties['storeFile']
            ? file(keystoreProperties['storeFile']) : null
        storePassword keystoreProperties['storePassword']
    }
}

Set Release Signing Configuration

Add the following line inside the buildTypes.release block:

signingConfig signingConfigs.release

Step 5: Build Your App

Open terminal in your Flutter project root directory and execute the following command to generate the release App Bundle.

flutter build appbundle --release

Optional Build Flags

You can use additional flags for code protection and crash reporting support.

--obfuscate
--split-debug-info

• --obfuscate helps protect your Dart source code
• --split-debug-info helps improve crash reporting and reduces stack trace exposure

Generated App Bundle Location

After successful build completion, the generated App Bundle file will be available at:

build/app/outputs/bundle/release/app.aab

Step 6: App Setup

Create App Listing

Open Google Play Console and create a new application.

1. Go to Google Play Console
2. Click Create app
3. Enter your application name
4. Select default language
5. Select App or Game category
6. Select Free or Paid status
7. Complete declaration of app content
8. Click Create App

Complete Store Listing

After creating the application, complete all required store listing information.

• Application Name
• Short Description
• Full Description
• Application Category
• Contact Information
• Privacy Policy URL

Step 7: Configure App Content & Store Listing

Complete all required Google Play Console content, policy, categorization, and store listing sections before submitting your application for review.

1. Set Privacy Policy

Privacy Policy is mandatory for all applications published on Google Play Store.

• Privacy Policy must be publicly accessible
• Users should access it without login
• Include data collection and usage information
• Include security and protection practices
• Include account/data deletion policy
• Include support and contact information

2. App Access

Configure application login and access requirements.

• Specify whether login is required
• Provide test account credentials if needed
• List special access requirements
• Specify region restrictions if applicable

3. Ads Declaration

Declare whether your application contains advertisements.

Supported Ad Types

• Banner Ads
• Interstitial Ads
• Rewarded Ads
• Native Ads

Also declare the ad networks used in your application.

4. Content Rating

Complete the content rating questionnaire carefully.

Content Categories

• Violence
• Sexual Content
• Language
• Controlled Substances
• Miscellaneous Content

5. Target Audience

• Select target age groups
• Specify whether the app is designed for children

6. News Applications (If Applicable)

Required only for applications that provide news content.

• Declare news content availability
• Provide publisher information
• Explain editorial policies
• Verify trusted news sources

7. Data Safety

Declare all collected user data and explain its usage.

Collected Data Types

• Location
• Personal Information
• Files and Media
• Device Information

Data Usage

• Application Functionality
• Analytics
• Personalization
• Advertising

Security Information

• Data protection measures
• Data sharing practices
• User privacy protection

8. Government Applications (If Applicable)

• Verify government association
• Provide official documentation
• Specify jurisdiction details
• Describe implemented security measures

9. Financial Applications (If Applicable)

• Declare financial services offered
• Provide license and compliance information
• Describe security and encryption measures
• Specify supported countries or regions

10. Health Applications (If Applicable)

• Declare health-related functionality
• Provide medical disclaimers
• Explain data protection measures
• List certifications if available

11. Categorization

Category Information

• Primary category selection
• Application tags and keywords
• Support contact information
• Email address
• Phone number
• Website URL
• Physical address

Store Listing Details

• Application Name (30 characters max)
• Short Description (80 characters max)
• Full Description (4000 characters max)
• What's New in This Release

Visual Assets

App Icon Requirements

• 512 × 512 PNG format
• Maximum file size: 1MB

Feature Graphic

• 1024 × 500 resolution
• PNG or JPG format
• Maximum file size: 15MB

Screenshots

• Minimum 2 phone screenshots required
• 16:9 aspect ratio recommended
• Minimum resolution: 1920 × 1080
• Tablet screenshots optional

12. Languages & Translations

• Default language selection
• Additional language support
• Localized store listings
• Translated screenshots and descriptions
• Language-specific assets

Step 8: Testing Setup

Before publishing your application to production, Google Play may require testing verification depending on your developer account type.

Understanding Testing Requirements

Internal Testing

Internal testing is used for quick distribution to trusted testers before public testing.

Purpose

• Quick testing and verification
• Distribute builds to trusted team members

Features

• Available before app setup completion
• Builds available within seconds
• Small trusted tester group
• Optional but recommended first step
• No special requirements for access

Closed Testing

Closed testing allows testing with a controlled group of users.

Requirements

• Complete application setup
• Minimum 12 opted-in testers
• 14 consecutive days of testing

Features

• Policy compliance verification
• Bug fixing and issue tracking
• User feedback collection

Open Testing

Open testing allows public users to test your application on Google Play.

Requirements

• Production access approval
• Application visible on Google Play

Features

• Anyone can join testing
• Private tester feedback collection
• Public application visibility

Production Release

Production release makes your application publicly available on the Google Play Store.

Requirements

• Successful closed testing completion
• 12+ testers for 14 consecutive days
• Approved production access request

Features

• Full Google Play Store distribution
• Public availability for users
• Access to all Play Console features

Step 9: Production Release

• Create production track
• Select Countries
• Upload app bundle
• Add release notes:
  • What's new
  • Bug fixes
  • Improvements
• Configure rollout percentage
• Review all sections:
  • Store listing
  • Content rating
  • Data safety
  • App content
• Submit for review

Step 10: Post-Release Tasks

After publishing your application on Google Play Store, regularly monitor and maintain your application to ensure the best user experience and policy compliance.

• Monitor Application Performance
• Track User Feedback
• Address Bug Reports
• Plan Future Updates
• Maintain Google Play Compliance

Contact Information

Email: support@pixelwibes.com

Expected response time: 24-48 hours

Support Policy

Not Included:

• Custom feature development
• Code modifications or customization
• Server configuration or hosting issues
• Third-party integrations or services

Support

Your feedback helps us improve XpressHive. If you have suggestions, feature requests, or ideas, feel free to share them with us.