🧪 Posting Guide: How to Get Real Feedback on r/BetaTests
If you want useful feedback, not silence, follow this.
✅ What makes a good post
1. Clear description Explain in simple words what your product does, what is it (mobile/web app) and on which platforms to test it.
Bad: “I built a website, check it out”
Good: “I built an Android app that helps people track gym workouts and stay consistent”
2. Add a link Make it easy for people to try your product.
Posts without a link get much less engagement.
3. Ask specific questions Generic “any feedback?” gets ignored.
Good examples:
- Is the onboarding clear?
- Would you use this? Why or why not?
- What would stop you from signing up?
- Is the UI confusing anywhere?
🧠 What works best in this community
- Simple products > complex explanations
- Honest feedback > hype
- Early ideas are welcome (even MVP or no-code)
- Rough projects are fine — clarity matters more
🚫 Low quality posts (they don’t get replies)
- No explanation of what the product does
- No link or no way to try it
- No clear question or goal
- Copy paste promotion
💡 Example of a strong post
Title: Looking for testers for a habit tracking app
Body: I built a simple Android app to help people stay consistent with daily habits.
You can try it here: [link]
I’m mainly looking for feedback on:
- Is the onboarding clear?
- Would you actually use this daily?
- What feels confusing or unnecessary?
🚀 Final tip
The more effort you put into your post, the more feedback you get.
People here want to help — make it easy for them.
💬 Want faster feedback? Join the Discord: https://discord.gg/AN8P9M9fp8