Connect with the Product Hunt community

Been thinking about this a lot for anything where the core pitch depends on numbers - finance, health, fitness, anything with metrics attached.

You can publish real data, real logs, whatever proof exists - but a brand-new account with no history saying "trust me, the numbers are real" is exactly what a scam would also say. The data being genuinely real doesn't automatically solve that problem.

For anyone who's launched something like this - how did you actually get people to believe you early on? Public/verifiable data, third-party validation, just time and reputation compounding, something else entirely? Genuinely curious what's actually worked for people here versus what sounds good in theory.

I recently ran my first small paid acquisition experiment for a workout-tracking mobile app.

The campaign targeted Android users in Poland and produced:

• 27 installs

• 3.47 PLN cost per install

• 8,705 impressions

• 4,481 accounts reached

• 1.94 average frequency

The campaign was planned to run for seven days, but I stopped it after four because the number of daily installs appeared to be declining.

I ve noticed I keep switching between notes apps and task managers because I m never sure where something should go. Sometimes a quick note turns into a task and then I end up copying it somewhere else. Curious how other people handle this do you keep notes and tasks separate or use one app for both?

The better an agent gets at handling edge cases the easier it is to ignore why those edge cases exist in the first place. When exception handling becomes seamless, the urgency to fix broken inputs completely disappears.

At some point fixing the symptom repeatedly becomes more expensive than resolving the root flaw in your pipeline.

What rules or logs do you set up to force your workflows to escalate recurring exceptions rather than just auto resolving them forever?

Two weeks of Search Console data pushed me into a CTR experiment. Ranking was not my problem. Position improved from 41.1 to 27.6 over a month and the clicks did not follow, so I went after titles instead.

The first page I picked was a manufacturing cost post sitting at 1,342 impressions, 0 clicks, position 6.2. I retitled it to lead with the 4k to 30k price bands the page already contained. That one I still feel good about.

The rapid growth in daily forum posts is making this place feel much more like Reddit or Twitter lately.

The focus seems to have moved from deep product feedback to general marketing quick polls and high volume posting.

While more activity is good for engagement it s getting harder to filter out generic chatter to find actual useful insights.

We tried feeding our entire component setup into AI to speed up wireframing. It definitely output clean on brand code but everything started feeling a bit dry because it relied entirely on past decisions.

Sometimes a fresh user flow needs a completely new pattern rather than forcing old buttons and cards into a spot where they don't quite belong.

For product teams using design tokens with AI: do you force total adherence, or do you let the prompt stray outside your system to test new concepts?

I've been going through a ton of sales call recordings the last few months, mine and a bunch of test calls we use to build the thing I'm working on, and there's a pattern I keep running into.

The deal almost never dies on the first soft no. It dies right after the seller pushes again.

If I can't figure out what something costs in under thirty seconds, I'm out. And if I see "Contact us" as the only option, that's an instant close, no matter how nice the product looks.

I don't think this is unreasonable. I just want to know if I can afford to even consider something before I get attached to it. But I've had people tell me I'm missing out on good tools just because they hide their pricing, which I guess is technically true.

Anyway, I've noticed pricing pages tell you more about a product than the landing page does. How it's structured, how many tiers, what's locked behind the paywall it's all right there if you look.

Do you judge products by pricing too, or do you actually read the whole page first?

I've been on Product Hunt since 2017, but my last launch was back in 2024. Coming back now, it feels like a lot has changed: the launch flow, the forums, how discussions work, how makers show up in the comments.

So I'm curious about the changes you actually like. What's better now than it was a couple of years ago? And is there anything you miss from the old days?

For people who have launched here before... What ended up being the most valuable outcome of your launch besides rankings or upvotes?

Is it customers? product feedback? partnerships? new connections? visibility? Or something completely unexpected?

Would love to hear what actually lasted beyond launch day.

I've gone back and forth between these two more times than I should probably admit.

Coda always pulls me in because I can make tables, buttons, little automations, etc. It's fun until I've somehow turned a simple notes system into a project of its own.

Then I go back to Notion because I just want to write things down and find them later.

And then, inevitably, I miss something Coda did better.

I love checking out new products but scrolling through the main feed can get exhausting fast. Everything looks amazing in the headline but after opening a few tabs to check out demos my brain just taps out. Half the time I end up closing the browser without testing a single thing because there are just too many options thrown at me at once.

Do you guys have a trick for filtering through daily launches, or do you only drop by when you're looking for something specific?

Product Hunt s new forum UI is great, but the notification system forces a tough choice: get spammed by every individual thread notification, or miss out on important posts entirely. The solution? Add a "Follow Forum" option so users can subscribe to topic hubs directly.

