AI Workflow 03 · Launch Operations · Declassified
Getting a new Android app through Google Play's 12-tester / 14-day closed test
Real people onlyNew personal developer accounts can't publish until the app passes a closed test. I ran it with real testers and agent-run routines. Production access came about 18 days after the test began.
ON THIS PAGE
01 Problem · 02 Setup · 03 Steps · 04 Tools
05 Results · 06 What you get · 07 Try it ▸ · 08 Talk
01 · The Problem
Twelve real testers, fourteen days straight
New personal Google Play developer accounts can't publish until the app passes a closed test: 12+ testers opted in continuously for 14 days. Then you apply for production and answer Google's questions.
My obstacles:
- Few Android contacts. Lots of my friends use iPhones.
- Testers who say "sure!" but never opt in.
- Noisy, fast-banning tester communities (Reddit, WhatsApp, Discord).
- Dozens of reciprocal swaps to track.
- Google watching for fake engagement.
02 · The Setup
Agents track and draft. People test.
Riley ran recruiting at first: Play Console checks, Group management, outreach drafts, and the reciprocal checklist. Pip took over the tracking routines on Sep 9. Ivy flagged Play Console and tester emails.
| Agent | Job | Ground rule |
|---|---|---|
| Riley (Organizer) | Recruiting, Group management, outreach drafts, reciprocal checklist | Drafts only; I post and send |
| Pip (QA) | Daily install tracker, reminders, cleanup (from Sep 9) | Tracks and reminds; never fakes an open |
| Ivy (Inbox) | Flags Play Console and tester emails | Read-only |
- Real people only. Automation tracked, reminded, and drafted, but never faked opens or installs. I played partner apps myself at a human pace.
- Human-sounding outreach. Every post, email, and DM got a "copy humanizer" pass.
- Only swap with apps that have both links: a Google Group link and a working Play opt-in link.
- The same Google account everywhere. Blank Play pages turned out to be account mismatches, not "Play lag."
03 · The Steps
How it runs, step by step
- Created the closed Alpha track tied to a Google Group. The track was available Sep 2, and the 14-day clock started about Sep 3.
- Built a tester checklist targeting 15–25 real opt-ins, not the bare 12, to cover dropouts.
- Warm outreach first: friends, family, and existing web players, with the website link in every message.
- Posted in tester-swap subreddits (r/AndroidClosedTesting, r/TestMyApp, r/TestersCommunity, r/AndroidAppTesters). The Group went from 1 to 13 members overnight.
- Joined reciprocal-testing Groups, opted in, installed, then privately asked each owner to test back.
- An agent scanned Reddit (read-only) and WhatsApp communities for fresh English-language tests with both links, skipping foreign-language, non-US, Mac/Linux-only, and banking-type apps. On Sep 10 I joined 10 reciprocal Groups and contacted all 10 owners.
- A live swap tracker (
need_join → need_install → installed → done_14d, orremove_no_reply,unavailable_country_US,pending_play_lag) with a 5-day rule: no owner reply in 5 days meant uninstall and leave. - Automated routines: a daily 9am install tracker (opted in / installed / day X of 14 / Group size), Tue/Fri reminders, and a weekday 5-day cleanup.
- Sep 7: uploaded build 1.0.36 (target SDK 36) mid-test after an upload-key reset, and confirmed it didn't restart the clock.
- Gave real feedback to partner developers (a launch crash, a country block, missing US units, a dictation glitch). That built goodwill.
- Sep 19: all three Play Console checks green. Submitted the production-access form, thanked testers, and wound down reciprocal swaps fairly (26 partners contacted).
- Sep 21, 2026: production access granted.
- Aim for about 2× the required testers.
- Installs, not Group joins, are the real bottleneck.
- Pace outreach. Subreddits filter fast, and too many DMs can restrict an account.
- Check country availability and account matching before blaming "Play lag."
04 · Tools
- AI agents: organizer, QA / tracker, inbox
- Scheduled routines
- Grok
- Claude
- ChatGPT
- Google Play Console
- Google Groups
- Gmail
- Reddit, WhatsApp, Discord tester communities
- Firebase (web players invited)
- GitHub (markdown checklist as source of truth)
- Galaxy S24 Ultra
05 · Results
What changed
Google Group members (13 overnight · 24 Sep 5 · 30 Sep 6 · 35 Sep 12)
Installs (15 Sep 9 · 17 Sep 12 · 20 Sep 13)
Reciprocal apps tracked
From test start to production access
Production release date / first live installs
Hours saved
06 · What a Client Gets
If you hire me for this
- Closed track + Google Group setup and a tester tracker.
- A vetted list of reciprocal tests: English, available in your country, working links.
- Human-sounding outreach templates.
- Automated daily install tracking and reminders.
- A wind-down plan and help answering Google's production-access questions.
- No bots faking engagement. Ever.
07 · Try It · Interactive Workflow Example
14-day tracker
Drag through the test day by day, using the real logged numbers. Then try the what-if to see why I aim for 15–25 testers, not 12.
Show the logged numbers as a table
| Date | Group | Installs |
|---|---|---|
| Sep 2 | 1 | 0 |
| Early days (exact date not logged) | 13 (overnight after first subreddit posts) | not logged |
| Sep 5 | 24 | not logged |
| Sep 6 | 30 | not logged |
| Sep 9 | not logged | 15 |
| Sep 12 | 35 | 17 |
| Sep 13 | not logged | 20 |
On day 9 I had 15 logged installs. Losing 3 would leave exactly 12. With the bare minimum, the same dropouts would sink the test. That's why I aim for about 2× the requirement.
Want something like this for your business?
Bring one workflow that feels slower or more manual than it should. We'll look at it together on a free 15-minute fit call, and I'll give you an honest answer, even if that answer is "don't automate this."