Question for folks documenting APIs, especially with docs in a separate repo from the code: how do you find out about changes before a customer does?

The big features usually reach us. What slips is side effects: a PR about a new filter that also lowers the max page size from 100 to 50, a default that flips, a new error code, a renamed webhook field. One line in a diff that's mostly about something else.

We built a tool that people said looked great, felt smooth, and solved a neat problem. People signed up, paid for the tier, and then quietly drifted away. No angry emails, just silent cancellations.

That s when it hit us: we built a vitamin, not a painkiller. It was nice to have but when budgets got tight or schedules got busy, it was the first thing to get dropped from the daily routine.

If your product isn't tied to an urgent daily workflow, how do you pivot before churn drains your MRR?

I have so many ideas. So many. They arrive at random times, usually when I'm supposed to be doing something else, and they all sound incredible.

And then I look at my bank account and remember I have a budget. And the ideas are not free. They cost time, money, energy, all the things I don't have unlimited amounts of.

Happy #StarWarsDay!
What are the most inspiring products that don't just support dark mode but default to it?
My collection includes:

• Linear

• Liveblocks

• Raycast

• Supabase

• v0 by Vercel

Over to you!
Oh and if you enjoy dark themes, make sure to star this repo full of hand-picked resources, tools, and examples to build awesome products in dark mode.
#MayThe4thBeWithYou

We ve been thinking about whether a free plan makes sense especially when the product already has some value without the paid features. It feels like removing the payment barrier could bring more people in but it might also attract a lot of users who never have any intention of paying. The tricky part seems to be finding the right limit. If the free version is too useful there s no reason to upgrade but if it s too restricted people may leave before they understand the product. For those who started with a free plan what actually worked for you usage limits feature restrictions or something else?

We re talking to mobile app founders about how they stay on top of user feedback. With reviews spread across Google Play, the App Store, and even CRM tools, it can feel like a full-time job just to know what s going on.

I m curious:

• Do you personally check reviews daily, or is it more ad hoc?

• How do you currently track and respond to reviews across platforms?

• Are you using any tools or custom setups to catch emerging issues early?

• What s been the hardest part of staying proactive with reviews (without burning hours every day)?

Default image generation settings always default to the exact same boring composition and lighting.

When we were making marketing banners every batch looked like it came from the exact same template. Adding random focal lengths and lighting styles via script sounds like a smart fix to force some variety.

Have you tried playing with negative prompts as well or do you mostly focus on randomizing the main input parameters?

Let s be honest: AI is getting eerily good at sounding human. It can craft hyper-personalized content and emails, and handle entire conversations. It s also made sales outreach noisier and eroded trust in once-reliable channels like email, chat, and even voice and crazy enough, video. But it s so seductive and fast. It s learning and adapting faster than ever. And it s not going to stop: in Q1, it already represented the majority share of global venture capital funding.

But one thing AI still can t fabricate is a real, trusted human relationship. These can t be made up or scaled with prompts. They re built through shared experiences, mutual trust, and real-world context.

And yet, in today s business world, precious human connections are slipping through the cracks. They re buried in inboxes, lost in forgotten LinkedIn threads, siloed in the minds of your team and stakeholders. The right lead, investor, or candidate is often just one intro away, hidden in the network you already have. LinkedIn is great if you re an individual building an audience but it fails to unlock the collective relationship capital of an entire company.

For six months our users kept asking for an export to PDF option. We changed our plans. We spent three weeks building the export feature. To keep the dashboard simple we put the button inside an advanced settings menu.

We checked the analytics for two months. Out of 4000 users three people clicked the export button.

The export feature turned out to be unnecessary, for users. They only wanted to feel safe knowing their data could leave if they needed it. They never actually used the export. We spent three weeks building a psychological safety net, not a feature.

Has anyone else ever built an export feature just to reassure users? something they thought people wanted. No one ever touched the export.

"Attention is loud and revenue is quiet" is such a spot-on way to put it.

We often fall in love with the launch hype on Product Hunt or Twitter, but that spike dies down fast. I had a tiny utility script I built in a weekend and completely forgot about.