r/AndroidClosedTesting • • Nov 29 '23

App testing requirements for new personal developer accounts, a minimum of 20 testers

111 Upvotes

There should be a few posts like this with the keywords, so that the new developers can find this Reddit on the Google easier and know where to find testers for testers.

This post here is only for Google SEO purpose.

In this sub r/AndroidClosedTesting you can find the people who can provide testing for testing, in order to pass your Google Play Console 20 testers policy.

Google Play is rolling out new testing requirements for developers with personal accounts created after November 13, 2023. These changes aim to enhance the app development process, encourage thorough testing, and ultimately deliver higher quality experiences to users. These requirements and the various testing tracks available on Play Console.

Developers with personal accounts created post-November 13, 2023, must adhere to new testing requirements. Before apps are eligible for distribution on Google Play, a closed test with a minimum of 20 testers is mandatory. These testers must have opted-in for the last 14 days continuously. Features like production and pre-registration in Play Console will remain disabled until these requirements are met. Applying for production access involves answering questions about the app, its testing process, and production readiness, ensuring a comprehensive understanding.

Play Console offers distinct testing tracks to facilitate a gradual testing process. Internal testing enables quick distribution to trusted testers during app setup. Closed testing, a prerequisite for production access, involves sharing the app with a controlled group of at least 20 testers. Open testing allows the app's test version to be visible on Google Play, with users providing private feedback. Developers must complete a closed test meeting specific criteria before applying for production access.

Tags: Google Play testing requirements, App development testing tracks, Personal developer account testing, Closed testing for app developers, Play Console testing criteria, 20 testing user Google Play policy.


r/AndroidClosedTesting • • May 02 '26 Heartwarming Bravo

Thank you to everyone guys!

Post image
83 Upvotes

Hey everyone,

just wanted to say thanks to this community 🙏

After testing, feedback, and a lot of iterations, my app finally got Google Play production access and is now live.

It’s called DriveLog — a simple app to track your car (fuel, expenses, maintenance, reminders) without accounts or subscriptions. Just clean and fast.

I started this as a solo project to solve my own problem, and seeing it actually live now feels crazy.

If anyone wants to check it out or give feedback (good or brutal, both welcome):
https://play.google.com/store/apps/details?id=com.torquelabs.drivelog

Thanks again, this sub actually helped a lot during the process.


r/AndroidClosedTesting • • Sep 23 '26

I got production access!

Post image
78 Upvotes

Thanks for all the testers, kleos music has passed to production thanks to all of you.


r/AndroidClosedTesting • • Dec 23 '25

Step-by-step instructions to create a Google Group and invite the testers to join

71 Upvotes

Hell everyone,

Earlier someone looking for the help with google group invite creation, even i had same issue when I started, thought to add this post, might help someone..

Step 1: Open Google Groups

  1. Go to https://groups.google.com

  2. Sign in with your Google account

Step 2: Create a New Group

  1. Click “Create group”

  2. Enter:

    • Group name (e.g., my-community)

    • Group email (auto-generated)

    • Description

  3. Click Next

Step 3: Set Group to Public (Important)

On the Privacy & permissions screen, choose:

  • Who can search for group → Anyone on the web

  • Who can join group → Anyone on the web

  • Who can view conversations → Anyone on the web

Click Next

Step 4: Create the Group

  1. Review settings

  2. Click Create group

✅ Your public Google Group is now live

Step 5: Share Public Join Link

  1. Open your group

  2. Click Group settings

  3. Copy the Group URL, for example:https://groups.google.com/g/my-community

  4. Share this link publicly (website, email, WhatsApp, LinkedIn, etc.)

👉 Anyone can open the link and click “Ask to join” or Join group

(Optional) Send Email Invites

  1. Go to Members

  2. Click Add members

  3. Enter email addresses

  4. Choose Invite (not Add directly)

  5. Send invite

Quick Tip

If you want instant joining without approval:

  • Go to Group settings → Access

  • Set Join the group → Anyone on the web (no approval)


r/AndroidClosedTesting • • 15d ago

🎉🎉 don't give up guys

Post image
69 Upvotes

r/AndroidClosedTesting • • Mar 29 '26

Thank you to everyone who supported me 🫡

Post image
63 Upvotes

r/AndroidClosedTesting • • Jan 03 '26

My app has been accepted into production on Google Play

Post image
62 Upvotes

Thanks to all!


r/AndroidClosedTesting • • May 29 '26

WE DID IT BOYS!

Post image
59 Upvotes

Thank you to all who participated in my closed testing! Each of you are a true blessing!


