Connect with the Product Hunt community

Road to 1,000,000 Votap users - Day 78 | Current: 1466

Driven just finished its first Product Hunt launch, and one of the most valuable parts was reading the comments.

Not just the compliments, but the questions.

A few themes stood out:

1. Trust comes before automation

Improved

• Find outgoing conversations faster with the new Sent filter in All Emails.

• One-time codes are detected more precisely and shown directly in email summaries.

• Notifications now use readable sender names and skip messages you ve already read or archived.

• Follow long conversations more easily with better collapsing of quoted replies, including Outlook threads.

• Enjoy more reliable email categorization when using local AI.

• Archived emails now stay out of automatic processing.

• Empty email views now clearly invite you to select a message.

Fixed

• Draft messages no longer show actions intended for regular email links.

Every review cycle, the same ritual. Open a blank doc. Try to reconstruct half a year.

What you remember: the big feature, the launch, the thing your manager already knows about.

What you don't remember: the production incident you took at 11pm in March. The afternoon you lost to a bug that turned out to be a dependency version. The teammate you unblocked twice a week for a month. The investigation that concluded "not a real problem," which was a genuinely valuable finding and produced no artifact. The small fix that saved everyone twenty minutes a day forever.

None of that is on a board. All of it is why the sprint went the way it did.

Introducing DunSocial CLI.
Why should posting the same update everywhere take eight logins? Now I run one command from my terminal & it goes out across X, LinkedIn, Bluesky, Threads, Reddit, Pinterest, Instagram, and YouTube.
Built for people who live in the terminal.

dunsocial

China and California both moved to rein in AI companion apps this month and the whole debate hinges on a question most builders never ask: what happens when the user closes your app?

Two weeks ago, on July 15, China rolled out rules specifically aimed at curbing emotional dependence on AI companion bots. Platforms now have to detect distress, intervene in a crisis, cap excessive use, and hand users real control over their data. California, meanwhile, became the first U.S. state to pass legislation regulating companion chatbots, forcing developers to build in actual safety protocols.

I want to thank everyone who took time out of their day to try Meridian, support our launch, and share feedback. Every upvote, comment, and message helped make this possible.

The day is not over yet. We would love your continued support and honest feedback as we work to keep Meridian at the top. Please try it and tell us what you think.

Product Hunt: https://www.producthunt.com/prod...

The answer depends on what you want to achieve.

• If you want to stay top of mind for a constantly growing audience and increase visibility, post every day.

• If you want to amplify your launch, focus on the period before, during, and after the launch.

  Before the launch, I would start with enough time in advance, around one month before, and I would personally post approximately (at least) twice a week.

• But I think that in general, if you want to be visible within the forums, twice a week is bearable.

A developer who finishes a task in two hours through experience, automation, or better tooling can appear less hardworking than someone who takes the entire day. The reward for being efficient is often more work, while long hours remain the most visible signal of effort.

This creates the wrong incentive. People learn to look busy instead of improving how they work.

We re building Meridian to make the work behind outcomes visible, from commits and pull requests to Jira updates and meetings, without requiring developers to document everything manually. It s fully open source and free for individuals.

We re currently #1 on Product Hunt, which suggests this problem resonates with more people than we expected.

I added playable DOOM to the internet's shared Windows XP desktop I launched [publicdesktop.lol]

