Product Hunt unveiled a list of 18 dev-first products nominated for the Golden Kitty Award 2023 in the Developer Tools category. I analyzed the following data to identify some trends:
People rarely type out a long paragraph explaining every little annoyance when they cancel a subscription they usually just check a generic box like "missing feature" or "too expensive" to get it over with. But when you actually look at session replays you notice users getting stuck on a weird button placement or a confusing login screen for three minutes straight before dropping off. Those tiny micro-frustrations add up yet nobody ever puts them in a feedback form.
What methods do you use to spot these hidden drop-off points?
When you're starting out it feels natural to build everything yourself internal docs task trackers chat systems just to keep users inside your app.
But at some point you realize users literally hate logging into yet another dashboard just to check one notification. They want your product to meet them where they already spend their entire day. It s super painful to put a pause on your own product roadmap to spend weeks building external integrations.
How did you figure out the exact moment to shift focus from native features to ecosystem plugins?
I had (what I thought was) a great product idea, so I described it to Fable 5 and asked for its thoughts. It basically called the idea trash and explained why, then gave me a tweaked version that it said was better.
I thought through the tweaked version and it was actually way better than my original idea.
I've started asking one thing before I give anyone advice about their product. Do you want me to help you think, or do you want me to tell you what I would do?
They are completely different conversations and most of the time people want one and receive the other.
Ask someone what they think of your product and you get a polite opinion with nothing underneath it.
Ask them what they did last time they used it and you get a story. A specific moment. The thing that broke, the thing they skipped, the thing that surprised them.
I used to keep my chat apps open all day replying to every ping within five minutes because I thought it showed dedication.
All it really did was chop my day into tiny useless pieces where I couldn't focus on anything meaningful. The day I started batching my replies to just twice a day my anxiety dropped and I actually finished things on time. Nobody got mad and the world didn't end.
How do you manage your communication loops without letting constant notifications wreck your focus?
We had an AI agent refactor our database submission tables to fix load times. The pull request looked super clean and performance metrics improved instantly so everything seemed fine at first.
A few days later we realized it stripped out essential audit columns because nothing in the database constraints explicitly flagged them as required. It optimized strictly for raw execution speed over domain context.
The baseline has moved fast this year. AI-generated UI is good enough now that for a lot of products the core screens come out clean on the first pass , dashboard, settings, checkout, all serviceable. That used to be weeks of work for a solo maker. It isn't anymore, and I don't think that's a bad thing.
I'm a UX designer, mostly on complex, high-trust products, and here's where I think it currently stops: AI generates screens, but product experience lives in the sequence between them. The happy path is basically solved. What doesn't come out of a prompt is what happens when someone is confused, hesitant, or something broke empty states, the permission ask that feels invasive, the error that doesn't say what to do next, the ability to undo something. None of those are visual problems, so a tool optimizing for a good-looking screen has no reason to raise them.
