Publishing to Google Play Store: Indian Developer Guide

You have built your Android app and it works perfectly on your test device. Now comes the part that trips up many first-time developers: getting it onto the Google Play Store. This guide is written specifically for Indian developers and covers everything from account setup to your first production release, including India-specific details about payments, GST, and compliance.

Setting Up Your Developer Account

Before you can publish anything, you need a Google Play Developer account:

1. Go to play.google.com/console and sign in with your Google account.
2. Pay the one-time registration fee of $25 (approximately 2,100 INR). This is charged to your credit or debit card — UPI is not supported for this payment.
3. Complete identity verification. Google requires a valid government ID. Aadhaar card or PAN card works. This process takes 2-5 business days.
4. If you plan to sell paid apps or use in-app purchases, you must set up a merchant account with your PAN number and bank details. Google will deposit a small amount to verify your bank account.

Important for Indian developers: Google deducts a 30% commission on Play Store sales. You must add your GSTIN (GST Identification Number) to your payments profile to ensure proper tax invoicing. Go to Settings → Payments profile → Tax information and enter your GSTIN.

Preparing Your App for Release

Switch your app from debug to release mode. Update your build.gradle (app-level) with proper versioning:

// app/build.gradle.kts
android {
    namespace = "com.yourcompany.yourapp"
    compileSdk = 35

    defaultConfig {
        applicationId = "com.yourcompany.yourapp"
        minSdk = 24
        targetSdk = 35
        versionCode = 1        // Increment for every upload
        versionName = "1.0.0"  // User-visible version
    }

    buildTypes {
        release {
            isMinifyEnabled = true
            isShrinkResources = true
            proguardFiles(
                getDefaultProguardFile("proguard-android-optimize.txt"),
                "proguard-rules.pro"
            )
        }
    }
}

The versionCode must be incremented every time you upload a new APK or App Bundle. The versionName is what users see. Follow semantic versioning (major.minor.patch).

App Signing with Play App Signing

Google Play App Signing is now mandatory for new apps. Google manages your app signing key while you use an upload key to sign what you send. Generate your upload key:

# Generate an upload keystore
keytool -genkeypair -v \
  -keystore upload-keystore.jks \
  -keyalg RSA -keysize 2048 \
  -validity 10000 \
  -alias upload \
  -storepass YOUR_STORE_PASSWORD \
  -keypass YOUR_KEY_PASSWORD

# Verify the keystore
keytool -list -v -keystore upload-keystore.jks -alias upload

Configure signing in your build file:

// app/build.gradle.kts
android {
    signingConfigs {
        create("release") {
            storeFile = file("upload-keystore.jks")
            storePassword = System.getenv("STORE_PASSWORD")
            keyAlias = "upload"
            keyPassword = System.getenv("KEY_PASSWORD")
        }
    }

    buildTypes {
        release {
            signingConfig = signingConfigs.getByName("release")
            // ... minify settings
        }
    }
}

Never commit your keystore or passwords to version control. Use environment variables or a key.properties file that is listed in .gitignore.

Build the release App Bundle (AAB is required — APKs are no longer accepted for new apps):

# For a native Android app
./gradlew bundleRelease

# The output AAB will be at:
# app/build/outputs/bundle/release/app-release.aab

# For a Flutter app
flutter build appbundle --release

# Output: build/app/outputs/bundle/release/app-release.aab

Creating the Store Listing

Your store listing is what convinces users to install your app. Go to Google Play Console → Your App → Store presence → Main store listing and fill in:

• App name: Up to 30 characters. Make it descriptive and searchable.
• Short description: 80 characters. This appears in search results.
• Full description: Up to 4000 characters. Use keywords naturally, explain features, and include Hindi/regional language keywords if your target audience is non-English.
• Screenshots: Minimum 2, recommended 8. Sizes: phone (1080×1920), 7-inch tablet (1200×1920), 10-inch tablet (1600×2560). Use a tool like screely or Figma to create framed screenshots.
• Feature graphic: 1024×500 pixels. This is the banner image at the top of your listing.
• App icon: 512×512 pixels, PNG, 32-bit with alpha channel.

For the Indian market specifically, consider adding store listing translations in Hindi, Tamil, Telugu, and other major languages. Go to Store presence → Store listing translations to add localized versions.

Content Rating and App Content

Google requires a content rating questionnaire. Navigate to Policy and programs → App content and complete all sections:

• Privacy policy: Mandatory. Host it on your website. It must describe what data you collect and how you use it. For apps targeting Indian users, ensure compliance with the Digital Personal Data Protection Act (DPDPA) 2023.
• Ads declaration: Declare whether your app shows ads.
• Content rating: Answer the IARC questionnaire honestly. Most utility apps get an “Everyone” rating.
• Target audience: If your app could appeal to children under 13, you must comply with additional policies.
• Data safety: Declare what data your app collects, whether it is shared, and encryption practices.

Release Process

Google Play has three release tracks:

1. Internal testing: Up to 100 testers. No review required. Use this for QA.
2. Closed testing (Alpha/Beta): Invite-only. Requires review but is faster.
3. Production: Public release. Review takes 1-7 days for new apps.

For your first release, start with Internal testing to verify everything works:

1. Go to Release → Testing → Internal testing.
2. Create a new release and upload your AAB file.
3. Add testers by email address.
4. Roll out the release.
5. Testers receive a link to install via Play Store within minutes.

Once internal testing passes, promote to production:

1. Go to Release → Production.
2. Click “Create new release”.
3. Upload the AAB (or promote from testing track).
4. Add release notes. Write them in English and Hindi if applicable.
5. Review and roll out. Use a staged rollout (start with 20%) for your first production release to catch issues early.

Post-Launch: Monitoring and Updates

After your app is live, monitor it through the Play Console dashboard:

# Useful ADB commands for testing on physical devices
adb devices                          # List connected devices
adb install app-release.apk          # Install APK directly
adb logcat | grep "YourAppTag"       # View app logs
adb shell dumpsys package com.yourcompany.yourapp  # Package info

Set up crash reporting with Firebase Crashlytics (free) and monitor your Android Vitals in Play Console. Google penalises apps with high ANR (Application Not Responding) rates or excessive crash rates in search rankings.

Conclusion

Publishing to the Google Play Store is a multi-step process, but none of the individual steps are difficult. The most common mistakes Indian developers make are: forgetting to add GSTIN for tax compliance, committing the keystore to Git, skipping the content rating questionnaire, and not adding a privacy policy. Follow this guide step by step, start with internal testing to build confidence, and your app will be live for India’s 600 million smartphone users in no time.