Connect with the Product Hunt community

Something you thought was a great idea at the time, but looking back you'd do completely differently.

Could be:
Launching too early
Launching too late
Building features nobody asked for
Not talking to users enough
Focusing on the wrong metrics
Having zero launch plan

Let's help each other avoid painful lessons.

What's your story?

This is not going to be a post about "passive" income completely.

It s more about how you started making money without selling your time. Tho still investing a little bit of it.

The one where Skim stops reading the CSS and starts reading the letter. A tiny release: one fix, one heuristic, zero new buttons.

Still standing on @gildas-refacto's shoulders

All of v1.0.19 was theirs #30, their fourth merged PR after #16, #18 and #29, where they traced three separate translation bugs down to individual Unicode code points and measured every fix over 20 runs.

Which made this release slightly embarrassing to write: they spent all that effort making the translation trustworthy, and it turns out we were sometimes not offering it at all. Fixed below. Thank you again.

Fixed

• The Translate chip shows up on mail that needs it. Some senders build their plain-text version by ripping the tags out of their own HTML <style> element included so the email "text" opens with a few hundred characters of .bio{margin:auto}. Skim guesses the language from that text, and on one real newsletter 72% of the sample was CSS: the guess came back "not confident", and a perfectly English email got no translation offer in a Russian UI. Braces are not a language.

  Now a leaked stylesheet gets removed first and since the language guess runs fresh on every open, mail already sitting in your database is fixed too, no resync required.

At some point, almost every founder faces the same question.
Keep growing with your own revenue...
or raise capital and move faster.
Bootstrapping gives you:
full control
sustainable growth
freedom to build on your terms
Funding can give you:
speed
bigger opportunities
the ability to build a stronger team sooner
Neither path is easy.
Neither guarantees success.
What path are you choosing, and why?

The one where Skim stops impersonating a corpse.

A self-update could relaunch Skim into a window with a titlebar and nothing. Restarts didn't help. Reinstalling didn't help. Then, hours later, it just came back which is somehow more unsettling than staying broken.

Turns out nothing was broken. The whole UI was waiting on the first mailbox query, that query was politely queued behind the catch-up sync, and the app had no way to say "hang on, I'm reading" so it said nothing at all. For hours. In an empty window. Cool.

Fixed

Kaavya from Scribble again. If you caught my last two updates, you know we've been shipping fast. This one is the feature those two were building towards.

Quick context for anyone new: Scribble tracks which sources AI engines cite when they answer questions. After 7,000+ citations across ChatGPT, Perplexity, Gemini, Copilot, and Claude, one pattern would not go away: the sources are rarely brand websites. They're Reddit threads, Quora answers, LinkedIn posts, Medium pieces. People talking about brands, not brands talking about themselves.

Yesterday we recapped our past 3 months, and I would like to continue in accountability.

Whether you have personal goals or business/career goals, write them down in the comments and after a quarter, we will revisit what we have done. (And what we will push into Q4.) :D

Hey everyone,

I've been building a labelling tool, a desktop app (PyQt6) for capturing and annotating gesture datasets think of it as a companion tool for gesture recognition pipelines like Gesto, making it easier to collect, label, and export hand landmark data for training models.

I'm at a fork in the road on direction, and I'd love your input:

1. Open source it release it freely (currently GPL-3.0), let the community use it, contribute, and shape where it goes.

For almost a decade, I've been building my personal brands.

It started with a local Slovak community and, over the past ~4 years, expanded to an international audience.

Cursor Crane 1.1.0 expands keyboard-first automation on macOS with declarative workflows, multi-element selection, and improved scripting APIs.

Declarative workflows let you turn fixed sequences of built-in actions into reusable commands without writing JavaScript logic, state, or forms.
They are especially useful for turning hard-to-remember shortcuts into command sequences. For example, in Xcode, similar actions such as:

• Move Focus to Next Editor Pane

• Jump to Next Issue

• Jump to Next Change

can be turned into three workflow and mapped to commands "ne", "ni", and "nc".

We know this situation exists, but not many people are openly talking about it.

Being in a highly competitive entrepreneurial environment is challenging on many levels... not only in terms of sales and business growth, but also legal responsibilities, administration, and often handling most things independently, all while managing family and personal stuff.

Hey folks,

When I launched Pulse, the pitch was simple: the notch should do something. Today I shipped 1.1, biggest update yet, and it turns the island into a place you can put things and a remote for your meetings.

Here's what's new:

We're partnering with Vercel to bring Vercel Day back to the leaderboard

If you're building on Vercel, now is the time to get ready to launch. Schedule your product for June 16th, add the tag vercel-day to your launch, and you're in.

