A friend of mine has two apps on the Play Store.
The first is Motion Cues — an app that prevents motion sickness by syncing visual cues with your inner ear. Over 30,000 downloads.
The second is Let it Rain — a rain overlay app for relaxation and focus. Climbing toward 10,000.
Each took about a month to code.
Each took three months to publish.
This is the story of how those six months were spent, and why it turned into a product idea.
Google Play's "Innocent" Rule
On November 13, 2023, Google Play added a requirement for new personal developer accounts: before your app can go to production, 12 testers must opt into your closed testing track and remain active for 14 consecutive days.
My friend's account was created after that date. When we first read the rule, both of us thought the same thing: easy.
12 people. 14 days. How hard could it be?
Very hard. As it turned out.
Motion Cues — The First Wave
My friend started writing Motion Cues in early 2025. The code took two months. Play Console listing, screenshots, description — one week.
Then came the publishing process.
The first thing he saw: "New personal developer accounts must complete closed testing with 12 testers for 14 consecutive days before production access."
He laughed. "Okay, I'll find 12 people. Done."
"Just Ask Your WhatsApp Group"
We live in Istanbul. Our circle is full of developers.
Developer friends group (~40 people):
- Android users: 3
- Willing to help: 3
- Actually opened the app daily for 14 days: 1
40 developers. All on iPhone. It's 2026, and that's the irony — developers who build mobile apps are the least likely to actually use the OS their users are on.
He turned to family. Explaining "open this every day for two weeks" to his mother. Asking her every morning: "Mom, did you open it today?" For 14 days.
End of week one: 5 active testers. 7 short.
He Turned to Fiverr
You've probably seen the gigs: "12 Testers for Google Play — $15." He paid.
Two days later, 12 Gmail addresses arrived. Two opted in. None opened the app.
The seller was really selling email delivery, not testing. Whether those emails corresponded to real people who used your app daily was not their problem.
Reddit Swap Threads
He ended up in r/androiddev's closed testing swap threads. The math is brutal: you need to test 12 apps, each for 14 days. Opening 12 strangers' apps every single day for two weeks. Just to launch your own.
By week three, still bouncing between 10–11 active testers. Never hit 12 continuously.
Three Months Later
- Coding: 2 months
- Launch preparation: 1 week
- Finding 12 testers: 3 months
Motion Cues is now on the Play Store with 30k+ downloads. But those three months stayed with him.
Let it Rain — The Pattern Repeats
A few months later, second app. Code: three weeks.
But the publishing process started from scratch. 12 testers. 14 days. Again.
"Bro, if I could just move Motion Cues testers to Let it Rain, I'd be saved. But Google wants fresh testing for every new app."
Every new app = 12 testers from zero.
Time to production: 2.5 months.
This Is Where It Clicked
"This isn't a bug," I said. "This is a system."
On Reddit, Twitter, LinkedIn, every day, hundreds of developers in the same hole:
- "Who needs testers? DM me for swap"
- "Lost $50 on Fiverr tester scam"
- "Launch delayed 6 weeks, still stuck on closed testing"
- "Google why is this so hard"
Every single one hitting the same wall.
The Vibe Coding Era Made Shipping Harder Than Building
Something shifted in 2025–2026: writing code became accessible to everyone. Claude Code, Cursor, Bolt, Replit. Working apps built over a weekend. Non-developers shipping mobile apps.
Building a mobile app now takes days. Publishing one still takes months.
So We Made a Service
Existing solutions weren't built for this:
- Fiverr freelancers: Sell email delivery, not engagement
- Reddit swap threads: Force you into 14 days of testing strangers' apps
- Enterprise testing services: $200+ price tag, overkill for indies
There was a gap. Real Android devices, real user behavior, 14-day continuous engagement, transparent dashboard, indie-friendly pricing.
That's where onTest came in.
Been through something similar? I'd love to hear your story in the comments. Good luck with your launch — you'll get there.