r/AndroidClosedTesting • • 26d ago

Chalk Runner game :) I’ll test yours back!

56 Upvotes

EDIT: CLOSED, thanks everyone! I have enough testers now. If you already joined, I’ll test yours back.

Hello there guys, I need testers to test play my game :)

40 levels in 4 chapters, plus Endless mode, you obviously do not have to play it all, but if somebody actually plays it and gives feedbacks even better :D

Join the Google Group: https://groups.google.com/g/chalk-runner-testers

Opt in to the test: https://play.google.com/apps/testing/com.profactor.chalkrunner

Install from Google Play: https://play.google.com/store/apps/details?id=com.profactor.chalkrunner

Keep it installed for 14 days. As I said you don’t need to play every day, just don’t leave the test (not sure if it has to be opened every day for some time? I think it does?)

Google is still approving the test build, so if links 2 and 3 say “not found”, join the group now. I’ll post in the group the moment they work.

If you want to see how game looks like and plays right now: Chalk Runner Dev Build

I did this with a lot of help from AI (Claude) for the code and art. I did the design, testing and decisions.

Drop your test link in the comments and I’ll join yours! Feedback as I mentioned is very welcome too, especially if anything flickers or a level feels unfair (People mentioned graphical bugs in the web version).


r/AndroidClosedTesting • • Aug 20 '26

Thanks guys

Post image
56 Upvotes

Thanks guys

My app has just been approved:

\- What I did, I simply asked the testers to sign up to my app and test as much as they could if possible

\- Leave a google review for me if possible, not must but I think it helps too

\- Published some updates during the testing process as Google asks some questions because they want to see if I have fixed the visitor issues during the testing time

\- I alread had a feedback mechanism in my app so it might also have helped


r/AndroidClosedTesting • • Jul 05 '26

I tested dozens of apps and found the same 7 mistakes every time

56 Upvotes

I build mobile apps, and recently I spent time testing a lot of apps across different categories.

One thing surprised me.

Most apps don't lose users because they look bad. They lose users because people don't know what to do when they first open it.

Here are the seven most common issues I found:

  1. No clear onboarding. Users shouldn't have to figure out your app alone. Show them what to do first in 3 steps or less.

  2. Slow load times. If your feed or home screen takes too long to load, users close the app and never come back.

  3. Too many features at launch. Less is more. Apps that try to do everything confuse users. One core feature done well beats ten average ones.

  4. No feedback when something happens. If a user posts, reacts, or deletes something, show them it worked. Silence creates doubt.

  5. Built for the developer, not the user. Many apps are designed around how the developer thinks, not how the user actually behaves.

  6. Apps that aren't finished. Please make sure your app is fully working before you release it. I have tested apps where buttons do nothing, screens are blank, and core features are completely broken. If a user opens your app and nothing works they will never come back. Test everything. Every button. Every screen. Every flow. If it doesn't work, fix it before you ship.

  7. Subscriptions too early. Asking users to pay before they have even experienced the value of your app is one of the fastest ways to lose them. Build your user base first. Monetize later. Nobody pays for something they don't trust yet.

You don't need a full rebuild to fix these. Sometimes one clearer button, faster loading, or a simple welcome screen makes all the difference.

What's the biggest app mistake you've seen recently?


r/AndroidClosedTesting • • Jun 18 '26

Thanks Good People!!!🥳🥳🥳

Post image
55 Upvotes

r/AndroidClosedTesting • • Feb 02 '26

Thank you! My app was Approved!

Post image
55 Upvotes

This is my first app. I'm not a developer. And my app was approved the first time around within 1 day. If you're curious, here's what I did.

  1. I enlisted 55 testers (my thinking: people will fall off. But at least 12 would remain to the end).

  2. Testers came from this group, FB and Reddit groups I'm in. And friends and family (yeah... I'm testing 60 apps on a rotating basis).

  3. I asked testers to open the app - only 3x over the 14 days.

  4. I checked stats in the Console: The app was opened every day, declining from 55 to 44 to 8 daily active users. 44 were installed the entire time.

  5. On days 10-14, I exchanged ratings/feedback (for developer only) with other apps. I think I received 5 ratings/feedback.

I hope this helps! Thank you for helping me! I'll keep testing the apps I have for about 5 more days.


r/AndroidClosedTesting • • Apr 15 '26

Thanks everyone!! I just want to share what I learned after one rejection

46 Upvotes

Thanks to this group, my first app is now on the Play Store!!

I want to share my experience in case it helps someone here.

My first attempt was rejected because of low tester participation.