(https://publicdesktop.lol/) as a tiny internet experiment: one shared Windows XP-style desktop where anyone can claim a permanent spot.

I've caught myself doing this more often than I'd like. Especially when I'm using AI to think through an important decision.

Ask ChatGPT something important. Get an answer. Not completely convinced, so ask Claude. Maybe try Gemini too.

I keep coming back to this idea: vibe code is basically instant legacy code.

Not because AI-generated code is necessarily bad, but because it often puts us in a familiar situation: the system works, yet no one fully understands how it works. That makes me wonder whether some of the most useful techniques for vibe coding are actually techniques we already use for legacy systems. For example:

• Snapshot / approval tests: capture the current output and require explicit approval when it changes.

• Characterization tests: describe what the system actually does today, regardless of what it was originally intended to do.

• Golden master tests: run known inputs through the system and compare the results with a trusted baseline.

• Contract test: protect the boundaries between components, services, APIs, events, and data stores.

• Differential testing: compare two implementations and detect where their behavior diverges.

• Test carving: observe a larger execution and extract smaller, focused regression tests from it.

Everyone says to test demand before you build. We didn t. We built the product first, like a lot of people do, and only afterward found a fast way to test the part we d skipped.

What we re testing now isn t really the idea - it s the positioning: Does someone landing on our page understand what the product is? Does the offer make sense? Does the pricing feel right?
We use a paid research panel (Prolific, though there are others like Wynter, PickFu and Lyssna) to put the page in front of people who match our audience. They read it and answer a short questionnaire: What do you think this does? Do you understand it? Does the price seem fair? You pick the audience, they review, you pay per response. A few hours to prepare, results back the same day.

It's been most useful for catching where people misread the offer - something our existing users can t really tell us, because they already understood it well enough to sign up. We ll use this approach for landing page changes from now on, and we ll run these tests before building the next thing rather than after.

How do you test whether people understand your product or your idea before you commit to it?

Hello guys,

this is not a post like others, a post to ask some feedback or to promote my products, idc if it gets 0 upvotes or anything.

I really want to externalize and i love product hunt because everyone is so supportive not like other socials /:

Think about the last product that genuinely impressed you.

Was it the description?

The demo?

A video?

Welcome to Olostep. We're building the infrastructure AI agents need to do real work on the web.

The web is the backbone of every business and the home of humanity's collective knowledge. Humans browsed it manually for decades. Now Agents are knocking on the door.

In late 2025, with improvements in AI models, we entered an era where software stopped following instructions and started thinking. We shifted from an instruction-based world to an intent-based one. The agentic era. That shift breaks a lot of infrastructure that quietly assumed a human in the loop: email, payments, identity, search.

Search asked you to do the rest. You typed a query, got some links back, and then opened the tabs, read, compared, and pieced it together yourself. In an agentic search world, what comes back isn't links, and isn't an answer. It's the work, done: hundreds of sources searched, pages read, fields extracted, conflicts resolved, output structured and delivered.
The web's second user is arriving, at machine scale. Everything it needs to work has to be built again. The data infrastructure is where we start. We are starting with a series of APIs to search, scrape, crawl, map, monitor, and turn the web into clean data for AI

We re excited to announce that Forgeon is officially on Kickstarter!

Our campaign is currently in pre-launch, and we re getting ready for something big.

Forgeon is a platform for creating, publishing, and experiencing interactive books - with branching stories, choices, RPG mechanics, characters, multiple endings, and much more.

We ve got a lot of exciting things planned for the Kickstarter campaign, and we can t wait to show you what we ve been working on.

MinkNote is joining Indie App Sales from July 28 to July 30.

If you've been thinking about trying it, you can get 50% off your first 3 months with code INDIEAPPSALES2026.

Direct link

MinkNote is a privacy-friendly, local-first notes app for Mac, built around files you own.

Until this release there were two doors: Homebrew, or go install. Both fine, both assuming you wanted a binary on your machine which is not what you want when you're inside gh already, or writing a CI step, or on a box you'll throw away in ten minutes.

New here, first post. I've been browsing for months without an account.

I've got a decent pile of free tools I use regularly and a couple I pay for. What I can never figure out is the line between "this is fine free" and "okay I'll actually pay." Sometimes the free version does 90% of what I need and I still
upgrade for the last 10%. Other times I'll tolerate an annoying limitation for years rather than pay five bucks.

I don't think my logic is consistent at all. Curious how other people decide. Is there a moment where it clicks, or is it just vibes?

First, the part that matters most: Thank You.

When I launched Pulse here, genuinely didn't know it would make it #10 globally on Product Hunt.

You downloaded it, broke it, told me exactly what felt right and what needed work, and sent me bug reports at 2am. Every single one of those shaped the app.

PH Community! Sooo we just hit 50,000 users in 14 months

Pretty Prompt wouldn't be without Product Hunt.

We ve spent the past two years rebuilding Dash to Cart around a question we kept coming back to.

Marketplaces are great at discovery and traffic, but merchants give up some control over the customer relationship.

First post here. Been browsing Product Hunt for a while without an account and finally made one.

I keep noticing apps adding an AI button to something that didn't need one. A calendar app with "AI scheduling." A to-do list with "AI prioritization." A notes app with "AI summaries." Most of the time I poke at it once, it does something vaguely fine, and then I go back to using the app exactly the way I did before. The button just sits there.

I'm not against AI features. Some of them are genuinely good and I use them. But there's a difference between a tool that was built around it and a tool that stuck a chat box on top because it was trendy. From the listing alone, those two look identical.

Curious if anyone else feels this. What's an AI feature you actually use regularly, versus one you tried once and forgot about? And does a listing mentioning AI make you more likely to try something, or less at this point?

we just launched a product video on linkedin, check it out here: https://lnkd.in/p/ewB7ASgp