Pass your 14-day closed test. Skip the daily screenshots.
Fourteen will match you with Android developers who test your app while you test theirs. Real use gets checked automatically, so your day goes to fixing your app.
You're on the list.
Groups need enough developers to start. Know someone stuck on the 12-tester rule? Send them this page.
What we're building differently
| Part of the test | Typical tester swap | Fourteen (planned) |
|---|---|---|
| Proof of testing | Upload a screenshot for every app, every day | A small SDK confirms real use. Screenshots stay as a fallback if you'd rather not add it. |
| Penalties | Points or removal, with little room to explain | A warning first, and a person reviews every appeal |
| Talking to testers | Often limited or paid | Free messaging inside your group |
| New builds | Testers can stay on an old version | One tap tells your group to update |
| Production form | You piece the answers together at the end | Feedback and fixes collected as you go, ready for you to review |
How it will work
Tell us when your app is ready
We'll show an expected start date before you commit, so you aren't left waiting on a half-full group.
Join a group with extra testers
Everyone opts in from day 1. Google counts only testers who stay opted in for 14 consecutive days, so the spare testers have to start with you.
Use each other's apps
Follow short tasks such as finishing onboarding or trying the main feature, then leave a line or two of feedback.
Apply for production with real notes
Google asks how testers used your app, what they said, and what you changed. You'll have that record in one place.
Questions
Can I use it today?
Not yet. Fourteen is in development, and the features on this page are plans. Waitlist members will hear first when groups open.
Does this apply to my account?
Google's rule covers personal developer accounts created after November 13, 2023. They need at least 12 testers opted in continuously for 14 days.
Will this guarantee production access?
No. Google makes that decision, and nobody can promise it. Fourteen is meant to help you run a real test and describe it accurately.
What would the SDK collect?
The plan is to confirm that a tester opened and used your app, and nothing about what's inside it. Exact details will be published before launch, and the SDK will be optional.