DENIS BRODLIN

I've been spending more time exploring what other indie developers and founders are building, and honestly, some of the most interesting products I've found aren't the ones getting thousands of upvotes.

I'll start!

We're building Dots, a macOS app that turns your Mac's notch into a customizable workspace. Instead of just music controls and notifications, you can bring in your own apps, websites, shortcuts, and even developer tools.

We re all builders here, which usually means at some point we looked at something clunky, slow, or frustrating and thought, there has to be a better way. Most products don t start with a grand vision; they start with irritation, curiosity, or firsthand pain.

I d love to learn more about how others here have navigated that journey:

How did you uncover the problem you decided to work on?
What signals told you this problem was worth solving?
How did you validate (if at all) whether people would actually pay for a solution?
Has your product stayed true to the original problem, or did it evolve into something different?
What surprised you the most along the way?