VibeCodingList
Ask one clear question. Get targeted product feedback.
VibeCodingList is the builder network and feedback marketplace for AI-built and vibe-coded products. Builders submit live apps, games, tools, SaaS projects, and experiments, then ask one clear question so contributors know what to check. Other builders and product-minded contributors answer requests on UX, onboarding, copy, bugs, conversion, and launch readiness. Useful contributors earn rewards, credits, reputation, and visibility.
Features
- Showcase AI-built and vibe-coded products
- Ask one clear, targeted feedback question
- Get actionable feedback from real builders
- Reward helpful contributors with credits and reputation
- Discover projects and connect with builders
Use Cases
- Validate an MVP before launch
- Improve UX and onboarding
- Find bugs and confusing flows
- Refine copy and conversion
- Review launch readiness and new updates
Comments
Forcing one specific question is the right constraint. Most feedback threads die because the ask is just 'thoughts?'. The part I would want to see spelled out is how you stop drive-by 'looks clean' answers from earning rewards, since that is where feedback marketplaces usually go sideways. Is there any weighting by whether the builder marked an answer useful?
The one-question constraint is the smartest part of this - generic 'what do you think?' posts get useless replies, but forcing a specific question turns feedback into actionable tasks. For browser extension builders like me, landing-page conversion and onboarding reviews are the two categories I'd camp on. Question on reviewer quality: is reputation tied to acceptance by the requesting builder, so consistently useful reviewers get surfaced over time? And is there any way to flag a review request as urgent for pre-launch checks?
Limiting each listing to one clear feedback question is a better constraint than an open comments thread that drifts into praise. Credits and reputation for helpful replies also give a reason to be specific about UX, bugs, or copy. I would want to see whether askers can mark a reply as the answer they acted on, so the credit system is tied to usefulness rather than length.
Premium Products
Sponsors
Buy
Makers
Makers
Comments
Forcing one specific question is the right constraint. Most feedback threads die because the ask is just 'thoughts?'. The part I would want to see spelled out is how you stop drive-by 'looks clean' answers from earning rewards, since that is where feedback marketplaces usually go sideways. Is there any weighting by whether the builder marked an answer useful?
The one-question constraint is the smartest part of this - generic 'what do you think?' posts get useless replies, but forcing a specific question turns feedback into actionable tasks. For browser extension builders like me, landing-page conversion and onboarding reviews are the two categories I'd camp on. Question on reviewer quality: is reputation tied to acceptance by the requesting builder, so consistently useful reviewers get surfaced over time? And is there any way to flag a review request as urgent for pre-launch checks?
Limiting each listing to one clear feedback question is a better constraint than an open comments thread that drifts into praise. Credits and reputation for helpful replies also give a reason to be specific about UX, bugs, or copy. I would want to see whether askers can mark a reply as the answer they acted on, so the credit system is tied to usefulness rather than length.
Premium Products
New to Fazier?
Find your next favorite product or submit your own. Made by @FalakDigital.
Copyright ©2026. All Rights Reserved