Google Play Closed Test를 위한 12명의 실제 테스터 모집 (구매하지 않고)

• Buying testers fails three ways: Play’s fraud detection flags dormant accounts, bought testers never open the app (so engagement doesn’t count), and you’re dependent on a third party to satisfy a store requirement.
• Three source pools that work: your existing audience (highest quality), community trades on r/androiddev and r/indiedev (fastest), and your personal network (last resort).
• A warm-list invite converts 40–50%. Anonymous forums convert 5–10% — which is why you need multiple pools.
• Play watches for meaningful engagement, not just opt-ins. Four touches over 14 days keeps testers active.

You need 12 opted-in testers for 14 days before Google Play will let you ship. Buying them looks like the shortcut.

It usually isn’t. Play’s ML is good at spotting bought accounts, and it will silently reset your 14-day counter.

Here’s how to recruit 12 real humans in 3–4 days instead.

Why paid services fail

The tester-service business exists, and some of it works. Most of it has three failure modes:

1. Play’s fraud detection flags dormant or newly created accounts. Your test “has 12 testers” but Play doesn’t count them.
2. The testers opt in and never open the app. The engagement signal doesn’t register.
3. You’re now dependent on a third party to satisfy a store requirement. If they turn shady, your launch is stuck.

And even when it works, you’ve spent $50–200 on 12 accounts that will never use your app again. You had to do the harder work anyway — you just paid extra for the privilege.

The three source pools

1. Your existing audience (highest quality)

Newsletter subscribers, followers, Discord or Slack members. Even 200 subscribers converts to 10–15 testers with a good ask.

If you don’t have this: start building one on day one of your next project. This requirement is a recurring tax, not a one-off.

2. Community trades (fastest)

• r/androiddev — weekly beta-swap threads
• r/indiedev — weekly “test my app” threads
• Indie Hackers — milestones section
• Discord communities in your product’s category (game dev, productivity, etc.)

The trade is simple: “I’ll test your app, you test mine.” Both parties get closer to their 12, and communities enforce reciprocity so quality stays high.

3. Personal network plus amplification (last resort)

Friends, colleagues, family — then their networks via a “know anyone with an Android who’d help?” broadcast. This usually gets you the last three or four you need.

The invite template

Subject: Would you spend 5 minutes to help me launch my app?

Hey [name],

I’m launching [app name] on Android next month. Google now requires 12 testers for 14 days before I can ship publicly.

If you have an Android phone and 5 minutes, you’d be helping me a lot by:

1. Clicking this link: [tester opt-in URL]
2. Installing when the app appears in your Play Store
3. Opening it a couple of times over the next 2 weeks

That’s the whole ask. You’ll get free access to the paid version as a thank you.

[your name]

This converts 40–50% on a warm list. Anonymous forums convert 5–10% — which is exactly why you need more than one pool.

Keeping them engaged for 14 days

Play watches for meaningful engagement. If your 12 testers opt in and never open the app, the requirement isn’t satisfied.

• Day 1: Welcome message with “here’s what to try” (two or three specific flows).
• Day 5: A genuine “what’s confusing so far?” ask. This gets you feedback and another session.
• Day 10: Preview of what’s shipping in the next update. Another reason to open.
• Day 14: Thank you, plus “the app goes to production tomorrow.”

Four touches, each with real value. Not spam.

Turning testers into first users

Your 12 testers just spent 14 days with your app. That’s the highest-quality feedback pool you will ever have. Before the closed test ends:

• Send a proper survey. Not “rate 1–5.” Ask: “What almost stopped you from using this?” and “What would you tell a friend it does?”
• Ask for a testimonial, with permission to quote.
• Ask whether they’d upgrade to paid at launch. Their answer is your first real customer signal.

The reframe

You started this hunting 12 accounts to satisfy Google. You finish with 12 engaged real users, genuine feedback, a few testimonials, and possibly your first paying customers.

The Play requirement is annoying. The discipline it forces is actually a launch playbook.

If you’re stuck at “have the app, need the testers,” letsdeploy.it handles the release side so you can focus on recruiting. The 12 humans still have to come from you.

How did you find your 12? I’m curious which pool actually worked — the swap threads or the personal network.