12 Testers for Flutter Apps: Complete Google Play Closed Testing Guide

If you are a Flutter developer, you already know the advantage: one codebase, multiple platforms. But when it comes to publishing on Google Play, Flutter apps follow the exact same rules as native Android apps. That includes the mandatory Closed Testing requirement for new personal developer accounts.

Since November 2023, Google requires all new personal Play Console accounts to run a Closed Testing track with at least 12 real testers for 14 consecutive days before applying for production access. This applies regardless of whether you built your app with Flutter, React Native, Kotlin, or any other framework.

The good news: Flutter's build tools make generating the required Android App Bundle (AAB) straightforward. The challenge is the same one every Android developer faces — finding 12 real human beings who will install your app, use it every day, and stay engaged for two full weeks.

The 12-tester requirement applies to you if:

• Your Google Play Console account is a personal developer account created after November 13, 2023.
• You are publishing your first app (or first app in a while) and need production access.
• Your app is not being published under an organization account with a D-U-N-S number.

The requirement does not apply if:

• You have an organization account with a valid D-U-N-S number.
• Your personal account was created before November 2023.
• You have already passed production access on a previous app with the same account.

Most Flutter developers — especially solo developers and indie hackers — fall into the first category. If you are a solo Flutter developer publishing your first app, you almost certainly need 12 testers.

Before you can set up Closed Testing, you need a properly built and signed Android App Bundle. Here is the production-ready build command for Flutter:

This generates an .aab file at build/app/outputs/bundle/release/app-release.aab. This is the file you upload to Google Play Console.

Before building, verify:

• App signing — Your app must be signed with an upload key. Google manages the app signing key via Play App Signing.
• Version code — Increment your versionCode in pubspec.yaml or local.properties for each upload.
• Target API level — Google Play requires target API level 34+ (Android 14) as of August 2025.
• Internet permission — Add the INTERNET permission in AndroidManifest.xml if your app uses network calls.

Once your AAB is uploaded to Play Console, follow these steps to configure Closed Testing:

1. Create a Closed Testing track: In Play Console, go to Testing → Closed Testing → Create Track. Name it something recognizable like "alpha" or "closed-beta".
2. Upload your AAB: Upload the app-release.aab your Flutter build generated. Play Console will validate the bundle.
3. Complete the store listing: You need at minimum: app name, short description, full description, app icon (512×512px), feature graphic (1024×500px), at least 2 screenshots, privacy policy URL, and content rating questionnaire.
4. Set up the tester list: Create an email list or Google Group containing your testers' Gmail addresses. Google will email each tester an opt-in link.
5. Share the opt-in link: You will receive a unique opt-in URL. Share this with your testers. They must click it, accept the invitation, and install your app from Google Play.
6. Roll out to testers: Once your testers are added, click "Start rollout" to make the app available to them.

Finding 12 testers is the hardest part of the process. Here are the most effective methods for Flutter developers:

Method 1: Flutter developer communities (Free)

The Flutter community is large and active. Post your testing request in r/FlutterDev (150K+ members), the Flutter Community Discord, and Flutter Facebook groups. Offer to test other developers' apps in return — Flutter devs understand the struggle.

Method 2: Tester exchange platforms (Free or low-cost)

Platforms like TesterBee let you earn testers by testing other apps. This works well for Flutter developers because the tester pool includes real Android users who understand they need to stay engaged for 14 days.

Method 3: Paid testing services (Fastest)

Services like TesterBee provide 12 verified testers on real Android devices. They handle engagement monitoring, daily check-ins, and dropout replacement. This is the fastest path — testing typically begins within 24 hours — and comes with a production access guarantee.

During the 14 days, Google tracks several metrics to determine if your testing was genuine:

• Daily Active Users (DAU) — Google expects testers to open your app most days. If DAU drops to near zero, your production access application may be rejected.
• Session duration — Testers should spend meaningful time in your app. 30-second sessions are a red flag.
• Installed devices — Google tracks how many unique devices have your app installed during testing.
• App updates — Google wants to see that you pushed at least one update during the 14 days in response to testing feedback.

Specific advice for Flutter apps:

• Push a mid-testing update — even a small UI fix — to show Google you are iterating based on feedback.
• If using Firebase or any analytics SDK, verify events are being logged correctly on Android devices.
• Monitor crash rates in the Play Console pre-launch report for Flutter-specific rendering issues.

After 14 days of active testing, you can apply for production access. Google will ask you to answer a questionnaire with 6 questions about your testing process. Each answer must be under 290 characters.

What Google expects to hear:

• You recruited real testers who used your app on real devices (not emulators).
• Testers provided feedback and you acted on it (mention specific changes you made).
• Your app is complete and functional — not a placeholder or template.
• Engagement was consistent across the 14 days (not clustered on day 1 and day 14).

Once submitted, Google typically responds within 3-7 days. Many Flutter developers report approval within 48-72 hours when their testing was properly documented.

TesterBee provides a complete solution for Flutter developers who need to pass Google Play Closed Testing:

• 12 real testers on physical Android devices — No emulators, no fake installs. Real people using your Flutter app daily.
• 14-day engagement guarantee — Your testers stay active for the full testing period. If anyone drops out, they are replaced immediately.
• Production access support — Get help with the questionnaire and avoid common rejection reasons.
• Feedback and bug reports — Receive real user feedback, crash reports, and device compatibility notes from your testers.
• Earn free testing — Test other apps to earn coins, then use those coins to get testers for your own Flutter app at no cost.