A hand ticking off a project checklist in a notebook.

Photo by Jakub Żerdzicki on Unsplash

← All articles

BTesting

Free app feedback, seven ways, compared honestly.

Every maker tries the same free channels for feedback, in roughly the same order, and gets roughly the same disappointing results from most of them. They aren't useless; they're good at different things. Here is what each one gives you, so you can stop expecting a test from a place built for conversation.

By Maxime Bertonnier · Published

1. Reddit

Subreddits like r/SideProject, r/alphaandbetausers or your niche's own community can send real people, and sometimes sharp criticism. Most posts get a few upvotes and comments about the landing page. Self-promotion rules vary per subreddit and are enforced. Good for first impressions of your pitch, rarely for a test of the product.

2. Discord and Slack communities

Feedback channels in maker communities are friendly and fast, and messages scroll away in an hour. You get reactions, not reports. Good once you're a known member, poor as a cold drop.

3. Indie Hackers and maker forums

Longer, more thoughtful replies, from people who've been there. Better for advice on positioning, pricing and growth than for someone to click through your sign-up.

4. Friends and family

They'll actually open it, which is more than most channels. They'll also be kind, and they're often not your audience. Good for spotting a crash; useless for knowing whether anyone would pay.

5. Your own waitlist or audience

The best free feedback there is, because these are the people you're building for. The catch is that you need the audience first, and you only get to surprise them once.

6. Launch platforms

Product Hunt and similar platforms bring a burst of visitors and public comments. Treat them as a launch, not as a test: the comments are visible to everyone.

7. Testing exchanges

You test other makers' products, they test yours, and the output is a written report. It's the one free channel built for testing. The testers are makers rather than your target users, so pair it with your waitlist for audience questions. Makers Wall is one; I built it, so weigh my opinion accordingly.

Which to use, when

  1. 1Pitch unclear? Reddit and maker forums, with the landing page only.
  2. 2Product built, never seen by a stranger? A testing exchange.
  3. 3Fixed the obvious problems? Your waitlist or a handful of target users.
  4. 4Ready to be seen? Launch platforms.

How it works on the wall

  1. 1 · SubmitPaste your link and write what testers should look at.
  2. 2 · TestClaim someone else's project and write down what broke. That earns the credits that unlock your own reports.
  3. 3 · ReceiveMakers test yours and send a report, every problem listed with its severity.
  4. 4 · RateYou rate each other; both ratings unlock together.

Free, and based on reciprocity. The FAQ has every rule written out.

Questions

What is the best free way to get feedback on my app?
For testing the product itself, a testing exchange, where other makers use it and write a report. For questions only your audience can answer, your own waitlist or users.
Why does nobody reply to my feedback posts on Reddit?
A post asks strangers for time and gives nothing back. Comment generously in the community first, ask one specific question, and keep the link to the landing page.
Is AI feedback on my app useful?
For copy and code review, it can help. It hasn't used your app on a phone at the end of a long day, and it tends to agree with how you framed the question, so it doesn't replace a person.

Put yours on the wall.

Submit your project for free, test someone else’s, and get an honest report back.

Get your first testers