Checklist You Need Before Deploying a New Application to Google Play Store

Deploying a Flutter app to the Google Play Store is not just about uploading an APK or AAB file. Before publishing, you need to make sure your app is properly tested, optimized, signed, policy-compliant, and ready for real users.

This checklist will help you prepare your Flutter application before submitting it to the Google Play Store.

Checklist You Need Before Deploying a New Application to Google Play Store

1. Update App Name, Icon, and Package Name

Before creating a release build, confirm that your app name, launcher icon, and package name are final.

Your package name should be unique because it cannot be changed after publishing the app on Google Play.

Check the following:

• App name is correct
• App icon is updated
• Package name is final
• Splash screen is configured
• App theme and branding are consistent

2. Update Version Name and Build Number

Every release must have a proper version name and build number.

In Flutter, you can update this in the pubspec.yaml file:

version: 1.0.0+1

Here:

• 1.0.0 is the version name shown to users
• 1 is the build number used by Google Play

For every new release, increase the build number.

3. Remove Debug Code and Test Data

Before release, remove all development-related code and temporary data.

Make sure you remove or update:

• Debug print statements
• Test API URLs
• Dummy credentials
• Unused files
• Development-only packages
• Test payment keys
• Console logs

Your production app should connect only to production APIs and services.

4. Test the App in Release Mode

Many issues appear only in release mode. So, do not rely only on debug testing.

Run your Flutter app in release mode:

flutter run --release

Also test the final build on real Android devices.

Check:

• Login and signup
• OTP verification
• Payment flow
• Push notifications
• API response handling
• App performance
• App startup time
• Crash scenarios
• Offline behavior

5. Run Flutter Analysis and Tests

Before building the final app bundle, run these commands:

flutter clean
flutter pub get
flutter analyze
flutter test

These commands help you find code issues, dependency problems, and test failures before release.

6. Review Android Permissions

Check your Android permissions carefully. Only keep the permissions your app actually needs.

Review this file:

android/app/src/main/AndroidManifest.xml

Common permissions include:

<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />

Avoid unnecessary permissions because they may create policy issues or reduce user trust.

7. Configure App Signing

Google Play requires your release build to be signed.

You need to:

• Create a release keystore
• Configure key.properties
• Add signing config in android/app/build.gradle
• Keep your keystore file and passwords safe

Never upload your keystore file to GitHub or any public repository.

8. Build Android App Bundle

Google Play recommends uploading an Android App Bundle, also known as an .aab file.

Use this command:

flutter build appbundle --release

After the build completes, your app bundle will usually be generated here:

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

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

9. Check Target SDK Version

Make sure your app targets the required Android SDK version according to the latest Google Play requirements.

You can check and update it in:

android/app/build.gradle

Look for:

targetSdkVersion

Keeping the target SDK updated helps your app meet Google Play policy requirements and Android security standards.

10. Add Privacy Policy

A privacy policy is required if your app collects or uses personal data such as:

• Name
• Email
• Phone number
• Location
• Camera access
• Contacts
• Files
• Payment information
• Device identifiers

Add your privacy policy URL in Google Play Console and inside the app if needed.

11. Complete Data Safety Form

In Google Play Console, you must complete the Data Safety section.

Declare clearly:

• What data your app collects
• Why the data is collected
• Whether data is shared with third parties
• Whether data is encrypted in transit
• Whether users can request data deletion

Make sure your answers match your actual app behavior.

12. Complete Content Rating Questionnaire

Google Play requires every app to complete a content rating questionnaire.

You need to answer questions about:

• Violence
• Sexual content
• User-generated content
• Purchases
• Gambling
• Location sharing
• Online interactions

Submit accurate answers to avoid rejection or incorrect app rating.

13. Prepare Store Listing Details

Before publishing, prepare all Google Play Store listing content.

You will need:

• App title
• Short description
• Full description
• App icon
• Feature graphic
• Phone screenshots
• Tablet screenshots, if supported
• Category
• Tags
• Contact email
• Website URL
• Privacy policy URL

Recommended image sizes:

AssetRecommended SizeApp icon512 × 512 pxFeature graphic1024 × 500 pxPhone screenshotsAt least 2 screenshotsTablet screenshotsRequired if supporting tablets

14. Test Using Internal Testing

Do not publish directly to production.

First, upload your app bundle to the Internal Testing track in Google Play Console.

Internal testing helps you:

• Test installation from Play Store
• Check Play signing
• Verify in-app updates
• Test payments
• Find crashes
• Review device compatibility
• Check the pre-launch report

Fix all major issues before moving to production.

15. Review Pre-Launch Report

Google Play automatically tests your app on different devices and provides a pre-launch report.

Review:

• Crashes
• ANRs
• Accessibility issues
• Security warnings
• Performance issues
• Screenshot problems

If the report shows serious issues, fix them before production release.

16. Check App Security

Before launch, review your app security.

Important checks:

• Use HTTPS APIs
• Do not hardcode secrets
• Restrict Firebase/API keys
• Secure user authentication
• Protect payment flows
• Validate user inputs
• Store sensitive data securely
• Enable code obfuscation if required

Flutter obfuscation command:

flutter build appbundle --release --obfuscate --split-debug-info=build/debug-info

17. Set Pricing and Distribution

In Google Play Console, configure:

• Free or paid app
• Countries and regions
• Device types
• Android phone/tablet support
• Ads declaration
• App category
• User age group

Double-check everything before submitting for review.

18. Final Review Before Submit

Before clicking submit, confirm the following:

• App bundle uploaded successfully
• Version code is correct
• Store listing is complete
• Privacy policy is added
• Data Safety form is completed
• Content rating is completed
• App access instructions are added if login is required
• Target SDK is compliant
• No policy warnings are pending
• Internal testing is completed
• Pre-launch report is reviewed

19. Submit App for Review

Once everything is ready, submit your app for review from Google Play Console.

Google will review your app for policy compliance, store listing accuracy, privacy, permissions, and app behavior.

After approval, your app can be published to the Play Store.

20. Monitor After Launch

Deployment does not end after publishing.

After launch, monitor:

• Crashes
• ANRs
• User reviews
• Ratings
• Installs
• Uninstalls
• Performance
• Play Console warnings
• Firebase Crashlytics reports

Use this feedback to improve your next release.

Final Flutter Release Command

Use this final command sequence before deployment:

flutter clean
flutter pub get
flutter analyze
flutter test
flutter build appbundle --release

Conclusion

Publishing a Flutter app to the Google Play Store requires proper preparation. You need to test your app, configure release signing, build an app bundle, complete Google Play Console requirements, and follow Play Store policies.

By following this checklist, you can reduce rejection chances, avoid release issues, and launch your Flutter app with more confidence.