How it works

From submission to final report

A campaign runs for at least 14 days of testing, plus time for review, payment and tester onboarding. Each step below shows who is responsible.

YouProject Play XTesters
  1. 1

    Create an account and submit your app

    You

    Give us your app name, Android package ID, Play testing link and clear testing instructions. You can save a draft and submit when ready.

  2. 2

    We review the submission

    Project Play X

    An administrator checks that the app is installable from a closed track and that the instructions are clear. We may ask for changes or decline.

  3. 3

    Pay for the campaign

    You

    Once approved, you pay ₹499. The campaign only moves forward after the payment is confirmed, not by a redirect.

  4. 4

    Your app is listed for testers

    Project Play X

    We create a Google Group for your campaign and list your app in our invitation-only tester catalogue. You add the group to your closed testing track in Play Console.

  5. 5

    Testers choose your app and opt in

    Testers

    Invited testers pick apps they will genuinely use, then join your test group with one click. They opt in on Google Play and submit evidence, which an administrator reviews.

  6. 6

    The 14-day testing period starts

    Project Play X

    Once enough testers have verified opt-ins, the qualifying period begins. Each tester has their own timeline.

  7. 7

    Testers use the app and report

    Testers

    Testers submit scheduled check-ins describing what they tested, plus feedback and bug reports with device details.

  8. 8

    We monitor and replace when needed

    Project Play X

    We follow up on missed check-ins. When a tester withdraws, their slot reopens in the catalogue for a replacement. Every change is recorded in the campaign history.

  9. 9

    You receive the results

    You

    A private report with participation, feedback, bugs, recommendations and a clear completion assessment, including anything that fell short.

How we label participation

You always know where a fact came from

We can't read Google Play's opt-in data automatically. Instead, every participation record carries one of these labels.

Self-reported

The tester told us they did something, such as joining the test. Not checked by us.

Evidence submitted

The tester sent evidence, such as a screenshot of the opt-in page. Awaiting review.

Admin-verified

A Project Play X administrator reviewed the evidence and recorded the result.

Platform record

Stored facts such as timestamps of check-ins, feedback and bug reports.

Continuous participation

Why we recruit 14 for a requirement of 12

Where the closed-testing requirement applies, at least 12 testers must stay opted in for 14 days in a row. We recruit 14 so one or two drop-outs don't end the campaign.

Tester A · continuousQualifies
Tester B · left on day 5, rejoinedClock restarts

Two separate periods are never added together. Tester B's new period starts on day 6.

Replacement tester · joined day 4Own timeline

A replacement starts a fresh 14-day period from their own opt-in date.

Ready to set up your campaign?