How to Publish a FlutterFlow App on Google Play
Two routes from FlutterFlow to Google Play: one-click deployment with a service account, or downloading the Flutter code. Plus the closed test.
Short answer
Either use FlutterFlow’s Google Play deployment (it needs your Play Console app and a service account key), or download the code and build it as a normal Flutter app with flutter build appbundle. Either way, a new personal account still needs a closed test with 12 testers for 14 days before production.
Route A: deploy from FlutterFlow
FlutterFlow can build and upload your Android app for you. In general terms:
- Create the app in Play Console first, with the same package name as in FlutterFlow’s settings, and complete the store listing and App content.
- Create a Google Cloud service account, give it release permissions in Play Console (Users and permissions), and download its JSON key.
- Add the key in FlutterFlow’s mobile deployment settings, choose the track, set the version, and deploy.
Google’s publishing API generally can’t create the very first release of a new app, so you may need to upload the first .aab by hand. FlutterFlow’s current docs describe the exact flow. Check them because the UI changes often.
Route B: download code and build
- Download the project code (or connect GitHub).
- Open it in your Flutter environment and run flutter pub get.
- Follow publish a Flutter app on Google Play: keystore, signing config, pubspec version, flutter build appbundle.
Route B gives you full control and is easier to debug when something fails.
FlutterFlow-specific checks
| Check | Why |
|---|---|
| Package name in FlutterFlow settings | Must match Play Console. It’s permanent |
| Firebase or Supabase auth | Add an account deletion path if users can sign up |
| Permissions toggled in settings | Each one must be justified in your Data safety form |
| Test mode data | Remove demo content before testers arrive |
| Target API | Builds must target API 36 since August 31, 2026 |
Then: the closed test
Add 15-20 testers, keep at least 12 opted in for 14 days, ship at least one update based on feedback, and apply for production access. FlutterFlow makes shipping fixes quick, which is useful evidence.
Frequently asked questions
Do I need a paid FlutterFlow plan to publish?
Code download and one-click deployment depend on your FlutterFlow plan. Check FlutterFlow’s current pricing before relying on either route.
Can I keep editing in FlutterFlow after downloading the code?
Yes, but local code changes can be overwritten by the next export. Decide which one is your source of truth.
Where do I set the version number?
In FlutterFlow’s mobile deployment settings, or in pubspec.yaml if you build locally. Increase the build number every upload.
Sources and how we keep this accurate
- Play Console Help: App testing requirements for new personal developer accounts
- Android Developers: Meet Google Play’s target API level requirement
- FlutterFlow docs: Google Play Store deployment
Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start freeKeep reading
How to Publish a Flutter App on Google Play (2026)
How to Publish an AI-Built (“Vibe-Coded”) App on Google Play
How to Add an Account Deletion Link for Google Play
Closed Testing for Wear OS Apps: Finding Testers With Watches
How to Generate a Signed App Bundle in Android Studio
Closed Testing for Android TV and Google TV Apps
Browse all guides, or see the quick answers, guides and comparisons.