Since sharing Prodshort here on @producthunt , we ve received a lot of early feedback. Ideas, feature requests, small improvements, UX feedback sometimes things we didn t even think about.
How do you decide what to actually build from all that feedback? Some feedback looks useful at first, but once you test it, you realize it adds complexity without real value. Other times, a small suggestion turns into something essential for the product. Would love to hear from your experience: How do you handle early feedback without going in too many directions?
Trophy is now powering over 24M streaks which is kind of crazy to think about considering we only launched 1.0 here in January this year. One of the parts I find most interesting about building horizontal infrastructure is that as you scale and power more and more products you get to see insights that most teams building in isolation will only see a part of, and you can use those insights to make the the infrastructure better for everyone. For example, because we power streaks for so many users, Trophy can tell that 25% of all streaks are lost on a Friday, closely followed by Saturday (19%) and then Wednesday (18%).
ClawOffice was a bit of a gimmick - a 3D virtual office for AI agents. It was fun to build and got some attention on launch, but let's be real: it didn't take off. People thought it was cool for a minute, then moved on. No real retention, no real problem being solved.
Here's what I actually learned from it:
Novelty value. A cool concept gets you a launch day. It doesn't get you users who come back on day 30.
I was building for the demo, not the workflow. ClawOffice looked great in a screenshot. It didn't solve anything measurable for anyone.
"What gets tracked gets improved" is real. The founders I talked to afterward all had the same pain - they were shipping features and running experiments with no clue what was actually driving revenue.
no one asked actually but to be honest i think i had to say something cuz i kinda feel bad that all the support i got here just went away... right now if you visited the domain finkitty.com you will find out that its listed for sale, i took this decision after a very long sitting with myself and ended up deciding that since im not having any users in this app i might just kill it and shift my focus into something else (working on templateson.com now) yet im still holding it inside cuz i do like the name of this app and i feel like it has very good potential and i just cant see it.. so... if you have any great idea for an app named "FinKitty" please let me know thanks
I don't have a CS degree. Never shipped a product. Never started a company. One month ago I didn't know what a Next.js route was.
I built Four-Leaf.ai, an AI career prep platform with voice mock interviews, resume tailoring, and negotiation coaching. It's live, it has users, and I launched it on Product Hunt today.
Hi everyone! I m Ayesha (@AyeshaBuilds), a designer turned indie hacker from Bangladesh.
I ve spent years looking at landing pages that look beautiful but fail to convert a single visitor. It s a common trap: we focus so much on the "vibe" that we forget to tell people why they should care.
Lately, I ve been looking closely at how independent builders and small teams are managing AI knowledge bases. It feels like the default "industry standard" is to immediately reach for a complex RAG pipeline and a heavy, paid Vector Database.
But I'm starting to wonder if we are over-engineering this for 90% of standard use cases.
Vector DBs are incredibly powerful for massive scale, but for smaller or non-massive datasets, they can be expensive, complex to query, and act as complete black boxes. If a search returns a weird chunk, diagnosing it is often a nightmare.
