My co-founder and I are getting ready to launch the next iteration of Radiant, our AI music app. It's been pretty sticky so far with users, which is great but my priority is to increase users prior to launch. Any tips?
Lessons from Athena s surprising coverage and what founders can learn about finding the right reporter, framing stories, and pitching press
The Wall Street Journal rarely covers seed-stage startups let alone one raising just $2.2M. That s why I was surprised to see Athena, an early-stage company working on how large language models surface brand-related content, featured in Katherine Blunt s article about the demise of traditional Google search.
Checklists always look the same: tested, works, has a landing page. The part that actually slowed me down building in personal finance wasn't any of that, it was "would I trust this with my own bank statement," which isn't really a checklist item, it's more of a gut check that doesn't show up until you're already deep in it.
Curious what that bar looks like for people in adjacent spaces, health data, identity, anything where "it works" and "it's safe to trust" aren't the same question.
This came to my mind when I read about how the creation of Sora has raised concerns that it could be an AI equivalent of TikTok (critics warning it could fall into the same addictive patterns as other social platforms).
And after several messages with some people, I also noticed how I wasted a lot of time on my desktop instead of doing something productive or learning.
While building an OpenAPI SDK generator, I realized that real-world API specifications are often much messier than the examples we see in documentation. I'm curious what's the biggest challenge you've encountered with OpenAPI? Circular references? Inconsistent naming? Missing schemas? I'd love to hear your experiences.
I run three businesses and for a long time I assumed the big decisions were the risky ones. The one that actually cost me was small, a supplier invoice I meant to double check and kept pushing to tomorrow, and by the time I noticed the error it had already gone through two billing cycles. Nothing about it looked urgent in the moment. No fire, no message marked important, just quiet until it was expensive.
Curious what your version of that was, the small thing nobody in the moment would have called risky, and whether you changed anything afterward or just started worrying about the next quiet one.
For years, there s been one place where big-name tech products could enjoy a second life, albeit without most or all of the people that got them there: Bending Spoons.
The Italian company, which is valued at $11B and reports 300M+ monthly active users, acquired Eventbrite for $500M this week.
In our meetings, we usually keep debating about what features to add to our product. But honestly, we need to be able to say NO to that.
Building became even easier with AI, so it is tempting to add a ton of features. The cost is how complex your app becomes. This is why products get messy fast. Usually it looks fine for old users, because they learned each feature slowly while you built it. But new users open the app and feel lost.
@busmark_w_nika asked yesterday what PH is missing and what people would improve. I am sure the team has enough to cook with now. So I want to ask the opposite:
What should Product Hunt kill? What feature would the product be better without?
What did you say NO to in your own product?
What feature would you remove from a big product you use?