Winners from Vercel Day are confirmed. Top prize, a meeting with Vercel Ventures plus Startup Perks, goes to Nitrosend : it gives AI agents their own email inbox, so they can sign up for things and reply on your behalf instead of routing everything through yours.

Four more walk away with Vercel Startup Perks: Alert Grouping by DrDroid collapses a flood of monitoring alerts down to the ones actually worth waking someone up for. Paradigm turns any goal into a personalized, adaptive learning path. In Parallel MCP by gives every agent you run access to the same context instead of starting cold every time. Zro runs private inference for coding agents.

Congrats to all five teams. Go check out their launches and give them some love.

One of the most effective and affordable marketing strategies is WOM (word of mouth) getting other people to share your product and potentially spark curiosity or create a domino effect.

Over the past few days, several people:

have shared screenshots of my tool on social media,
sent me DMs saying they like it, or
left reviews on the Chrome Web Store.
I plan to use them in:
the landing page
 marketing materials (Chrome Web Store)
 possibly advertisement and "show off on socials"

Hey Product Hunt community,

With hundreds of products launching every single day, I ve been trying to understand the underlying architecture of homepage visibility and traffic distribution.

As a maker, when you launch a product, you often notice it doesn't always appear directly on the main featured feed for every visitor or on every device/browser.

This got me curious about how the platform balances fairness vs. algorithmic curation:

Hey everyone,

First of all, a huge thank you to this amazing community. Your support, curiosity, and willingness to try new things mean the world to us, and we're genuinely grateful to have you along on this journey.

When we started building @ProdShort , our first instinct was to make the product "ready" before showing it to anyone. Then we started seeing founders launching much earlier. Sometimes with nothing more than a landing page, just to see if people were interested enough to sign up... or even pay.

It completely changed the way we thought about validation. On one side, launching early gives you real feedback much faster. On the other, launching too early can make people leave before they see the real value of your product.

We're still not sure there's a perfect answer.

This is a quick demo video of Banquish. The official demo video is on the way!

THe official demo video is on the way!

People spend a lot of time preparing for a product launch, but after every campaign, they usually look back and think, "We could have done this better."

Not because they didn't prepare, but because there were things they simply didn't know beforehand.

The gap most auto-fix tools have

They tell you the bug is fixed. They don't show you. Our rule has always been: make the bug happen on real code, apply the fix, show it stops happening. The gap was we could only do that for bugs we'd scripted in advance. Anything unusual and the honest answer was "found it, fixed it, can't prove this one."

What we built

We taught FetchSandbox to write the reproduction itself, no pre-scripted test required.

Wanted to share some data before our own launch, since this took a while to pull together and might save someone else a bad launch day pick.

We pulled every featured product across all 7 days of the week and looked at the median points needed to break the top 5 and top 10 on each day.

Every business I have run had a version of this. A lead who asked a good question and never heard back from me. A client who mentioned something felt off during a slow week, and I told myself I would circle back once things calmed down. Things never calm down enough on their own. The follow-up does not disappear because I forgot about it, it disappears because nothing in my day ever forces it back to the top again.

Curious whether other people running something small have actually solved this, not with more willpower, just structurally. Does anything in your process bring the thing you meant to get back to, back in front of you at the right time, or does it just stay buried until the client brings it up themselves first.

The one where we stop blaming you for emails that render as a beautiful, pristine, completely empty rectangle. Turns out it was us. Well it was the sender's mailer. But we fixed it anyway.

Fixed

• Blank emails are no longer blank. Some mailers finish a message on the last base64 chunk and just walk away, never writing the closing --boundary--. The MIME parser reads that as "this part is broken", quietly demotes your email to an attachment, and hands us nothing to show. Skim now closes those dangling multiparts itself (innermost first, like a polite houseguest turning off the lights) and parses again. Your booking confirmations are back.

• No more phantom attachment. That mystery .bin full of raw base64 sitting under the empty email? It was your email. It has been returned to its rightful place.

• Bad parses no longer latch forever. The old code cached "I fetched this" and "there's genuinely nothing here" as the same thing, so a message that failed to parse once stayed broken until the heat death of the universe. Now Skim can tell the difference and gives previously-mangled messages one more honest attempt.

• Truly empty emails say so. If a message really has nothing to render, you get a plain line saying that instead of headers floating above a void. Silence is not a UI.

• Stale attachment files get cleaned up on refetch, instead of quietly squatting on your disk forever.

Everywhere

Some founders build to run the company for decades. Others already have an acquisition, a certain valuation, or even a type of buyer in mind.

I usually think more about building something that works first. But I can also see how the exit you want could change the company you build from day one.