Paramclasses Academy - Blog

Tutorials Details

←
Post 38 of 40
→

How to Publish a Flutter App on Google Play Store Step by Step

How to Publish a Flutter App on Google Play Store Step by Step

November 3, 2026

❖ Welcome to Param Classes!

✦ Introduction

After developing a Flutter application and generating an Android App Bundle (AAB), the next step is publishing it on the Google Play Store.

Publishing your application allows Android users to discover, install and use it through Google Play.

However, uploading an AAB file is not the only requirement. You also need to create a Google Play developer account, prepare your app information, upload screenshots, complete policy declarations, test your application and submit it for review.

In this tutorial by Param Classes, we will learn how to publish a Flutter application on the Google Play Store step by step.

✦ 1. What Is Google Play Console?

Google Play Console is the official platform used by Android developers to publish and manage applications on Google Play.

Using Play Console, you can:

  • Create a new application.

  • Upload APK or AAB files where supported.

  • Manage application releases.

  • Add app descriptions and screenshots.

  • Configure testing tracks.

  • Monitor crashes and performance.

  • Manage application updates.

  • Review publishing status.

Official website:

https://play.google.com/console/

You need a Google account and a Google Play developer account to publish an application.

✦ 2. Create a Google Play Developer Account

Before publishing your application, register for a Google Play developer account.

Follow these steps:

  1. Open https://play.google.com/console/

  2. Sign in using your Google account.

  3. Follow the developer account registration process.

  4. Choose the appropriate account type.

  5. Provide the required developer details.

  6. Complete identity and account verification.

  7. Pay the applicable registration fee shown during registration.

  8. Accept the developer terms and conditions.

Google may ask for additional information or verification depending on your account type.

Important: A developer account registration fee is generally required. Check the current amount and requirements on the official Play Console registration page before registering.

✦ 3. Prepare Your Flutter Application

Before uploading your application, make sure the Flutter project is ready for production.

Open your project in Android Studio or VS Code.

Run:

flutter doctor

Download project dependencies:

flutter pub get

Check your code:

flutter analyze

Run your application:

flutter run

Test important features such as:

  • Login and registration.

  • Navigation between screens.

  • API connectivity.

  • Database operations.

  • Form validation.

  • Image uploads.

  • Notifications.

  • Internet connectivity.

Fix important errors before creating the release version.

✦ 4. Set Application Name and Package ID

Every Android application needs a unique application ID.

Open the Android Gradle configuration file:

android/app/build.gradle.kts

For Kotlin DSL projects, check the configuration:

android {
    namespace = "com.example.myapp"

    defaultConfig {
        applicationId = "com.example.myapp"
    }
}

For projects using Groovy, the configuration may be inside:

android/app/build.gradle

Example:

defaultConfig {
    applicationId "com.example.myapp"
}

Replace the example application ID with your own unique ID.

Example:

com.paramclasses.studentapp

Choose carefully because the application ID becomes the permanent identity of your published application on Google Play.

✦ 5. Set Application Version

Before every release, check your application version.

Open:

pubspec.yaml

Find the version field:

version: 1.0.0+1

Here:

  • 1.0.0 is the version name.

  • 1 is the version code.

For your next update, you can use:

version: 1.0.1+2

Increase the version code for every new release uploaded to Google Play.

Flutter uses this version information when building the Android application.

✦ 6. Generate a Release AAB File

Google Play prefers the Android App Bundle format for publishing new applications.

Open the terminal in your Flutter project directory.

Run:

flutter clean
flutter pub get

Now generate the release bundle:

flutter build appbundle --release

After a successful build, your AAB file will normally be available at:

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

This is the file you will upload to Google Play Console.

Important: Your release bundle must be properly signed. Configure release signing and Play App Signing according to the official Flutter and Google Play instructions.

✦ 7. Create a New App in Google Play Console

Now open:

https://play.google.com/console/

Follow these steps:

  1. Sign in to your developer account.

  2. Open the Play Console dashboard.

  3. Click Create app.

  4. Enter your application name.

  5. Select the default language.

  6. Choose whether it is an app or a game.

  7. Select whether the application is free or paid.

  8. Provide a contact email address.

  9. Review the required declarations.

  10. Accept the applicable terms and create your app.

After creation, Play Console will show your application dashboard with setup tasks.

✦ 8. Prepare Your Google Play Store Listing

The store listing is the information users see when they visit your application page.

You should prepare the following details.

A. App Name

Choose a clear and professional application name.

Example:

Param Student App

B. Short Description

Write a short introduction explaining what your application does.

Example:

Learn programming and improve your technical skills with practical courses.

C. Full Description

Explain your application's features, benefits and purpose.

Example:

Param Student App helps students explore programming courses,
learning resources and educational updates.

Features:
- Course information
- Learning resources
- Student updates
- Easy navigation
- User-friendly interface

D. App Icon

Prepare a high-quality application icon according to Google Play's current asset specifications.

E. Screenshots

Capture screenshots of your actual application screens.

For example:

  • Home screen.

  • Login screen.

  • Dashboard.

  • Course list.

  • Profile screen.

F. Feature Graphic

Prepare a promotional graphic using the dimensions and requirements specified in Play Console.

Use genuine screenshots and accurate promotional information. Do not show features that your application does not actually provide.

✦ 9. Complete App Content and Policy Information

