The annoying part
Why Android app testing gets annoying.
Publishing an Android app is not just uploading an APK or AAB and calling it done. Google Play may require closed testing before production access, and finding real testers can become one of the slowest parts of the work.
I have run into the normal developer problems here. Friends and family may use iPhone. People say yes, then forget to opt in. Someone installs the app, never opens it, or uninstalls before you are ready. A few testers may be helpful, while others give no feedback at all.
That does not mean the testing step is pointless. It means you need a cleaner way to manage it. When you are also fixing bugs, writing store copy, checking privacy policy details, and getting Play Console set up correctly, chasing testers by hand gets old fast.
Google Play
What Google is looking for.
Google's official Play Console help says developers with personal accounts created after November 13, 2023 need to meet specific testing requirements before they can make new apps available on Google Play.
The careful version is this: Google says some new personal developer accounts need to run a closed test with at least 12 opted-in testers for 14 days before applying for production access. That does not mean all developer accounts are in the same situation, and it does not mean production access is automatic after testing.
Google also tells developers to give testers clear instructions and a feedback channel, such as email, a website, or a message forum. That part matters. If all you have is a list of email addresses and no real plan, the test can look busy without giving you much useful information.