User testing changed our roadmap, have you had to pivot after launch?
I'm building a website audit platform to help small to medium brands identify where their website is hurting visitor trust, engagement, and conversions. It's called you x you i. We released the MVP at the end of last year and did user testing. We have continued to involve users in our development process, and with their help, we've shipped updates and features every week.
Through the user testing, we identified a key audience that we didn't set out to target. It's led us to add an enterprise version of the tool to our long-term roadmap.
I'm curious, have you had to change directions after launching? If yes, what drove the decision, and how do you know it's the right choice?
https://www.youxyoui.io/
I built a film camera app for my girlfriend launching soon
Hey
I'm Boran, solo indie dev. I built an iPhone app called NiCam and I'm launching on Product Hunt in the next couple weeks.
The short story: my girlfriend kept saying she wanted one of those old digital cameras with the tiny screen on the back. I didn't really get it. Then on her birthday, her best friend showed up with a scratched iPhone 6 she'd dug out of a drawer. The whole night people kept passing it around taking photos with it. Bad sensor, slow shutter, weird colors. And every single person at that table was losing it over the pictures.
I went home thinking about that for weeks.
Hey Product Hunt 👋
We built BeaconKeel after seeing how slow and frustrating business insurance workflows still are for many companies.
A lot of the process still involves:
repetitive forms
manual underwriting
unclear carrier comparisons
slow back-and-forth communication
So we started building an AI-powered platform to help businesses compare insurance options faster and simplify underwriting workflows.
How I stopped wasting 10 hours on PRDs and started building (The "Product-Led" Way)
Hey everyone,
As a designer/founder, I used to hate writing PRDs. I'd spend hours in Google Docs, stressing over feature specs, user flows, and edge cases, only to realize I was overcomplicating things.
I realized that writing specs isn't the work building the product is.
So, I built a tool that takes a rough idea and automatically generates a dev-ready PRD in 5 minutes.
Compliance in Vibe coded Apps.
I analyzed hundreds of App Store rejections. The vibe coding era has made the problem dramatically worse.
I want to share something that's been genuinely painful to watch as someone who's spent months deep in App Store compliance data and as someone who has had past issues with compliance for vibe coded projects.
Vibe coding has changed everything about how fast you can build. Lovable hit $100M ARR in 8 months. Replit scaled from $2.8M to $150M ARR in under a year. 25% of Y Combinator's Winter 2025 cohort had codebases that were 95% AI-generated. The tools are incredible and the speed is real.
But the rejection rate hasn't changed. It's actually gotten worse.
50% of apps are rejected on first submission. 40% of all apps get rejected at least once.
We’re building an AI agent for M&A execution — from sourcing to signed deals
Hey Product Hunt
I m Florent, co-founder & Head of AI at Gravity Capital.
We built Gravity because M&A teams don t lack data. They lack a scalable way to turn data into qualified transactions.
Gravity is an AI agent for small and mid-cap M&A execution, helping deal teams with sourcing, scoring, qualified outreach, financial documentation, digital NDA workflows and pipeline follow-up.
Building Kognis made me realise
Building Kognis made me realise modern productivity isn t the real problem anymore
Over the last year I ve been building Kognis an AI-powered personal intelligence system focused on memory, recall and reducing mental overload.
What surprised me most is that people aren t really struggling with capturing information anymore.
We already have endless apps for:
Your AI is only as smart as what you type. We changed that.
Hey Product Hunt
I'm Edo, co-founding team member at Memoket. We're launching the Gem tomorrow and I wanted to share a bit about why we built it.
The hidden tax on every AI product: working around limits
When we launched oneinfer.ai five months ago, we set out to solve one problem, making AI infrastructure usable at scale through a unified inference layer, smart routing, and cost optimization.
What we didn't expect was how often a different problem would come up in every conversation with teams in production.
It wasn't the models. It wasn't even the infrastructure cost. It was the constant engineering tax of working around access, retry logic for rate limits, juggling multiple provider accounts, splitting prompts to fit token windows, building fallback chains for throughput ceilings, monitoring usage caps that change without warning.
Launching in ~1 hour: Why I built a 'Local-First' PDF merger 🛡️
Hi everyone!
In just about an hour, I m officially launching FDM AI PDF Merger on Product Hunt.
I noticed a recurring frustration in my own workflow: every time I needed to merge simple PDF documents, I was forced to upload them to a third-party server. It felt unnecessary, and frankly, risky for sensitive files.
I decided to build a better way. FDM AI PDF Merger processes your documents completely locally in your browser.