Help

help · credits

Credits

The currency of the swap. You earn them by testing and spend them to get your own apps tested. Why it matters: Without it everyone would post and nobody would test. Example: A Full test approved: +1. Three Quick tests: +1. Posting a test: −1.

help · testTypes

The three test types

Full (14 days, daily check-ins), Quick (5–10 minutes and a public review) and Website (recorded and verified). Why it matters: Help in five minutes, or go deep for 14 days: both count. Example: An Android builder needs a Full test; an iOS builder often wants Quick reviews.

help · twelveTesters

Google Play’s 12 testers

New personal Google Play accounts must run a closed test with at least 12 opted-in testers for 14 days in a row before going to production. Why it matters: Most tests fail because testers drop out. Streaks and reminders keep them in. Example: Ask for 15 testers: if 2 drop, you still have 13.

help · proof

Proof of testing

Screenshots from inside the app and a short checklist; optionally a screen recording. Why it matters: Builders care about real use, not installs. Example: Two screenshots: the expense you added and the monthly summary.

help · challenge

The challenge word

A random pair of words shown when you start. Type it in the app or say it while recording. Why it matters: It proves the recording is yours and new, not borrowed. Example: amber-otter typed in the app’s search bar.

help · streak

Streaks and check-ins

A Full test lasts 14 days. Open the app and check in once a day; up to two missed days are fine. Why it matters: Google needs testers opted in for the whole 14 days. Example: Day 7 of 14: seven squares filled.

help · trusted

Trusted tester

Earned with 5 approved recorded tests, at least 80 % of Full tests finished and no flags. Why it matters: Builders can ask for Trusted testers first; it’s earned by work, not by ID. Example: Paid Guaranteed tests are filled with Trusted testers.

help · recorded

Recorded proof

A 30–90 second screen recording with your challenge word. Why it matters: Recorded tests show first to the builder and raise your trust more. No extra credits. Example: Record yourself adding an expense and saying the word.

help · snippet

The website snippet

One line of code on your site. It only wakes up for visitors arriving through a tswap test link. Why it matters: Proof comes from your own site, so it’s very hard to fake. Example: Mark the end of the task with data-complete-path="/welcome".

help · guaranteed

Guaranteed testers

15–20 Trusted testers for the full 14 days, with replacements if someone drops. Paid. Why it matters: For builders who need the 12 for sure, now. Example: Order it on your app’s page; tswap places the testers.

help · featured

Featured and Boost

Featured pins your test to the top of the feed, labelled. Boost notifies more testers. Why it matters: Money buys visibility, never better reviews. Example: Earned free with 3 referrals, or as a top tester.

help · apiKeys

API keys and MCP

Personal keys for the REST API and the MCP server, scoped and revocable. Why it matters: Post a new build from CI or from your AI assistant. Example: “Post my new build and tell me how many spots are left.”

help · shareCards

Share cards

A card for each moment of a test that X shows with your link. Why it matters: Tagged testers repost, so each post reaches many audiences. Example: “Passed! Tested by @a @b @c…”

help · referrals

Referrals

Your link carries your handle. When someone joins through it and finishes a first test, you earn 1 credit. Why it matters: Builders bring builders; never for likes or follows. Example: 3 referrals: a free 48-hour Featured spot.