Independent testing marketplaceAndroid · iOS · Web
Ship it after strangers have tried to break it.
Built for vibe coders shipping Android, iOS, or web apps and looking for beta testers. Post a testing ticket — testers who already own the devices file severity-graded findings. Their pay stays held until you accept the report.
Exact cost shown before you pay · No seats · No retainers
- ✓Pay is held, not taken. Tester shares release only on accept.
- ✓Fixed by time. Smoke ≈15 min, feature ≈30 min, full pass 1 hr+.
- ✓Mutual 1–5 ratings. Stored on both profiles, forever.
- ✓Real devices only. Ranked by hardware overlap.
01How a ticket runs
Five steps, each with a paper trail.
Nothing happens off the record. Every state change — match, payment, finding, accept, rating — is stored on the ticket and visible to both sides.
- 01
Post the ticket
Name the build, platform, target devices, category, and testing depth — smoke, functional, exploratory, or regression. State how many testers you need, from 1 to 25.
- 02
Read the ranked bench
Every eligible tester is scored 0–100 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 up to N testers and pay per slot through Stripe Checkout. The exact total is shown before you confirm — testers earn the full tier price, and each share is earmarked and held. No charge, no match.
- 04
Get findings
Contact details unlock immediately — email and WhatsApp. Share the build, and testers file a summary, individually severity-graded issues (critical / major / minor / cosmetic), reproduction steps, and a verdict: pass, fail, or pass with issues.
- 05
Accept or revise
Accept the report and that tester's held share releases, the test lands on both profiles, and you rate each other 1–5. Not good enough? Request a revision with a note instead — the money stays held.
02The ranking, published
Our matching formula, in full. No black box.
This is the actual scoring from the production ranker, weights included. If a tester outranks another, you can see exactly why — and challenge it.
| Signal | Weight | Rule |
|---|---|---|
| Covers your platform | +30 | Tester owns a device (or lists a platform) matching the ticket. |
| Owns the exact device | +10 each, max +25 | Exact match against the shared device list. |
| Knows the category | +20 | Tester has shipped or tested in your app category before. |
| Experience fits the depth | +15 · near-fit +8 | Senior ≥ exploratory; mid ≥ functional. Smoke is open to all. |
| Rating record | +2 per star | A 4.8★ tester carries +10. Unrated testers simply get +0 — no penalty. |
| Completed tests | +1 each, max +10 | A slow trust bonus for testers with accepted history. |
Capped at 100 · Incomplete & over-capacity testers excluded before scoring
03When it goes wrong
The failure cases, answered upfront.
Most marketplaces hide these pages. We'd 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 1–5 rating with an optional comment, stored permanently on both profiles. Developers with low scores attract fewer senior testers — the incentive runs in both directions.
G.3
No-show protection
A tester who never files leaves no accepted test, earns nothing, and carries the gap on their record. You only ever pay for the slot; the 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 — the full history stays on the ticket.
04Questions
Asked before the first ticket.
No hiring, no contracts, no device lab. You describe the build once, get ranked testers who already own the devices, and pay per slot. Communication happens over email or WhatsApp; the record — matches, payment, findings, ratings — stays on the ticket.
Through Stripe Checkout when you confirm testers. Testers earn the full tier price for the depth — smoke is a ≈15-minute pass, functional ≈30 minutes, exploratory and regression run 1 hr+ — and a platform fee applies on the developer side. The exact total is shown before you confirm anything. Each tester's share is held and releases only when you accept that tester's report.
Request a revision with a written note — the tester's share stays held until the rework lands. Only your accept action releases money. Every completed test also ends in a mutual 1–5 rating on both profiles.
Testers list devices, OS versions, categories, and experience, then get picked from ranked suggestions. They earn the full tier price per accepted report depending on depth — smoke, functional, exploratory, or regression — with no fee taken from their share, and the exact amount is shown on the assignment before they start. Every rating compounds into higher future ranking.
Continue with Google on the sign-in page. After you authenticate, a short onboarding asks whether you’re a developer or a tester and collects the profile details matching needs.