Connect with the Product Hunt community

At Product Hunt, we re on a mission to help builders find users and help users find the best new products.

We ve been at it for over a decade, and we ve accumulated a ton of data, but we ve rarely shared it with the outside world. Until now.

Earlier this year, we introduced Navi as a new interface to the Parsewise Data Engine. Instead of learning the platform first, users could begin with the questions they wanted answered and the data sitting in their documents.

Navi can now build apps around a project s extracted data, inspect the decisions behind an extraction, transcribe dictated prompts, and use screenshots as context.

Because building products has become much more accessible thanks to AI, the bar has had to rise a bit, or at least the expectations have become stricter.

I built my own tool  SafeLimit, but personally, I wouldn t launch it on Product Hunt yet because it s still very basic and doesn t even have a website.

Road to 1,000,000 @Votap users - Day 84 | Current: 1470

And again the pricing plan =D

Let s discuss the serious side of product growth.

At first, it seems easy: set some prices, create a few plans, and start selling your product.

But when the time actually comes, a ton of questions appear...

In every community, we naturally find people we love to communicate with, interact with, or simply follow.

From my very first day on Product Hunt, some people became little lighthouses for me here.

The moment I signed up, I noticed @busmark_w_nika and her threads. She became one of those people I always enjoy following here.

Then came @amraniyasser and @bengeekly .
And that was only my first day =D

Most Lovable apps I've seen ship with integrations that were never actually run end to end.

What's usually happening?

The Stripe webhook is wired, the retry logic is there, but nobody ran a confirm capture webhook fire sequence before going live. Testing is either skipped or scripted in isolation against mocked responses that don't reflect real API behavior.

you're moving fast, you've shipped login, it works, users are in. and then an enterprise prospect shows up and the first thing they ask is 'do you support SSO?' and suddenly the thing you built in a weekend is blocking a six-figure deal.

but SSO is usually just the first question. after that comes the security questionnaire. then someone asks about audit logs. then their IT team wants to know how they'll provision and deprovision users at scale. then legal asks about data residency.

For solo makers, wearing every hat is almost unavoidable - developer, marketer, support, product and often designer too.

AI makes this even easier now. You can generate UI pretty quickly, but a lot of products end up relying on consistent, polished AI-generated solutions rather than something truly unique or thoughtfully designed for their specific product.

So I m curious:

Do you design the UI/UX yourself when building solo?

Making a product is one big challenge. But shifting your mindset from building to marketing it might be an even bigger one.
As makers, we spend so much time improving the product. Then comes the question: How do we get people to discover it - and ultimately turn that attention into real customers and sales?
I'm not sure traditional approaches like email marketing and constantly posting on social media are enough anymore. The way people discover products is changing.
So I'm curious:

How do you approach marketing your product?
And for the marketers here:
What would you consider a modern marketing approach in 2026-2027? What would you advise an early-stage founder to focus on?
I'd love to hear different perspectives...

Meta just launched Muse, its personal AI agent. AI agents have been everywhere lately, so seeing Meta enter the space was probably just a matter of time. But Meta has one huge advantage: distribution.

WhatsApp, Instagram, Facebook they already have billions of users.

Do you think Meta can become a serious player in AI agents?

Not a complaint about pricing. A real question I could not answer until I went looking.

The intuition is that a better model needs fewer attempts, so a job should get cheaper. My bill kept going the other way, and the price per token had gone down, not up.

The answer turned out to be in the docs. Reasoning models produce a block of internal work before they answer, and OpenAI's guide says it plainly: those tokens are "not visible via the API" but are "billed as output tokens". Anywhere from a few hundred to tens of thousands of them. Anthropic bills the same way.

I m not really a person who likes sharing my everyday life online =)
That s one of the reasons I m really happy to be part of the Product Hunt community.

I like being able to stay in touch with like-minded people and have everyday conversations about things we re building, learning, and interested in.
But I understand that social media is a big part of today s lifestyle, and it s absolutely great that it gives people a way to connect, share, and find each other.

So, I m curious:

Do you have social media as a maker?

@Supabase. @Langflow. @Nuxt. @Plane. @Mastra.

600,000+ GitHub stars between them, and CodeRabbit reviews it all, for free.

Two months ago I asked here how people stay aware of what their agents are doing, and @getosmo replied with something that has been quietly rearranging my roadmap since.

I had been treating "can you undo it" as the line for when an agent should stop and ask. He took that apart. Irreversibility over-fires and under-fires, he said. It over-fires on things that cannot be undone but that nobody cares about, like the agent writing a log line. It under-fires on the ones that really hurt: a mass email to 50k users, or a migration you can only roll back after downtime. "Reversible on paper, ruinous in practice."

When you're a first-time founder/maker, and you're the only person using your own product, you probably overlook important things. That's why you need to test the product with as many people as possible.

The problem is that time is limited. You have to decide not only how many people will test it, but also who those people should be.

Before Harden: approve every action.

After Harden: let it run.

We launched CoWork, a mobile app testing solution, on PH a while back and got a lot of useful feedback. Some of the most interesting comments came from developers who wanted to test their mobile apps before the merge, not after.

So we built QApilot MCP, that lets Claude, Cursor or Codex drive a real Android device. It launches Saturday.

Local Panel has been live for over three months and we now have over 100 users thank you to everyone for that .

For those who aren t familiar with it, Local Panel is a desktop app for developers who are fed up with the hassle of setting up their development environment. Windows, Mac, Linux hosts, databases, SSL, project management, all in one place. No web app, no browser tabs, no it works on my machine excuses.

I run multi-client creative work (video, ad scripts, photography) and feedback always ends up scattered across WhatsApp, email, and Figma comments. Half the time nobody's sure which version actually got approved.
Curious how others handle this, especially freelancers and small agencies juggling several clients at once.
Is your bottleneck getting clear feedback, keeping versions straight, or something else entirely?

If you have two minutes: make one snipplet, then tell me where you almost gave up. What was confusing, what looked bad, what would stop you from coming back.

Yes, you have to make an account first... that's one of the things I want roasted.

From 1 October, leaving Apple In-App Purchase drops a Small Business Program developer from 15% to 10% in the EU. On a 4.99 euro subscription, a processor's fixed per-transaction fee can eat most of that on its own - and your choice locks for 12 months.

Apple updated the Developer Program License Agreement on 18 August, and the new EU business terms go into effect on 1 October. The coverage I've read frames it as Apple finally opening up. That's true in a structural sense and mostly irrelevant to anyone running a small subscription app, because the interesting question isn't whether you can leave Apple's payment system. It's whether the arithmetic works. For most of us it doesn't, and it's worth being able to say why rather than just having a feeling about it.

Not another chatbot builder. Not another connect your API to an LLM tool.
I mean the boring, painful infrastructure that you don't want to build every time you ship an AI agent.

Things like:

• Agent orchestration

• RAG

• 900+ integrations

• Evaluations

• Observability & analytics

• LLMOps

• Payments & usage tracking

Basically:

New from Timmy: a 30-second look at real creative work, with an ElevenLabs voice-over.

Watch the 30-second narrated demo

Living Canopy starts with editable SVG artwork and becomes native Rive animation through MCP: an eight-second loop, 23 moving groups, adjustable speed and strength, and 240 delivered frames.

The result stays connected to its native file, rendered frames and recorded loop/delivery checks. We ve also organized 102 template families into base templates and project variations.