Probably yes, using a separate Google account on that device. But it barely helps, and it is not the question worth asking.
Google does not publish an explicit rule saying your own account cannot be one of the twelve. What it publishes is the requirement itself: at least 12 testers opted in continuously for 14 days. Your own second account is one of those twelve. You still need eleven more.
The question people are really asking is whether they can make up the whole twelve themselves. That answer is a clear no, and it is worth understanding why.
What does Google actually require?
The rule is that a personal developer account created after 13 November 2023 must run a closed test with a minimum of 12 testers who have been opted in for at least the last 14 days continuously.
Three things follow from that:
- Each tester is a distinct Google account that completed the opt-in through your link.
- They install from the Play Store on a real Android device.
- Since 2026, Google also evaluates whether those testers genuinely used the app, and rejects applications for insufficient testing engagement when they did not.
Nothing in there names you specifically. That is why the honest answer to the literal question is “probably, but it does not matter much”.
Why does my own phone not help?
Arithmetic. One account is one twelfth of the requirement.
If you are asking this question, you are almost certainly short of testers, and adding yourself moves you from needing twelve to needing eleven. It does not solve the problem, it just makes the number slightly less round.
There is also a practical catch. You are the developer. You already use the app constantly and you know exactly how it works, so you generate none of the thing testing exists to produce: the experience of someone encountering it for the first time.
So can I just make 12 accounts?
No. This is the shortcut almost everyone considers, and it is the one that carries real consequences.
Creating multiple Google accounts to test your own app is precisely the pattern Google’s enforcement systems are built to detect. In 2025 Google banned more than 80,000 developer accounts and blocked over 1.75 million policy-violating apps from being published.
Consider what the record looks like from Google’s side: twelve accounts created around the same time, on a small number of devices, all installing the same app, all with near-identical activity patterns, none of them existing before your test began. That is not a subtle signal.
The downside is asymmetric. The upside is skipping a couple of weeks of recruiting. The downside is losing the developer account, and with it the app you spent months building.
What about emulators?
No, for two separate reasons.
Emulators do not produce the engagement signals a real device does, and a test made up largely of them looks artificial for the same reasons multiple self-made accounts do. Beyond policy risk, an emulator also tells you nothing useful about real-world performance, battery behaviour or how your layout survives on a five year old midrange phone.
Testing on emulators during development is normal and sensible. Using them as your twelve testers is not.
Can I use my family’s phones?
Yes, and this is the important distinction.
A phone belonging to your partner, your brother or your flatmate, used by that person with their own Google account, is a legitimate tester. Google explicitly suggests recruiting from friends and family. There is no rule against people you know.
The line is not who they are, it is whether they are real and whether they actually use the app. A family member who genuinely opens it across the two weeks counts fully. A family member’s phone that you set up yourself and never touch again is closer to the fake account problem than to real testing.
What is Google actually looking for?
It helps to stop thinking about the number and start thinking about the record.
At the end of your test, Google is looking at whether twelve or more separate people spent two weeks using your app. Twelve opt-ins with almost no sessions behind them fails that test even when the count is technically correct, which is why applications get denied for insufficient testing engagement despite hitting the number.
Your own account, however you add it, contributes one person’s worth of that record, and it is the one person whose opinion of the app was never in question.
Frequently asked questions
Does Google explicitly ban the developer from being a tester?
Google’s published requirement does not name the developer either way. It specifies 12 testers opted in for 14 continuous days. The practical point is that one account does not meaningfully change your position.
Can I use two Google accounts on the same phone?
Technically a device can hold several accounts. Doing it to inflate your tester count is the pattern that risks the account, so it is not worth it.
Do testers need their own separate devices?
In practice yes, because you need distinct people, and distinct people have their own phones.
Can my second phone count as a second tester?
A second device with a second account is still you. It is one person’s usage recorded twice.
Will Google actually notice?
The enforcement numbers suggest so. Google blocked 1.75 million policy-violating apps and banned over 80,000 developer accounts in 2025.
What if I genuinely only need one more tester?
Then ask one more real person. If you are at eleven, one message in a developer community usually closes the gap faster than any workaround.
The safe way to close the gap
Every risky idea in this post comes from the same place: trying to manufacture testers instead of finding them. Fake accounts, emulators and second phones are all attempts to make the number go up without twelve real people existing.
The safe version is simply the opposite. Twelve genuine Google accounts, on twelve real devices, belonging to twelve actual people who use your app. That is what the requirement asks for, and nothing about it puts your developer account at risk.
The practical problem is that most solo developers do not have twelve such people available, which we cover in what to do when you do not know 12 people with Android phones. There are two safe ways to get them.
Option 1: verified testers assigned to you
This is the safe bet if you want the gap closed without any judgement calls about what is and is not allowed.
- Real people on real Android devices, each with their own Google account. Nothing that resembles the pattern Google’s enforcement systems look for.
- Assigned within 6 hours, so your 14 days start today rather than after weeks of asking.
- They stay active for the full period, which is what the engagement check actually measures.
- Anyone who goes inactive is replaced, so a quiet week never becomes a denied application.
- A feedback report at the end, plus pre-filled answers for the 10 production access questions.
- 100% production access or your money back.
Starter, ₹999 gives you 15 testers for the full 14 days. Pro, ₹1,699 gives you 25, plus a detailed ASO report and priority support. More than 10,000 apps have reached production this way, from a community of over 50,000 developers. Submit your app to start.
Option 2: join a free Pack of 16
Equally safe, and free. The Testers Community app pairs you into a Pack of 16 developers who test each other’s apps for 16 days. Every member is a real developer with a real device and a real reason to keep testing, because they need production access for their own app. Members who stop testing are replaced.
The cost is your time: you are testing fifteen other apps while yours is being tested.
Whichever route you take, read the full closed testing requirements before your 14 days begin.
