Give a test, get a test: why I built TestSwap

You finish the first version of your app. You show it to a friend. "Looks great!" they say, and hand the phone back. You learn nothing.

You post the link somewhere public. A few people scroll past. Nobody clicks, or somebody clicks, bounces in four seconds and never tells you why. If you build things on your own, you know this loop. I've lived in it for years.

The problem: feedback is scarce

Friends and family are kind, and kindness is useless for a product. They won't tell you the signup form is confusing, because they don't want to hurt you. Strangers would tell you, but strangers have no reason to spend ten minutes on your half-finished app.

Meanwhile, every other indie developer you know is in the same spot. They also have an app nobody has really tested. They also would happily spend ten minutes on yours, if someone would spend ten minutes on theirs.

That's the whole idea behind TestSwap: give a test, get a test.

The idea: a 1-for-1 swap

TestSwap is a small site where indie developers test each other's apps. You review someone's app, you earn a credit. You spend that credit to have someone review yours. Web apps, iOS apps and Android apps are all welcome. It's free, there are no paid tiers, and no money changes hands.

You sign in with X (Twitter) and nothing else. No password to forget, no extra account to manage, and a real identity attached to every review.

How the credits work

• Every new account starts with 3 credits.
• When you write a review, you earn +1 credit. The maker of that app pays −1.
• An app only accepts reviews while its maker has a balance above 0. At 0, the maker's apps stop accepting reviews. Review someone else's app and they're back.
• You can't review your own app, and you can review a given app only once per version.
• When you ship something new, you can "bump version" and the people who reviewed the earlier version can test again.

The feed shows apps that are accepting reviews first, then the ones with the fewest reviews on their current version, then the newest. So the app that most needs eyes gets them first.

Each app has a test task: one concrete thing the maker wants testers to do, in 200 characters or fewer. It matters more than it sounds, and I wrote a whole post on it: how to write a test task that gets useful feedback.

Two rules I feel strongly about

1. A 👎 costs the reviewer

After a review comes in, the maker rates it 👍 or 👎. Once. The rating is final. A 👎 takes back the credit the reviewer earned. Balances are allowed to go negative, so a pile of bad reviews has a real cost. The maker does not get their credit refunded.

Why? Because a credit system without any consequence turns into "write one line, collect your credit." Reviews like "nice app!" would flood the site, and we'd be right back where we started. I'd rather the reviewer put in ten honest minutes. Making the maker's rating final keeps it simple, too: there's no haggling over it.

A review has two public parts (what the experience was like, and what to improve) plus an optional private field for bug notes that only the maker sees.

2. Sharing on X earns nothing

TestSwap has "share on X" buttons, because word of mouth is how a small site grows. But sharing earns no credits, on purpose. There are three reasons:

1. I can't verify a share. Anyone could claim one.
2. Free credits would break the 1-for-1 swap. Every credit should come from someone doing a test.
3. Paying credits for positive posts is incentivized endorsement. I don't want a feed full of people saying nice things because they were paid to.

If you share TestSwap, I hope it's because you thought it was useful.

What's missing on purpose

This is a weekend-sized product, and I'm keeping it that way for now. There's no money, no notifications, no search, no comments and no admin panel. I'd rather ship a small thing that works and find out what people actually want than guess at a big roadmap.

It's also brand new. It launched in October 2026, so I have no user numbers or success stories to show you. What I have is a clear rule set and a feed that starts out small. Early testers will shape it.

Come test something

If you're not sure where to start, test first. You get 3 credits anyway, but writing one review is the quickest way to see how the site works and what a good review feels like. Open the feed, pick an app that's accepting reviews, and do the task. Then post your own app and see what comes back.

If you're still deciding how to get testers for your app in general, I wrote a plain guide to the free options. TestSwap is only one of them.

Thanks for reading. Tell me what's broken, what's missing and what you'd change.

Marc (@dizid on X)