So here’s what I did differently:

  1. I didn’t stop at just 12 testers. Based on the graph, during my first try, almost nobody was opening my app anymore by day 6 lol.

  2. The next time, I tried to get at least 30–40 testers.

  3. Even if the production button appears, don’t submit right away. Wait until you’ve completed the 14 days with at least around 20 testers.

  4. Keep updating your app during the 14-day testing period.

  5. Two real reviews are better than 10 that look fake.

  6. When answering Google’s questions, I was honest. I mentioned Reddit, the changes I made to the app, and the features I added.

  7. I don’t think all 12 testers need to open the app every day. In my case, only about 4 people opened it daily.

  8. Your app needs activity, so keep looking for testers every day during the testing period.

  9. Even if other people don’t test your app, you should still test theirs. As a Software Engineering student, I learned a lot by trying other apps. Some ideas were so good that I ended up implementing them in my own app, and others showed me what to avoid lol

  10. Also, check the comments after posting your links. Sometimes the bot deletes some of them.

Hope this helps someone, and thanks again to everyone here for the support.

Here is my app link if anyone wants to try it. I’m also open to testing other apps:
https://play.google.com/store/apps/details?id=com.pulsescanner.lan


r/AndroidClosedTesting • • May 03 '26

Please if you stop testing at least don't uninstall the app.

Thumbnail
gallery
44 Upvotes

It's a shame to see some people (just a few) uninstalling your app a week later.

I'm still testing your apps guys and I still need testing for another week.

Thank you for the guys still testing 🙏


r/AndroidClosedTesting • • Sep 06 '26

Got approved for production - how you can do it too

Thumbnail
gallery
43 Upvotes

This subreddit is great for padding the 12 users needed but horrible for getting any actual testing done. Out of the 12 users I obtained from this subreddit I got a total of 2 users who actually used the app and that wasn’t regular either.

I built an app to help with spiraling when emotions get overwhelming or simply getting help with your self confidence: Undine.app

I’m an actual developer so I did what I would have done in any actual pre release testing.

What I did that helped with prod approval:
- I got 7 friends to download the app and actually try to use it at least once a day for 90% of the test period. This meant the app actually had active users.
- released builds regularly either with fixes or improvement based on feedback, I had 6 builds pushed during the 14 day period, would have gone for more but not enough time.
- keep a change log of what you pushed, this will help when you need to explain what you updated or fixed during the review phase.

Unfortunately what I suspected would happen came true and barely a single person who agreed to test actually did so, many thanks to the two users who at least did that for a few days. Feel free to leave any questions and I’ll reply with what I know

All the best and may your approval go through :)


r/AndroidClosedTesting • • Dec 30 '25

Thank you for helping me through closed testing. Here's what I learned as a first-time dev (tips for newcomers)

41 Upvotes

Hey everyone,

A few months ago I posted here looking for testers. You helped me hit the 12-tester requirement and gave feedback that actually made my app better. I wanted to say thank you and share what I learned along the way – maybe it helps someone who's just starting out.

What I learned about closed testing

The 12-tester / 14-day wall is real

You need 12 testers to keep your app installed for 14 days straight before you can go to production. Sounds easy. It's not. Most people download, try once, uninstall.

This sub and communities like BetaCircle were the difference – people here actually keep apps installed because they understand the struggle.

Aim for 30-40 testers, not 12

Some testers will uninstall early. Life happens. If you only have exactly 12, one person dropping out resets your counter. Get 30-40 to be safe.

Be prepared to invest time

Finding testers here means giving back. You'll spend several days downloading apps, testing them properly, taking screenshots as proof. It's not a quick thing – budget real time for it.

Use Google Groups

Set up a Google Group for automatic tester registration. People join the group → automatically become testers. Way smoother than manual invites. Wish I'd known this from day one.

Respond to EVERY bug report

Even if it's something you can't fix immediately. People who report bugs are your best testers. They care enough to tell you what's wrong instead of just uninstalling.

