For developersAndroid · iOS · Web
Ship it after strangers have tried to break it.
Post a testing ticket for your build. Testers who already own the devices file severity-graded findings. Their share stays held until you accept the report.
Ranked bench · Held shares · Accept to release
- ✓Held, not taken. Shares release only on accept.
- ✓Fixed by time. Smoke, feature, and full-pass depths.
- ✓Mutual ratings. Stored on both profiles.
- ✓Real devices only. Ranked by hardware overlap.
01For developers · How a ticket runs
Five steps, each with a paper trail.
Nothing happens off the record. Every state change — match, funding, finding, accept, rating — is stored on the ticket and visible to both sides.
- 01
Describe the build
Name the build, platform, target devices, category, and depth — smoke, functional, exploratory, or regression. State how many testers you need, from one up to twenty-five.
- 02
Read the ranked bench
Every eligible tester is scored with the reasons printed next to the score: which devices they own, category overlap, experience fit, rating. Testers already at capacity are excluded before you ever see them.
- 03
Confirm and fund
Select testers and check out. The exact total is shown before you confirm, and each tester's share is earmarked and held. No charge, no match.
- 04
Share the build, get findings
Contact details unlock immediately. Testers file a summary, individually severity-graded issues with reproduction steps, and a verdict: pass, fail, or pass with issues.
- 05
Accept or ask for more
Accept the report and that tester's held share releases; you rate each other and the test lands on both profiles. Not good enough? Request a revision with a note — the share stays held.
02The report
What lands in your inbox.
Every report follows the same structure, so a first ticket reads like a tenth. Severity is assigned per issue, not per report.
R.1
Summary
What was tested, on which build and devices, in the tester's own words.
R.2
Issues, graded
Each issue carries one severity — critical, major, minor, or cosmetic — with steps to reproduce.
R.3
Verdict
A closing call on the build: pass, fail, or pass with issues.
R.4
Thread
Revisions, notes, and your accept decision stay on the ticket, visible to both sides.
03When it goes wrong
The failure cases, answered upfront.
Most marketplaces hide these pages. We would rather you read them before your first ticket than discover them after.
G.1
Revisions before acceptance
If findings are thin, request a revision with a written note. The tester's share stays held until the rework lands. Accepting is the only action that moves money.
G.2
Ratings cut both ways
Every completed test ends in a mutual rating with an optional comment, stored on both profiles. Low-scored developers attract fewer senior testers — the incentive runs in both directions.
G.3
No-show protection
A tester who never files leaves no accepted test and earns nothing. A share releases solely on your accept.
G.4
Cancel states are explicit
Tickets carry open, matched, in-progress, completed, and cancelled states. Nothing silently disappears.
Get started · Developer
One account. Post tonight.
Create an account with Google, pick Developer once, and describe your build. The bench is ranked the moment your ticket is live.
- ✓Exact total before you confirm. Nothing moves until you approve it.
- ✓Contact unlocks on match. Email and WhatsApp, straight to the tester.
- ✓History stays on the ticket. Matches, findings, revisions, ratings.
- ✓Real devices only. Ranked by hardware overlap.
Continues on the full login page · Free to join · No card required
Testing instead? See the tester page.
05Questions
Asked before the first ticket.
- How is this different from hiring QA?
- No hiring, no contracts, no device lab. You describe the build once, get ranked testers who already own the devices, and fund per slot. Communication happens over email or WhatsApp; the record — matches, funding, findings, ratings — stays on the ticket.
- When does money move?
- When you confirm testers, each share is earmarked and held. It releases to a tester only when you accept that tester's report. The exact total is shown before you confirm anything.
- What if a report is bad?
- Request a revision with a written note — the tester's share stays held until the rework lands. Only your accept releases it. Every completed test also ends in a mutual rating on both profiles.
- How do I create an account?
- Continue with Google on this page (or /login). After you authenticate, onboarding asks you to choose developer, then collect contact and platform details so matching can start.