The independent developer’s launch guide

A better closed test starts with a clear plan.

From the first install to your production application, here’s how to give your app a useful test and your fellow developers a good experience.

1. 1

   Prepare a test people can actually complete

   • Roll out a working release to a closed-testing track and copy its opt-in link.
   • Walk through sign-in and the main task on a real phone. Make test credentials available if your app needs them; never share your personal password.
   • Check device and country availability so the developers in your Pack can install the app.
   • Write down three things to test: the first-run experience, your main feature, and an important edge case.
2. 2

   Connect your phone and join the queue

   • Install the companion app and sign in with the same Google account as the website.
   • Join the TestersTrade testers Google Group with that same account. It’s a one-time step that lets you opt in to every Pack app.
   • Make space for up to 15 apps and plan time to use them and give feedback.
   • Add your app name, package name, and closed-testing opt-in link. Matching depends on the number of available developers.
3. 3

   Give your Pack access

   • On your closed-testing track’s Testers tab, choose Google Groups and add testers-trade@googlegroups.com before you submit. You never paste individual emails.
   • Keep the group on the track and a release rolled out until your test ends. Replacement testers reach your app automatically.
   • Use each assigned app’s opt-in link with the correct Google account before installing it.
4. 4

   Make every check-in useful

   • Use the apps yourself. Install checks cannot replace real testing or establish Google Play opt-in.
   • Day 1: describe whether you understood the app and completed the first task.
   • Day 7: explore the main features. Explain any issue with steps to reproduce it, what you expected, and what happened.
   • Day 13: revisit the experience and describe the biggest remaining obstacle. Add a screenshot when it helps, avoiding private information.
   • Review missed-check warnings and open the companion app if a check is missing.
5. 5

   Review the evidence before applying

   • Review your test in Play Console and confirm that its eligibility requirements are met there.
   • Read the feedback, fix the issues you can reproduce, and record what changed in your app.
   • Use your TestersTrade report as a factual starting point. Add your own account of engagement, improvements, audience, and readiness.
   • Keep testing if more work is needed. Completion in TestersTrade does not guarantee Google’s approval.