There sa common assumption in SaaS that faster support always equals better retention but I m starting to doubt that. Dropping everything to reply instantly can actually distract you from high-impact work while training users to rely on you for simple answers.

Taking a bit longer to respond often pushes users to explore the product or read the FAQs which builds better long term habits.

For those running small products or indie software: how do you set boundaries on support time without making customers feel ignored?

I used to think answering support tickets within minutes was the secret to keeping users happy. But after being forced to step away for a few days, I realized fast replies were actually backfiring.

Because I was answering right away, users stopped checking our basic help guides and just emailed us for every minor thing. Giving them a bit of breathing room actually encouraged them to figure things out on their own.

Does anyone else feel like instant customer support creates bad habits instead of better retention?

For a long time I treated everyincoming support message like an absolute emergency. It was exhausting and constantly pulled me away from actually building and fixing the product.

When I was forced to slow down my response time recently nothing broke. In fact churn didn't go up at all and users started using our docs instead of waiting on me.

It made me rethink my whole support strategy. Curious how other founders handle this what s your realistic response window and have you noticed any downside to taking a few hours to reply?

I ve been thinking about what actually makes me uncomfortable about letting an AI agent take actions.

It may not be the size of the action.

It may be whether we can undo it.

I've used Product Hunt in the past to launch my company's AI/XR-related projects, with some success. I'm now building smart home stuff as a side project, and I wonder if people here are interested in that or not? My feeling is that everything here is about AI agent nowadays .

Thoughts? Thanks!

A two minute check for anyone who receives signed webhooks. Find the line where your code reads the signing secret from the environment. Then find out what happens to a request when that variable is not set at all.

I expected the answer to be that everything fails. That is what a missing secret sounds like: no key, so no signature can match, so every event is refused, and the worst case is a noisy outage somebody notices within the hour.

It is not what happens. An unset variable arrives in most config layers as an empty string, and an empty string is a perfectly valid key to a hash function. The official library I use takes the secret, computes the expected signature with it, and compares. It never asks whether the key is empty. So with no secret configured, the endpoint does not refuse everything. It accepts anything signed with the one key every person on earth knows, which is nothing at all.

That turns a missing line in a deployment file into a way to send my system a forged payment confirmation, with a signature that verifies.

I ve realized I am far more likely to stick with a new tool if I can test it out on my phone first. Whenever a setup requires me to open my laptop, log into a browser, and configure everything from a desk, there is a good chance I will put it off and forget it exists entirely. Mobile testing just fits better into small pockets of free time throughout the day.

The problem is that a lot of products still feel like they were built desktop-first, treating the mobile app as a stripped-down afterthought. When the phone experience feels clunky or limited, I lose interest quickly, even if the tool itself is solid.

Does mobile access change whether you actually end up using a new tool? Where do you normally test things out for the first time?

I ve tried a few AI powered coding editors and the workflow feels quite different from using a traditional IDE. The suggestions are useful, but sometimes I prefer the predictability of a normal setup. For web development, which approach works better for you and why?

I spent a few years writing case studies for B2B tech companies, and the writing was never the hard part.

The hard part was getting the actual story out of the engineers and PMs who did the work.

By the time marketing wanted to turn a project into a case study, the people who knew what really happened were busy, moved on, or couldn't remember the numbers.

I've been working on internal documentation recently, and one thing that keeps coming up is that creating the documentation isn't necessarily the difficult part keeping it accurate is.

A process gets documented, someone changes a few steps a month later, and eventually the original guide no longer matches what people actually do.

I've seen teams handle this in very different ways:

• Assign an owner to each document

• Review SOPs every few months

• Update documentation whenever a process changes

• Keep a video walkthrough alongside the written instructions

• Just fix the documentation when someone notices it's wrong

Been thinking about this since Llama 4 Scout is quietly running Meta AI across WhatsApp, Instagram, and Messenger, which is a genuinely massive footprint, arguably bigger reach than ChatGPT in a lot of markets outside the US.
And yet almost nobody in the AI-visibility/GEO conversation talks about it. Every "which LLMs should I track" list defaults straight to ChatGPT, Gemini, Perplexity, Claude.

Makes sense in one way. Scout's a smaller, more efficient model (10M token context, MoE architecture) built for scale and cost, not for being anyone's primary "ask it everything" assistant the way ChatGPT is. But the distribution is the part that's hard to ignore: it's sitting inside apps billions of people already have open every day, recommending things in casual chat context rather than a dedicated search box.

Genuinely curious, for anyone building or using AI-visibility tools, does Meta AI even show up in what you're measuring?
Is it worth the effort to track, or is the actual query volume for anything commercial/brand-related just too low to matter yet compared to the "real" search-intent surfaces?