I launched a developer product with no audience. Here's what happened.
Three days ago, I had no waitlist, no audience, and no promotion budget.
This week, DEV·TV finished #5 Product of the Day on Product Hunt, out of 67 featured launches.
Here's what actually happened — and what I'd tell someone about to launch something with basically nothing behind it.
What DEV·TV is
DEV·TV is a TV for the developer internet.
GitHub, Hacker News, DEV, Hugging Face, framework releases, research papers, CVEs and more become channels that play continuously instead of requiring you to keep opening tabs and checking them.
It's deliberately simple:
One HTML file. No backend. No login. No build step.
Try it: https://shouvik12.github.io/devtv/
Code: https://github.com/shouvik12/devtv
Product Hunt Link: https://www.producthunt.com/products/dev-tv?launch=dev-tv
What seemed to matter
I can't see Product Hunt's ranking formula, so these aren't claims about how the algorithm works.
They're simply the things I saw happening during the launch.
1. Real comments mattered more than I expected
DEV·TV finished with 152 points and 18 comments.
The interesting part wasn't just the number of votes. People were actually asking questions, suggesting channels and discussing what the product could become.
That gave me something much more useful than a pile of "nice work" comments:
people telling me what to build next.
2. Shipping during the launch was surprisingly powerful
Someone asked for Swift releases in the comments.
So I added Swift releases to the Releases channel while the launch was still running.
Then I replied to the comment and showed what had changed.
That tiny interaction probably did more for the launch than another paragraph of marketing copy could have.
The product wasn't just being presented.
It was responding.
That changed the nature of the conversation from:
"Here's my product."
to:
"Here's my product — tell me what it should become."
3. Being a small open-source project became part of the story
There were much larger launches around me, including launches participating in Product Hunt's sponsored Vercel Day contest.
DEV·TV was just a solo open-source project.
So ending up at #5 became interesting in its own right.
I didn't have a launch team, paid acquisition or a big existing audience.
I had a working thing and people who happened to find it interesting enough to talk about.
That was enough to get it into the conversation.
What I got wrong
I assumed GitHub stars would follow naturally from Product Hunt traffic.
They didn't.
People came, tried the TV, and left.
Which makes sense.
Product Hunt is fundamentally a product-discovery environment. Someone can spend two minutes playing with DEV·TV and have no reason to open GitHub afterward.
Developer-specific communities are different.
That's where someone might actually care about the implementation, fork it, contribute, or star the repo.
So I'm changing that now.
There's a direct Star on GitHub path inside DEV·TV rather than relying on someone to discover the repository through the README.
The lesson for me:
Don't assume traffic from one community automatically converts into the behavior you want from another.
What's next
I'm taking DEV·TV to Show HN next.
That should be an interesting experiment because the audience is different.
Product Hunt gave me product feedback.
I'm curious what happens when the audience is primarily developers looking at the implementation, the idea, and whether they'd actually leave this running in a tab.
And that's probably the biggest thing I've learned from this launch:
Don't optimize the launch before you have something people can react to.
Give people something real.
Listen to what they say.
Ship the thing they ask for when you can.
Then watch what happens.
If you've launched something with little or no existing audience, what was the smallest thing you did that ended up making the biggest difference?
Top comments (0)