Now I'm launching on Product Hunt. Will it work?
Yesterday I shared the story of how I went from selling medical icons on stock marketplaces to building my own product instead.
Today I’m launching that product on Product Hunt. Honestly, this feels more intimidating than building it.
Building Glyfiq was actually fun. I had zero development experience, so I vibe coded the entire thing with AI. Back in April I started working on the Figma plugin, and by the end of the month I had the first version live with around 200 icons.
Since then I’ve expanded the library to 400+ icons and I’m currently preparing the next batch. The long-term goal is to bring in my entire archive of 6,000+ medical and healthcare icons.
Now comes the harder part: finding the people who actually need it. I’m a designer. Marketing is new territory for me. The more I think about it, the more I realize that waiting for people to discover a niche healthcare icon plugin probably isn’t a strategy. I may need to start reaching out directly to healthcare companies, clinics, agencies, and independent designers.
Still, Product Hunt feels like a good test. Maybe nothing happens. Maybe a few people find it useful. Maybe I’ll learn something that helps with the next step. Either way, it’s another experiment.
If you’ve launched on Product Hunt recently, I’d love to hear how it went.
Vote on Product Hunt 👉 https://www.producthunt.com/products/glyfiq?utm_source=other&utm_medium=social
Any support — a vote, a comment, sharing with a designer friend — means more than you know.
You said you vibe coded Glyfiq with zero development experience, and it already had real users across Figma and Framer. Now that it’s live, who owns dependency and security updates when those platforms or packages change, you or the AI agent?
That's a fair and important question.
Practically speaking — I do. When Figma or Framer updates their plugin API and something breaks, I'm the one who has to fix it. The AI helps me understand what changed and how to patch it, but the responsibility is mine.
So far it's been manageable. Both platforms notify developers of breaking changes in advance, and the fixes have been within what I can handle with AI assistance. But I won't pretend I have the same safety net a developer with 10 years of experience would have.
The honest answer is: vibe coding gets you to launch, but it doesn't make maintenance disappear. It just changes who you're debugging with.
Exactly, and this is the reason I'm building StackRadar: to help teams and individuals do the boring dependency maintenance so they can focus on building the product. Perhaps you would like to give a try?
I’d be careful with the lesson you take from Product Hunt.
The risk isn’t a bad launch. The risk is drawing customer-acquisition conclusions from a channel that may be measuring something else entirely.
For a product this niche, the important question may not be whether Product Hunt works. It’s whether the people who respond are the same people you ultimately want to sell to.
That’s not a decision I’d make casually because getting it wrong can create a lot of misleading signal.
My strategy is more about getting into at least the top 30 on day one and potentially attracting the attention of various design communities that follow new products. As for attracting a direct audience during a product launch, I'm almost certain it's zero. I'll try to share the statistics tomorrow after the launch on Product Hunt. But thank you for your valuable advice and for commenting on my story.
That's a reasonable way to look at it.
I'd be especially interested in whether the design-community attention and the eventual paying-user signal end up pointing in the same direction.
Looking forward to seeing the numbers tomorrow.