PeerPlay
Most advice about Google Play closed testing assumes a phone app. You post your opt-in link, people install it on their phone, and the 14 days start counting. If you built a watch face, a Wear OS app or an Android TV app, that advice leaves out the hardest part.
The rule for new personal developer accounts is the same: at least 12 testers opted in to your closed test for 14 days in a row before you can apply for production. What changes is who can actually test. Almost everyone who offers to test has a phone. Far fewer people have a Wear OS watch, and fewer still have an Android TV or Google TV device they are willing to install test builds on.
Why phone-only testers are a risk for watch and TV apps
A tester can join your test from any browser with a Google account, so a phone owner can opt in to a watch face test without any trouble. Your opted-in count goes up. But if they have no watch, they never install and never open your app.
Google does not publish exactly how it judges a closed test, so be careful with anyone who promises otherwise. What it does say in the production application is that it wants to know how testers engaged with your app and what you learned. A watch face that 12 people joined but nobody wore is a weak story to tell, and it gives you no real feedback about battery, layout on round screens or how your complications behave.
So for these apps the question is not only how to get 12 testers. It is how to get 12 testers who own the device.
Set up the test for the right device
Before you recruit anyone, check that the build is actually offered to the device. Play Console has form factor settings and separate release tracks for Wear OS and Android TV. If your watch or TV build sits on the wrong track, testers opt in and then see nothing to install on their watch or TV.
Test the path yourself with a second Google account if you can. Opt in from the web link, then open the Play Store on the watch or on the TV with the same account and look for your app. If it is not there, fix that first. Every tester you recruit before this works is a tester you may lose.
Write down the install steps for testers in plain words. For a watch: join from the link on your phone or computer, then open the Play Store on the watch and search for the app, or install it from the phone's Play Store if your watch is listed as a device. For a TV: join with the same Google account that is signed in on the TV, then find the app in the TV's Play Store. Short steps like these save you a lot of messages later.
Where to find people who own a watch or a TV
Start with other developers in the same niche. Watch face and Wear OS developers own watches, because they need them to build and check their own work. A swap between two watch face developers is the most natural swap there is: each of you has exactly the device the other needs. Developer forums for watch faces, including the Samsung developer forum, have threads where people ask for exactly this.
Look in communities where owners already talk about their devices. Subreddits and Discord servers about Wear OS, Galaxy Watch, Pixel Watch and Android TV boxes are full of people who like trying new watch faces and apps. Offer something useful in return, such as free premium access or an early version, and ask only people who say which device they own.
Ask your own users. If you already have a phone app with users, a short in-app or email message asking who owns a Wear OS watch can find testers who already trust you.
Recruit more than 12 and check every day
With phone apps the usual advice is to recruit 15 to 20 people instead of exactly 12, because some never join and some leave. With watch and TV apps the buffer matters even more, because each replacement is harder to find. Start with the bigger group on day one, not after someone drops.
Check your opted-in tester count in Play Console every day. If it drops below 12, the 14 days may have to count again, which costs you weeks on a watch or TV app. Message anyone who has gone quiet, and keep one or two backup testers you can invite the same day.
Ask testers for one short note during the test: which watch or TV model they use, and whether anything looked wrong. That gives you real answers for the production application instead of a vague line about testing.
If you cannot find enough device owners
Do not quietly fill the gap with phone owners who will never install the app. You may pass the count and still have nothing to say about how people used it.
PeerPlay is starting a Wear OS and Android TV package for this exact problem: testers who own your device type, opening your app every day for the 14 days, with nothing to test in return. It is in early access while we build the watch and TV tester group, so you request it from the pricing page and we confirm a start date. If you own a Wear OS watch or an Android TV, you can also join as a paid tester from the same page.
FAQ
Does the 12 testers rule apply to watch faces and Android TV apps?
The closed testing requirement applies to new personal developer accounts, not to a type of app. If your account is covered, a Wear OS app, a watch face or an Android TV app needs 12 testers opted in for 14 days before you can apply for production.
Can a tester without a watch join my watch face test?
They can opt in from any browser, so they count as opted in. But they cannot install or use a watch face without a watch, so you get no real use and no feedback from them.
How do testers install a Wear OS app from a closed test?
They join with the opt-in link, then open the Play Store on the watch with the same Google account and find the app there. Some can also install it to the watch from the phone's Play Store. Test this path yourself before you recruit.
How many testers should I recruit for a watch or TV app?
Aim for 15 to 20 instead of exactly 12. Replacements are harder to find for watch and TV apps, so the buffer should be in place on day one.