What made you stop trusting a demo?
Genuinely curious, because I am on the making side of this and I want to know what we are getting wrong.
We build real-time face and voice models, so demos are most of how anyone judges us. The tell I have become allergic to in our own material is the cut. If a video edits right at the moment the product would have had to respond, the edit is doing the work the product could not. Anyone who has built something real-time spots it immediately, because you know exactly what got removed.
The other one is a demo where nothing goes wrong. Real usage has friction, so a flawless run starts to read as rehearsed rather than good.
So what is yours? The moment in a demo where you quietly stopped believing it.
First-time maker: 3 questions before our launch (expectations, anti-spam, audiences)
Hey PH!
I m Roy, one of the makers of Surf a research copilot for crypto folks. Super excited for our first launch.
I ve read a ton of guides but would love real advice from makers:
1. Expectations / forecasting
Do you usually have a sense of how many participants will show up on launch day or a rough range of upvotes/comments? Any rules of thumb you ve used (e.g., % of Teaser followers who visit, comment to upvote ratios, or targets you set for the first 4 hours)?
What's one bug that took way longer to find than it should have?
Working on a Gmail tracking extension (Chrome + Next.js backend) right now, and just spent way too long chasing a notification that silently never fired turned out the message type was defined but nothing ever triggered it. Classic "the code looks right" trap
What do you think is the biggest barrier to adopting AI-powered UAVs across industries?
Over the past few years, I've noticed AI-powered UAVs evolving from simple aerial cameras into intelligent systems that can inspect infrastructure, monitor crops, generate maps, detect anomalies, and even make decisions during autonomous flights.
The technology seems ready for much broader adoption, yet many industries still rely on traditional workflows.
From what I've seen, the potential benefits include:
Faster inspections with fewer safety risks
Better data collection for decision-making
Reduced operational costs through automation
More frequent monitoring of assets and infrastructure
Improved environmental and agricultural analysis
AI transcription and GDPR: why European teams can't just use the best US tools
I run explicare, a GDPR-compliant transcription tool in Germany, so this tension is basically my day job. I want to open it up as a discussion rather than push a conclusion.
Here's the practical reality for a European company. Most of the best speech and AI services run on US infrastructure. The moment audio, transcripts, or personal data leave the EU and land on a US server, you're in GDPR territory: lawful basis, transfer mechanism, sub-processors, all of it. For many of our enterprise and public-sector users, that alone rules out half the market before accuracy or price even come up.
The legal ground keeps moving, too. The EU-US Data Privacy Framework is still valid today, but a French challenge is now pending at the European Court of Justice, and a US Supreme Court ruling this June, plus the oversight board (PCLOB) losing quorum, have weakened the exact safeguards the framework was built on. A "Schrems III" case is widely expected. If you plan a product roadmap around that, you're building on sand.
Credits don't confuse people, hiding the per-action cost does
We went with credits because it's the only model that survives routing across a dozen models with different per-token costs. Seats don't work when one user's afternoon costs more than another user's month.
What broke wasn't the price, it was that people wouldn't press the button. If you can't tell whether a run costs 1 credit or 40, not running it is the safe move, and a tool nobody runs churns quietly. The fix was putting the cost of that specific action next to the button, before it happens, not on a pricing page.
What's the one thing you still won't hand to an agent, even now?
Mine's anything touching payments or auth. Not because the code would be wrong, because when it's wrong there's no diff to review before it already happened, a webhook fires and the consequence is already out the door.
Curious where other solo builders draw that line, since "just review the diff" stops being the safety net past a certain kind of change.
The value of interrupted workflows
One thing I ve learned from building workflow tools: a task left halfway through is not the same as one that was never started. It can reveal where time, context, or a handoff broke down. Treating both states as simply incomplete hides the useful part.
How have you designed workflows to learn from interruptions without adding reporting burden for users?
Most brands get "premium" packaging wrong. Here's the actual difference.
Been working in B2B brand growth for a while now, and one pattern keeps showing up: founders think "premium" means adding more, more foil stamping, more inserts, more finishes.
But the brands that actually feel premium usually do less, just with more precision. A clean die cut, one deliberate material choice, consistent color across every touchpoint. That restraint is what reads as expensive, not the extra decoration.
Curious what others here think. If you've built or scaled a brand, what's one packaging or presentation decision that actually moved the needle for how premium you felt to customers? And what's one thing you tried that looked good on paper but didn't land?
Should I add more pages to my viewer app, or keep it ultra-simple?
Hi Product Hunt community,
I m a solo developer who recently passed the production review for a mobile document viewer app.
Honestly, I built this out of pure personal frustration. I just wanted a lightweight, lightning-fast viewer to read my files (PDF, PPTX, DOCS, HWPX) without being bombarded by annoying ads. Personally, I am very satisfied with how it turned out.
But now, I m hitting a wall of self-doubt.