For testersAndroid · iOS · Web
Test real builds on the devices you already own.
List your hardware once. Get matched to builds that need it, file severity-graded findings, and get rated. Your share stays held until the developer accepts your report.
Real hardware · Graded findings · Held shares
- ✓Ranked by overlap. Hardware you own decides fit.
- ✓Held, not promised. Shares release on accept.
- ✓Revisions are written. Every request carries a note.
- ✓Ratings compound. Every accept builds your rank.
01For testers · How testing works
Five steps, each with a paper trail.
Nothing happens off the record. Every state change — match, assignment, finding, accept, rating — is stored on the ticket and visible to both sides.
- 01
List what you own
Devices, OS versions, platforms, categories you know, and experience. Matching is scored against this list, so keep it accurate — it is the whole basis of your ranking.
- 02
Get picked from the bench
Developers see a ranked bench with the reasons next to each score: hardware overlap, category fit, experience, rating. Testers already at capacity are excluded before scoring starts.
- 03
Receive the build
Contact details unlock on match — email and WhatsApp. The developer shares the build directly, and the assignment states the depth and what the report must contain.
- 04
File findings
Write a summary, log each issue with its own severity — critical, major, minor, or cosmetic — with reproduction steps, and close with a verdict: pass, fail, or pass with issues.
- 05
Acceptance releases your share
The developer accepts your report or requests a revision with a written note. On accept, your held share releases, the test lands on both profiles, and you rate each other.
02The report
What an accepted report looks like.
Every report follows the same structure, so developers can compare testers fairly. Severity is assigned per issue, not per report.
R.1
Summary
What you tested, on which build and device, in plain language. A developer who was not in the room should be able to follow it.
R.2
Issues, graded
One severity per issue — critical, major, minor, cosmetic — each with steps to reproduce. Thin reports come back as revisions.
R.3
Verdict
Your closing call on the build: pass, fail, or pass with issues. Own it.
R.4
Revision notes
If a revision is requested, the note tells you exactly what was missing. Answer it directly and resubmit.
03Fair ranking
How the marketplace treats testers.
The ranking is published, not hidden. If another tester outranks you, the reasons are printed next to the score — and you can see exactly what to improve.
F.1
Unrated means zero, not negative
New testers start with no rating bonus and no penalty. Ratings compound only from completed, accepted tests.
F.2
Capacity is respected
Testers at capacity are excluded before scoring, so you are never ranked for work you cannot take.
F.3
Revisions are specific
A revision must carry a written note. Vague rejections have nowhere to hide — the thread stays on the ticket.
F.4
Ratings cut both ways
Developers are rated too, and low-scored developers attract fewer senior testers. The record is mutual and permanent.
Get started · Tester
One account. List your devices tonight.
Create an account with Google, pick Tester once, and tell us what you own. Matching starts the moment your profile is complete.
- ✓Amount shown before you start. Every assignment states its share upfront.
- ✓Direct contact with developers. Email and WhatsApp on every match.
- ✓History builds your rank. Accepted tests and ratings, stored permanently.
- ✓Real devices only. Matched on the hardware you list.
Continues on the full login page · Free to join · No card required
Shipping an app instead? See the developer page.
05Questions
Asked before the first test.
- What do I need to join as a tester?
- A Google account, real devices you can name precisely, and the ability to write clear reproduction steps. List your devices, OS versions, categories, and experience once — matching starts immediately.
- When do I get paid?
- Each assignment's share is earmarked and held when the developer confirms testers. It releases to you when the developer accepts your report. The exact amount is shown on the assignment before you start.
- What makes a report get accepted?
- A plain-language summary, every issue severity-graded with reproduction steps, and an honest verdict. Reports that restate the obvious without evidence come back as revisions with a written note.
- How do I create an account?
- Continue with Google on this page (or /login). After you authenticate, onboarding asks you to choose tester, then list devices, OS versions, categories, and experience.