I'm co-founder at daily.dev (thanks for the mention in the articles part). Here's what I see working for open-source projects right now.
Your Product Hunt numbers match what we hear from a lot of maintainers: a good spot gets you a spike and then it's over, recently many bots have also found their way to PH unfortunately. The projects that win treat the launch as starting point. They write about each release, a benchmark, battle scar, and generally try to be useful in their domain.
I'd also push back a bit on the AI point, like Ivan did. Cursor will write the gallery component, sure. It won't maintain a parser or a sync engine for you, and people still go looking for those. They want to focus on their core problem. What helps is describing the problem in the same words they search for.
That's the idea behind daily.dev for Startups. It gives your developer tool its own page on daily.dev and puts your posts in the feeds of developers who follow your topics, so each post keeps working after launch day: daily.dev/startups/
Hello, Ido! Thanks a lot for your comment. Yes, my thoughts on ProductHunt were based on my own experience. The fact that you have features tailored for startups is really cool, I’d love to give it a try sometime. I’ve been using daily.dev for a while now, and I think it’s a great concept.
As for AI, it’s simply everywhere these days, so it’s no longer capable of surprising anyone. It’s even difficult to come up with a unique selling proposition.
The Product Hunt example is a useful reminder to separate a distribution event from lasting adoption. For a developer tool, I would track the first successful setup and a second real use, not only stars after launch. A small tutorial solving one specific problem can reveal more about the audience than another broad launch announcement.
Well, that’s true, but in the open-source world, the term "tool" often bears little resemblance to what it meant 10 years ago—back when people would just download an npm package for an image gallery. Nowadays, apart from AI, nobody reads the documentation.
Hard disagree on the 'with AI nobody needs your product' bit. There's way more junk now, sure, but a tool that fixes one specific painful problem still gets picked up the same day. Did nailing the audience first move your numbers on past projects, or just how fast you got there?
That’s what my experience has taught me. In Cursor, a prompt can solve a specific problem—either by pulling in a package or by writing the code from scratch. It’s not 2010 anymore, back when you could create a gallery component on npm and rack up 100,000 downloads in a single week.
Your embed idea gives me a concrete experiment. I'd show the same repository in two ways: a generic project description and one tiny before-and-after example of the problem it solves. Then count people who reach a working setup, not just embed clicks. That could tell me which audience understands the value before I spend another week promoting it.
We're a place where coders share, stay up-to-date and grow their careers.
Great article! 😸
Promoting OSS is really difficult, so I think a platform where developers can easily showcase and discover open-source projects is a really nice idea.
I’m looking forward to seeing how it grows! 🚀
I'm co-founder at daily.dev (thanks for the mention in the articles part). Here's what I see working for open-source projects right now.
Your Product Hunt numbers match what we hear from a lot of maintainers: a good spot gets you a spike and then it's over, recently many bots have also found their way to PH unfortunately. The projects that win treat the launch as starting point. They write about each release, a benchmark, battle scar, and generally try to be useful in their domain.
I'd also push back a bit on the AI point, like Ivan did. Cursor will write the gallery component, sure. It won't maintain a parser or a sync engine for you, and people still go looking for those. They want to focus on their core problem. What helps is describing the problem in the same words they search for.
That's the idea behind daily.dev for Startups. It gives your developer tool its own page on daily.dev and puts your posts in the feeds of developers who follow your topics, so each post keeps working after launch day: daily.dev/startups/
Hello, Ido! Thanks a lot for your comment. Yes, my thoughts on ProductHunt were based on my own experience. The fact that you have features tailored for startups is really cool, I’d love to give it a try sometime. I’ve been using daily.dev for a while now, and I think it’s a great concept.
As for AI, it’s simply everywhere these days, so it’s no longer capable of surprising anyone. It’s even difficult to come up with a unique selling proposition.
yap requires everyone to think harder to go above the noise level
The Product Hunt example is a useful reminder to separate a distribution event from lasting adoption. For a developer tool, I would track the first successful setup and a second real use, not only stars after launch. A small tutorial solving one specific problem can reveal more about the audience than another broad launch announcement.
Well, that’s true, but in the open-source world, the term "tool" often bears little resemblance to what it meant 10 years ago—back when people would just download an npm package for an image gallery. Nowadays, apart from AI, nobody reads the documentation.
Hard disagree on the 'with AI nobody needs your product' bit. There's way more junk now, sure, but a tool that fixes one specific painful problem still gets picked up the same day. Did nailing the audience first move your numbers on past projects, or just how fast you got there?
That’s what my experience has taught me. In Cursor, a prompt can solve a specific problem—either by pulling in a package or by writing the code from scratch. It’s not 2010 anymore, back when you could create a gallery component on npm and rack up 100,000 downloads in a single week.
And how do you promote your open-source projects?
Your embed idea gives me a concrete experiment. I'd show the same repository in two ways: a generic project description and one tiny before-and-after example of the problem it solves. Then count people who reach a working setup, not just embed clicks. That could tell me which audience understands the value before I spend another week promoting it.