How to Deploy Your App on
Google Play Store — Step by Step

Prerequisites Before You Submit

Before beginning the submission process, make sure you have the following ready:

• A fully tested, production-ready Android app (AAB format preferred, APK also accepted)
• A signed build — the app must be signed with a production keystore (not the debug keystore)
• A Google account to create your developer account
• A one-time developer registration fee of $25 (~₹2,100)
• A privacy policy hosted at a stable URL (required if your app collects any data)
• Store listing assets: icon (512×512px), feature graphic (1024×500px), and at least 2 screenshots

Step 1: Create a Google Play Developer Account

1. Go to play.google.com/console and sign in with your Google account
2. Click "Get started" and choose whether you're registering as an individual or organisation (choose organisation if submitting on behalf of a company)
3. Fill in your developer name — this is what users see on the Play Store next to your app
4. Pay the one-time $25 registration fee via credit/debit card
5. Complete the account verification — Google may request ID verification for organisations
6. Accept the Play Developer Distribution Agreement

Account approval typically takes a few hours to 1 business day. You'll receive a confirmation email when your account is active.

Step 2: Prepare Your APK / AAB

Your app must be signed with a production keystore before submission. In Android Studio:

1. Go to Build → Generate Signed Bundle / APK
2. Select Android App Bundle (recommended)
3. Create a new keystore or use an existing one. Store the keystore file and its passwords securely — losing this file means you cannot update the app.
4. Select the release build variant
5. Click Finish — Android Studio will generate the signed AAB file

Ensure your app's versionCode and versionName in build.gradle are correctly set for your first release (typically versionCode 1 and versionName "1.0.0").

Step 3: Create Your App on Play Console

1. In Play Console, click "Create app"
2. Enter your app name (this can be changed later but choose carefully as it affects discoverability)
3. Select your app's default language
4. Declare whether it's an app or a game
5. Declare whether it's free or paid (you cannot change from paid to free later)
6. Accept the Play Developer Program Policies and US export laws declaration

Step 4: Set Up the Store Listing

The store listing is what users see before downloading. A well-optimised listing improves both conversions and organic discoverability:

• Title — Up to 30 characters. Include your app name and one key benefit or category. E.g. "SchoolPro – School Management"
• Short description — Up to 80 characters. Appears in search results. Lead with the strongest benefit.
• Full description — Up to 4,000 characters. Describe features in detail. Use natural language that includes keywords your users might search for.
• Screenshots — At minimum 2, up to 8. Show the key screens users will interact with. Add captions that explain what they're seeing.
• Feature graphic — 1024×500px image shown at the top of your listing. Use brand colours and a clear tagline.
• App icon — 512×512px, high-resolution, PNG with transparency. This is the first visual impression of your app.

Step 5: Content Rating

Google requires all apps to complete a content rating questionnaire. This determines the age-appropriate rating (similar to movie ratings) shown on your listing. The questionnaire asks about violence, sexual content, gambling, user-generated content, and more. Answer honestly — misrepresentation can result in removal.

Most business apps receive an "Everyone" or "Everyone 10+" rating.

Step 6: Data Safety Form

This section (introduced in 2022) requires you to disclose what data your app collects, how it's used, and whether it's shared with third parties. Categories include: location, personal info, financial info, health, messages, photos/files, device identifiers, and more.

Be accurate — Google (and users) take this seriously. If your app collects login email addresses and sends push notifications, you must disclose both. Inaccurate data safety forms can result in removal.

Step 7: Pricing & Distribution

Set your app as Free or Paid. Select which countries to distribute to (we recommend starting with India and expanding once the app is stable). You can also exclude specific devices or Android versions if your app doesn't support them.

Step 8: Submit for Review

1. Navigate to Production → Releases → Create new release
2. Upload your signed AAB file
3. Add release notes (what's new — for the first release, write "Initial launch")
4. Click Review release — Play Console will warn you about any incomplete sections
5. Complete all warnings, then click Start rollout to Production

Your app will enter the review queue. You'll receive an email when it's approved or if action is required.

Handling Rejections

Common reasons for rejection and how to fix them:

• Missing privacy policy — add a privacy policy URL to your store listing and in-app
• Permissions not used — remove any manifest permissions that aren't actively used by app features
• Misleading listing — ensure your screenshots and description accurately represent the current app
• Broken functionality — ensure all test credentials (if you provided them to Google) work correctly
• Policy violations — read the specific policy cited, make the required changes, and reply via the appeals process if you believe the rejection was in error

FAQ