We pull recall data from 41 government sources across 13 countries.

The single biggest cause of food recalls isn't bacteria, metal fragments, or pesticides. It's undeclared allergens. Mislabeled ingredients. A factory that processes peanuts on the same line as "peanut-free" granola bars and doesn't update the packaging. 45% of all food recalls come down to someone not listing what's actually in the product.

Since sesame was added as a major allergen under the FASTER Act in 2023, there's been a new wave of these. Manufacturers are still catching up on labels and sourcing three years later.

The thing that gets me is how invisible this is. If you don't have allergies, you'll never hear about these recalls. They don't make the news. But for the families who rely on those labels, each one is a near-miss.

Since sharing Prodshort here on @producthunt , we ve received a lot of early feedback. Ideas, feature requests, small improvements, UX feedback sometimes things we didn t even think about.

How do you decide what to actually build from all that feedback?
Some feedback looks useful at first, but once you test it, you realize it adds complexity without real value. Other times, a small suggestion turns into something essential for the product.
Would love to hear from your experience:
How do you handle early feedback without going in too many directions?

I m getting ready for my first-ever product launch, and I ll be honest, I m feeling like the ultimate underdog. I m a 50-year-old Realtor from the Canadian Prairies, and looking at some of these launch teams with their massive marketing budgets and VC backing is a little intimidating.

I built this solution because I had a problem I needed to solve: my own doomscrolling habit. Since I don't have a technical background, I used AI as my "expert partner" to help me navigate the roadmap and bridge the gaps I didn't even know I had.

But now that I'm at the starting line, I have to ask: Can a solo, non-tech founder still rank well here? Or has the platform shifted to favor the big players with the huge email lists?

I d love to hear from other indie makers how do you compete when you don't have a marketing department? Is the "Maker's Story" still enough to get people to pay attention?

Building in public is important today. It helps you build a community, get feedback, and create traction around your product. But creating content to share every day shorts, posts on X, LinkedIn, Instagram can quickly become boring and very time consuming.
By recording your meetings with Prodshort, you get content ready to share: Shorts, X posts, LinkedIn posts... You keep things authentic, because the AI documents what you actually do and doesn t create fake content from scratch. Your real progress, your real discussions, your real decisions become things you can share.

It makes build in public much easier. You can share updates about your project directly from your calls: progress, ideas, feedback, small wins... Stay consistent with your build in public without adding extra work to your day !!

I formally studied marketing as a university program (5 years), and due to inspiration on social networks, it feels completely natural to do it, even easy to learn (because most of the time you just guess what might work for you).

BUT

I'll go first.

I still reply to every comment manually. Reddit, LinkedIn, Product Hunt, forums, Twitter, Discord. Every single one.

AI could do this. There are tools that generate replies, post on schedule, analyze sentiment, even mimic your brand voice. But I don't use them. Here's why.

A 2024 study on community engagement across 500 brands found that personalized responses drive 3.2x higher retention and 4.7x more repeat interactions than automated replies. People can tell when a response is copy-pasted. They can feel when no one actually read their comment. The average user only needs 2-3 automated interactions before they disengage entirely.

Hey Product Hunt family!

Just wanted to share a little "behind the scenes" pain from the OptiClear launch. We all know the Apple App Store review process can be a rollercoaster, and I definitely hit a loop.

I had built this sweet "Invite a Friend" feature. The logic was simple: generate a code, share it with a friend, and both of you earn free premium days. A classic, organic growth loop, right?

Well, Apple hit me with a rejection. Apparently, unlocking premium features outside of their standard In-App Purchase flow (even as a reward) is a big no-no.

Hi everyone! I m Rhonda, a Realtor from Saskatoon. I m definitely not your typical tech founder I m 50 years old and I built my first app because I was tired of my phone "winning" over and over again.

We ve all been there: you check your phone for "one second" and suddenly an hour is gone. I call it the "scroll trance". Most blockers I tried felt like an "adult time-out" they were frustrating and made me feel like I was being punished. I don't want to be punished; I love my phone! I just want to stay in control of my time.

I was reading Nika's thread here about free vs paid features. Really made me think.

Link: https://www.producthunt.com/p/ge...
( shout-out to @busmark_w_nika ! )

She talks about giving generalized advice for free, but charging for specific, tailored help. That's a good framework.
But most product owners figure this out after they build, not before.

That's backwards.

Every top athlete has one (Lebron James, Novak Djokovic, Serena Williams). And it turns out, so do most of the biggest names in tech.

Steve Jobs mentored Mark Zuckerberg in the early days of Facebook. Eric Schmidt mentored Larry Page and Sergey Brin at Google and later credited that relationship as one of the key reasons Google scaled the way it did. Bill Campbell, known as "the Coach of Silicon Valley," mentored Jobs, Schmidt, Jeff Bezos, and dozens of other founders throughout his career.

1. I've always been on the personal brand side. More and more founders are building it now (sometimes even before the product is ready while it's still in development, before seed fundraising). The CEO builds their position so the product sells more easily at the official launch.

2. But I have experience with people who built the product, scaled it, and only then did we discover who was behind it.

Honestly, with the first approach, I'd be concerned that people invest more in me as a person than in the product. People would idealise the founder and overlook the product's flaws (which could hurt development and constructive feedback).

+ I noticed the most common mistake that many people who started building a personal brand first, connected their product to their personal accounts (emails, social media, etc.) and started having a problem selling these things, because they cannot "give someone keys" to their personal profiles.

Today, this graphic caught my attention:

It featured individuals who managed to build significant profit while running their businesses solo, without employees. Until now, I ve seen these more as exceptions rather than the norm.

There are so many launches on Product Hunt every day. How do you decide which ones are worth clicking into?

What s your #1 filter or shortcut?

I am a Computer Science student doing research into how solopreneurs and small startups create new apps and what their stack looks like. Particularly, I'm interested in how you handle things like authentication, billing, and permissions/authorization in your apps.

Let me know what you're working on below and how you're going about it -- I'd love to connect for some quick calls to learn about your product and talk about your process in building it!

Hey everyone! I'm Maliik, a solo dev building Nibble, a food recall alert app for families. It tracks recalls personalized to your household, including kids and pets.

Currently in closed testing on Android and live on the web. Been a long road getting here as a solo builder, so figured I'd finally say hello to the community.

With the advent of clawdbots, it's as if we've all lost our inhibitions and "put our lives completely in their hands."

I'm all for delegating work, but not giving them too much personal/sensitive stuff to handle.