I am trying to do something a little bonkers - I want to build an app when I am a bit of a technophobe! I am a product designer - so it's not entirely crazy but social media, online forums is all really alien to me. I'm looking to put the feelers out there to understand the demand for the idea - any tips or tricks?
The vague idea - without giving the game away....
People are incredible at tracking workouts, steps, sleep, macros

but somehow still stare at a single mug in the sink like it s a moral dilemma.

I m exploring an idea around why everyday maintenance tasks feel heavier than they are, and how the same psychology that keeps people hooked on fitness tracking might work for real-world chores.

Hey PH - today we re rolling out configurable proxies for API-based execution in BrowserBook.

One of the most common reasons browser automations fail in production is bot detection. Captchas, IP reputation issues, geo restrictions, and rate limits can derail even solid Playwright workflows once you start running them at scale.

One of the coolest parts of my job is getting a front-row seat to how @marianaprazeres thinks about AI.
Memory feels table stakes in AI right now. But for @Meet-Ting, it s not just a log of the past - it s a living system that shapes how people schedule, work, and want to spend their week.
It s not just logistics - it s patterns around energy, priorities, and relationships over time.

Here are a few things we learned while designing and testing agent memory in production:

Hey everyoby thank you so much for helping me out in this launch!

Let s use this forum to discuss anything related to anonity and your experience so far!

Huge thanks for the love, sharp questions, and thoughtful feedback. For us this wasn t a threw it together in a month launch. Mujo AI is years of work by people who believe product cards for marketplaces can be fast, beautiful, and scalable.

Under the hood it s agents, pipelines, our own tables and templates a lot of machinery. We worked hard so all that complexity feels like a simple Generate button and the output is ready for production.

The best reviewers don t act like gatekeepers.
They act like collaborators :

asking questions,
surfacing alternatives,
and making intent explicit.

Guys, over the past 3.5 months, we encountered one significant problem at ProblemHunt:

1. Many contributors who shared problems aren't very motivated to provide feedback to developers for various reasons. Even among those willing to give feedback, not everyone agrees to work with more than 3 5 different developers (for context: currently, one contributor receives messages from 7 15 people on average). And without quality feedback, it s difficult to clarify all the details and build a great product.

2. To solve this problem, we talked to some of the contributors and found out: they are willing to provide feedback much more actively if they can receive 1% equity in the future startup. According to them, this would give them strong motivation to help with advice and actively participate in testing.

3. Therefore, we decided to run an experiment over the next few months. Now, in the problem submission form, contributors can optionally indicate that they want to receive 1% equity in the future startup. And we will mention this in the publication for you.

4. By the way, if you currently have a problem and also want to get 1% equity in a future startup, you can seize this opportunity right now on ProblemHunt!