A first look at TestPogo · Payments and requests are not open yet.

Google Play closed testing

Your app is ready. Find the people to test it.

You built the app. Let’s take the next step together: real Android testers, useful feedback, and a coordinated closed test.

15 testers·14 days·$10 one time

Proposed launch offer. No payments or reservations yet.

Target onboarding within 6 hours after payment is verified and you supply a ready-to-test app with valid access details.

Real Android testers One-time campaign Your account stays yours Feedback you can act on

A clear next step

Less chasing.
More learning.

The proposed campaign keeps coordination off your list, so you can focus on making your app better.

01

Share your test

Supply a ready build, your opt-in link and the tasks you want people to try.

02

Meet your cohort

We plan to recruit 15 Android testers and help them join your closed test.

03

Test and improve

A 14-day campaign with participation checks, feedback and time for your fixes.

04

Take the next step

Review your feedback summary, check eligibility, then apply in your own Play Console.

When does it start? Target onboarding within 6 hours after payment is verified and you supply a ready-to-test app with valid access details. The target covers onboarding, not the entire test or Google’s review.

Useful feedback, not just a headcount

Know what happened.
Know what to fix.

“It doesn’t work” is a starting point. A clear report shows the task, the steps, and the difference between what someone expected and what happened.

  • A task to tryYour app’s real user journey.
  • A problem to understandReproduction steps and impact.
  • A change to checkYou fix it. Testers try again.
Use the feedback checklist ↗
Sample feedback reportFictional example

Saved item disappears after reopening

Task blockedSaved items
Steps to reproduce
Save an item. Close the app. Reopen the saved-items screen.
Expected
The saved item is still in the list.
Observed
The list is empty after reopening.
Suggested follow-up
Check saved state, then repeat the task on the next build.
Sample only. Not a customer result or a telemetry feed.

Your app. Your account.

Clear roles.
No shared passwords.

A testing service helps coordinate people. You keep control of your app, your fixes and your application.

The proposed TestPogo role

Recruit the cohort, coordinate genuine testing, check participation and bring feedback together. Replacement and extension terms must be agreed before sales.

Your role as the developer

Provide working access, choose meaningful tasks, resolve issues and apply for production access yourself. Arrange limited test accounts securely when needed.

Google’s role

Assess your production-access application. Meeting the testing threshold does not guarantee approval or publication on a particular date.

Read the closed testing requirements ↗

Small price. Defined scope.

One app.
A thoughtful test.

No tiers to decode. Review exactly what is proposed before requests open.

One app campaign
$10USD
one time

No subscription. A defined testing campaign.

Explore the testing plan

Proposed launch plan. Payments are disabled.

A little coordination goes a long way.

  • 15 real Android testers
  • 14-day testing and feedback campaign
  • Daily participation checks
  • Final feedback summary
  • Replacement and extension support, with limits to be confirmed
  • No Google password or administrator access

Target onboarding within 6 hours after payment is verified and you supply a ready-to-test app with valid access details.

Read the draft service-delivery terms ↗
Tax treatment will be confirmed before orders open.See the full plan and limits ↗

Before you take the hop

A few good
questions.

Google’s policy checked on 2026-09-18.

Read Google’s official guidance ↗
Does this requirement apply to every developer?

This requirement applies to personal developer accounts created after November 13, 2023. Check your own Play Console for the requirements that apply to your account and app.

When would my campaign start?

Target onboarding within 6 hours after payment is verified and you supply a ready-to-test app with valid access details. This is an onboarding target, not the duration of testing or Google’s review.

Why plan for 15 testers if Google requires 12?

The proposed cohort of 15 gives you a buffer above the minimum of 12. It does not remove the need for each qualifying tester’s continuous opt-in history.

Does a replacement inherit the previous tester’s days?

No. A replacement has their own opt-in history, so replacing a tester can extend the time before you qualify.

Are daily opens a published numerical requirement?

Google’s cited guide does not prescribe a daily-open count. It asks about engagement and feedback; TestPogo’s proposed daily participation checks are a separate service commitment.

Do you need my Google password?

No. Keep your Google password and Play Console administrator access private. If your app needs login access, a limited test account can be arranged securely later.

What happens if Google asks for more testing?

Review Google’s explanation, address the issues and continue testing as needed. Extensions and replacements are part of the proposed service, but their limits must be confirmed before orders open.

Can I pay or reserve a campaign now?

No. Payments and testing requests are closed in this preview. You can review the plan and try the app-details flow without sending anything.

Can I test another app or repeat a campaign?

The proposed price covers one app and one campaign. Another app or campaign would need a separate order after sales open.

What is the refund policy?

Refund terms are under owner review and no money is being collected. Read the draft refund policy before any future purchase.

A little guidance helps

Make your next move
an informed one.

All guides and tools ↗

From built to better

Give your app a thoughtful first audience.

Start with the plan. Keep your account and your decisions in your hands.

Explore the testing plan
One app · Proposed $10Explore the plan ↗