Public conversation snapshot
Follow the community thread graph.
Vibecodr conversations collect launch notes, feedback, architecture questions, and discussion around runnable web apps. This fallback keeps the public thread index linkable even when the SPA shell is not executing.
- Hottest
- Section: suggestions
-
@vibecodr • Jan 24, 2026 • Suggestions
How can I improve Vibecodr for you?
When I started building Vibecodr, I was really just trying to answer a question I kept asking myself: why is it so hard to deploy things? Once I got some real momentum there, another realization hit me. You can deploy projects all day, but if there’s no community to experience them with you, it eventually starts to feel kind of empty. Let’s be honest, most of us don’t have thousands of followers on X or Threads ready to interact with everything we make. We build things that matter to us, and then they just… sit there. That gap is why Vibecodr exists. At this point I’ve been building this for months, and I’m getting to the stage where I really need input from the people who would actually use it. I want to know what would make this something you’d come back to every day. What do you wish existed? What feels missing? What do you hate or find frustrating? No suggestion is too small. My goal is to grow this little space into something genuinely useful and meaningful for all of us, and the only way that happens is if you help shape it. Anywho, thank you as always, -Braden