Mistakes I made (so you don't have to)

1. In-app purchases are harder than you think

I spent weeks debugging payment issues. Version mismatches between libraries, API conflicts, unclear error messages. Budget extra time for this. Read the documentation carefully – AI tools can help debug, but YOU need to understand what's actually happening.

2. Don't rush to production

I was so eager to "launch" that I pushed before the app was ready. Take the full 14 days. Use them. The feedback you get is gold.

3. Test on multiple devices

What works on your phone might crash on someone else's. I learned this the hard way when testers reported bugs I couldn't reproduce.

4. Keep your testers updated

When you fix something, tell them. People appreciate knowing their feedback mattered. A simple "Fixed in v1.2" comment builds goodwill.

5. Not preparing for the production access questionnaire

After 14 days, you don't just click "go live." Google asks detailed questions: What feedback did you receive? What changes did you make? How did you collect feedback? Why is your app ready for production?

I wasn't prepared for this. What saved me: my changelogs and git commits. I fed them to AI and asked it to summarize all bug fixes, tester feedback, and improvements into a coherent report. 30+ fixes, device-specific issues, UI improvements – suddenly I had a solid answer for every question.

Lesson: Document everything from day one. Every bug report, every fix, every tester comment. When Google asks "what did you learn?" – you'll have the answer ready instead of scrambling.

6. Underestimating changelogs and store pages

Every update needs release notes – Google Play limits you to 500 characters per language. Writing these manually for 30+ versions is painful. AI tools helped me a lot here: I'd summarize my git commits into changelogs, then condense them for the store. Huge time saver.

Also: your store listing matters more than you think. Screenshots should show actual gameplay, not just your logo. Short description (80 chars) needs your main keywords. Long description – structure it with emojis and sections, people skim.

7. Overcomplicating my website

I initially tried to build something fancy. Wasted time. What worked: a simple landing page with one goal – the download button. No fancy frameworks, just HTML/CSS. AI helped write the code. For multiple languages, I made separate pages instead of building a language switcher. Easier.

What actually worked

  • This sub + BetaCircle. People here understand the struggle.

  • Responding to every comment. Even just "thanks for trying it out" matters.

  • Being honest about what's broken. People respect that more than fake polish.

  • Small, frequent updates. Fix bugs fast. Show that you're actively working on it.

  • Using AI for the boring stuff. Changelogs, store descriptions, website code – let AI draft it, then edit. Saves hours.

For other first-timers

  1. Post here early. Don't wait until your app is "perfect."

  2. Offer to test other people's apps. It's a community, not a billboard.

  3. Expect things to break. That's normal.

  4. Read error logs carefully. Most bugs have clear causes once you look.

  5. Take feedback seriously, even when it hurts.

  6. Prepare your store page properly – screenshots, descriptions, keywords. It's your first impression.

Thank you

To everyone who installed my app, kept it for 14 days, reported bugs, or just left an encouraging comment – thank you. This community made it possible.

Some of you might remember Anpfiff1 (the retro football manager). That was my project. It's now live and I couldn't have done it without the testers from here.

Happy to answer questions about the process in the comments.


r/AndroidClosedTesting • • Feb 08 '26

Thanks to this community, we are ready to go!

Post image
40 Upvotes

Thanks to this community, my app Temp Mail got production access!

It was tough to reach the 12 testers, then wait for 2 whole weeks, but the wait is over and I am granted the production access!

Thanks, and good luck to fellow developers


r/AndroidClosedTesting • • 22d ago

Looking for 12 testers for Paper Launcher, a poster-style home screen for Android (free, no ads)

Thumbnail
gallery
38 Upvotes

Hi everyone! I've built Paper Launcher, a home screen that makes your phone look like a printed poster: bone-white paper, black ink, one red accent and big bold type.

How to join (takes 2 minutes)

  1. Join the tester group: https://groups.google.com/g/paper-launcher-testers - use the Google account that's signed in to the Play Store on your phone.

  2. Opt in to the test: open https://play.google.com/apps/testing/com.paperlauncher and tap Become a tester.

  3. Install it: tap Download it on Google Play on that page, or search the Play Store from the same account. If Play says "item not found", wait about 15 minutes and try again.

  4. Set it as your home app.

  5. Stay in the test for 14 days. You don't have to use Paper as your main launcher the whole time, but please don't uninstall it or leave the test. Opening it now and then helps a lot.

Feedback, bug reports and ideas are very welcome, either in the comments or by email: [email protected]

Some things I'm proud of

  • Depth effect: pick a photo for the picture widget and Paper finds the subject (a person, a pet, an object) and lets it stand in front of the big numbers, like a magazine cover. It runs entirely on your phone using Google's ML Kit.

  • Automatic black-and-white photos: any photo you choose is automatically turned into black-and-white newsprint so it matches the paper look. You can also keep the built-in engraved landscape drawing.

  • Icons that fit the theme: app icons can keep their original colours, or be tinted mono, ink or your accent colour so they blend into the paper. Tip: this looks best with an icon pack that uses line icons without a background shape, like Whicons or White Moonlight Icon Pack.

  • A free-form grid where you place, resize and merge tiles, plus clock, calendar, month view, weather, music controls, battery, signal, storage & RAM, quotes and Google search widgets.

  • Back up your settings to a file and restore them later.

Why it asks for permissions (all optional)

  • Location: only for the weather widget. Your coordinates are sent over HTTPS to Open-Meteo, a free weather service, to get your local forecast. Nothing is stored and no account is needed. Say no and only the weather widget stops working.

  • Notification access: Android only lets a launcher show "now playing" music if it has notification access. Paper uses it only to read the music player (song, artist, artwork and play/pause). It never reads, stores or sends your notifications. Skip it and only the music widget is affected.

  • "Match your wallpaper" on first launch: Paper asks once whether to set a plain paper wallpaper. That's because Android itself, not the launcher, draws your wallpaper at a few moments: behind the blurred Recent Apps screen, and while an app slides closed back to home. With a different picture there, it flashes behind Paper at those moments. Only the home-screen wallpaper changes; your lock screen stays the same. Paper can't save your current wallpaper, so choose "Keep my wallpaper" if you want to keep it. You can change this later in Settings > Look > Wallpaper.

No account, no ads, no tracking.

Requires Android 10 or newer. Thanks so much for helping! 🙏


r/AndroidClosedTesting • • Feb 15 '26

Special thanks to my testers🙏

Post image
38 Upvotes

Thank you for your help! I hope Google will approve my application for production. Mole Collect coming soon.


r/AndroidClosedTesting • • Feb 20 '26

My App (KanbanTab) Got Approved on the First Try! 🎉 Here's What I Learned

Post image
36 Upvotes

After registering my Google Play Console account, I was devastated to find out that I needed 12 (active) testers for 2 weeks, but thanks to this community everything went smoothly and I can finally see my app in the Play Store.

I have seen so many developers who had their app testing rejected (sometimes even multiple times), which must feel so discouraging. I really wish I could help out to pinpoint what the problem might be because it doesn't seem like Google gives you a detailed reason for why your app was rejected - but I will give you the details I have in case it will help someone in the future.

1. Don't expect every tester to be reliable
According to my Google group, I have 51 members, most of which even sent me a screenshot of testing my app. However, according to Google, there was only 26 testers in total.

2. Release updates for your app
I made three updates to my app in total during these two weeks. The first update was a small bug fix so my app doesn't lay underneath the Android's top bar. The second update came from feedback which included adding a light theme to my app. I get the impression that these updates are important to get approved because after you get approved you will have to answer a questionnaire about how the testing went, and one section was about updates.

3. Don't use paid testing services
During the questionnaire I mentioned, Google will ask you where you got your testers from. Google genuinely wants you to have a proper two weeks testing, so if you use testers who are flagged for being a paid service, there's a higher chance that your app will get rejected. I don't have any proof of this but it makes sense considering how Google worded the question in the questionnaire.

Here is my app, KanbanTab, if you want to check it out:
https://play.google.com/store/apps/details?id=com.kanbantab.app

Thank you everyone who tested my app!

I will remain active in here for a little while longer because I am still testing apps for other people. I wish you all good luck and I hope you get your app approved on the first try like me. Please let me know in the comments if you have any questions.

(I won't test new apps at this moment because the apps I'm testing right now only have a few days remaining before hitting the two weeks mark)


r/AndroidClosedTesting • • Jan 07 '26

App has been approved!

Post image
36 Upvotes

Thank you to everyone who joined my closed testing group and helped me get production access! For those who are in the process of testing, I'll give some insight that might be useful. I had 28 people join my Google group from this community, they installed my app and opened it at least once, some others tested features more thoroughly, but I'm certain almost none actually opened the app daily. I made three releases / updates in my closed testing track, and I did not apply for production access on the 14th day, I waited a few days after because I needed to fix a few bugs. After applying for production access and answering the questionnaire carefully, I was approved in a little over 24 hours. Once again, thank you to everybody who helped me out and I hope the apps I tested also get production access.


r/AndroidClosedTesting • • Jul 06 '24

INFORMATION MESSAGE!

36 Upvotes

We're here to support each other, guys. Please do not uninstall the applications you downloaded before 14 days, they may remain on your phone for a while longer. I am writing this to avoid any problems during the test. Thank you.


r/AndroidClosedTesting • • Jun 25 '26

Thank you everyone my app has now been published on play store <3

35 Upvotes

Thank you so much for testing my app
its finally on play store now

if anyone wants to check it out heres the link


r/AndroidClosedTesting • • Aug 26 '25

Thank you everyone for testing!

Thumbnail
gallery
35 Upvotes

Thank you everyone for testing the app, I will continue testing everyone's app for a few days to make sure y'all also get approved!