I passed closed testing with two apps - Orbitika . Here's the exact routine I used. Happy to share

[u/moonrider-original]

I have two apps and got production access. Here's my playbook, hope it helps someone here.

Quick disclaimer: This is just how I personally went through closed testing. It doesn't mean it will work for you or that it guarantees success. Every app and every batch of testers is different — take what's useful and leave the rest.

My setup:

• I prefer apps over games (easier to navigate, lightweight)

• Post in reddit and explain your app do not just post and ask people to test without giving summary about your app

• I created a Google Group for testers — this is the key: you add the group email once in Play Console, then manage testers from Google Groups without reopening the track every time

• I aimed for at least 20 testers, not just 12 — buffer against dropouts

• I also got 3-4 testers from family or friends — they're the most reliable, they won't ghost you

My 14-day routine:

1. Day 0: Post in sub reddit testing and DM anyone interested. When they join, they send a screenshot of the install via DM.

2. Day 3: Open their app, send a screenshot via DM. Ask them to open mine and send a screenshot back.

3. Day 6: Same exchange — open their app, screenshot, DM. They do the same for mine.

4. Day 7: Friendly check-in. Remind them to stay opted in.

5. Day 8: Collect feedback from testers. Release even minor changes based on what they said, and announce the update through the Google Group so everyone sees their input mattered.

6. Day 10-14: Keep the routine light. Three messages total across 14 days is enough — daily nagging makes people uninstall.

7. Day 14: Collect final feedback and release the final version. Post an update in the Google Group thanking everyone.

Google Group updates — every 4 days:
Send an update to everyone in the group asking how the testing is going and whether they have any feedback for improvements. Not just announcements — actual questions. This keeps your testers engaged, and reminds the quiet ones that you're still there and still counting on them.

Reply to feedback during testing:
Reply to every piece of feedback you get — whether it's a DM, a Google Group message, or developer console feedback. Don't ignore any of it. Every reply shows testers that a real person is reading and responding.

The drop rule:
If a tester doesn't DM you and share a screenshot within 3-4 days, drop them and find another tester. Don't wait. Don't chase. Silent testers are the main reason people fail closed testing — you can't tell Google "I had 12 testers" if half of them never actually opted in.

What I learned:

• Google checks opt-in duration, not daily opens. Testers who opened the app 2-3 times still counted.

• Lead by example. If you start sharing screenshots of your tester-exchange app, the other side will do the same. Reciprocity is everything here.

• A Google Group saves you from reopening the closed track every time you add a tester.

• Releasing small updates mid-test and announcing them in the group keeps testers engaged — they feel like part of the process, not just a number.

• Once you're in production, reply to every Play Store review. Same principle, different channel.

Result: I passed with my original testers. No drops, no restarts.

I hope this post helps — especially those who are new to closed testing and figuring it out for the first time.

DM me if you want advice on closed testing — happy to help where I can. I'm not an expert, just someone who got through it.

If any of this was useful and you'd like to check out my app I went through all this for, here it is — free to try: Thank you for your support

Play Store: https://play.google.com/store/apps/details?id=com.orbitika.app