Before publishing, Google Play requires developers to provide information about their applications.

Depending on your app's features and target audience, Play Console may ask you to complete:

  • App access information.

  • Ads declaration.

  • Content rating questionnaire.

  • Target audience information.

  • Data safety form.

  • Privacy policy.

  • Permissions declarations.

  • Financial features or other applicable declarations.

Privacy Policy

If your application collects or handles personal information, prepare a suitable privacy policy and provide its publicly accessible URL where required.

The policy should accurately explain what information is collected, how it is used, how it is protected and whether it is shared.

Data Safety

Declare the relevant data collection, sharing and security practices accurately.

Your declarations must match the actual behavior of your application and any third-party SDKs it uses.

App Access

If your application requires login, provide Google with the access instructions or test credentials requested during review. Do not provide personal or production user credentials.

✦ 10. Upload Your AAB File

Now upload your Flutter release bundle.

For a first release, it is a good idea to begin with internal testing.

Follow these steps:

  1. Open your application in Play Console.

  2. Go to Test and release.

  3. Select Testing.

  4. Open Internal testing.

  5. Create a new release.

  6. Upload your generated app.aab file.

  7. Enter release notes.

  8. Review the release information.

  9. Save or roll out the testing release as prompted.

Google Play will process the uploaded bundle and display any detected errors or warnings.

Internal testing allows you to share your application with a limited group of testers before public release.

✦ 11. Test Your Application Before Production

Testing helps identify problems before your application becomes publicly available.

Google Play provides different testing tracks:

1. Internal Testing

Useful for quickly testing an application with a small group of testers. It supports up to 100 testers.

2. Closed Testing

Useful for testing with a selected group of users.

3. Open Testing

Allows a wider group of users to participate in testing, subject to the configured testing conditions.

4. Production

Makes the application available to Google Play users in the selected countries or regions after the required review and release steps.

Important for New Personal Developer Accounts: Personal accounts created after November 13, 2023 may have to complete Google's closed-testing requirement before production access. The commonly specified requirement is at least 12 testers continuously opted in for 14 days. Check your Play Console dashboard for the exact current requirement applicable to your account.

✦ 12. Submit Your App for Review and Publish

Once you have completed the required setup tasks and testing requirements, you can prepare a production release.

Follow these steps:

  1. Open your application in Play Console.

  2. Go to Test and release.

  3. Select Production.

  4. Click Create new release.

  5. Upload or select your AAB file.

  6. Add release notes.

  7. Review the release details.

  8. Resolve any blocking errors.

  9. Complete the required declarations.

  10. Submit the changes for review or start rollout, depending on the available Play Console workflow.

Google will review your application according to its policies.

After approval and rollout, your application can become available on Google Play in your selected countries or regions.

Note: Review times vary. Some developer accounts or applications may require additional review time.

✦ 13. How to Update Your Published Flutter App

After publishing, you may want to add new features, fix bugs or improve your application.

Follow these steps:

Step 1: Update your Flutter code.

Step 2: Increase the version in pubspec.yaml.

Example:

version: 1.0.1+2

Step 3: Generate a new release bundle:

flutter build appbundle --release

Step 4: Open Google Play Console.

Step 5: Create a new release in the appropriate testing or production track.

Step 6: Upload the updated AAB file.

Step 7: Add release notes and submit the update.

Always use the same application ID and the appropriate signing key arrangement for updates to your existing application.

✦ 14. Common Google Play Publishing Problems

1. App Bundle Upload Failed

Check whether the AAB file was generated successfully and whether it meets the current Play Console requirements.

2. Version Code Already Used

Increase the version code in pubspec.yaml and build a new AAB.

3. App Signing Error

Check your release signing configuration and upload key.

4. Privacy Policy Missing

Provide a valid, publicly accessible privacy policy URL wherever required.

5. Data Safety Form Incomplete

Review your application's data collection and sharing behavior and complete the declarations accurately.

6. Testing Requirement Not Completed

Check the testing requirements shown in your Play Console dashboard, especially if you have a new personal developer account.

7. App Rejected During Review

Read the policy issue mentioned in the rejection notice, correct the problem and submit a compliant version.

✦ 15. Google Play Publishing Checklist

Before submitting your application, review this checklist:

  • Google Play developer account created.

  • Developer identity verification completed where required.

  • Application ID configured.

  • Application version updated.

  • Release signing configured.

  • Release AAB generated.

  • App icon prepared.

  • Screenshots uploaded.

  • Store listing description completed.

  • Privacy policy provided where required.

  • Data Safety form completed.

  • Content rating questionnaire completed.

  • App access information provided where required.

  • Required testing completed.

  • Policy declarations reviewed.

  • Production release submitted.

✦ Conclusion

Publishing a Flutter application on Google Play Store is an important milestone for every Android developer.

From creating a developer account and preparing a store listing to generating an AAB file, completing testing and submitting your application for review, every step matters.

With proper preparation, you can make the publishing process easier and avoid common mistakes.

At Param Classes, we encourage students to learn complete Flutter app development through practical projects—from designing the user interface and connecting backend APIs to building release files and publishing Android applications.

Start preparing your own Flutter project and take your first step toward becoming an Android app developer.

Learn Today, Grow Tomorrow with Param Classes!

❖ Official Learning Resources

←
Post 38 of 40
→