One thing I keep noticing is how easy it is to build something that is technically helpful and emotionally noisy.
That is not a small problem. For the kind of product I am trying to make, it is the problem.
A helpful product can still feel emotionally noisy
A fair amount of the work ended up around breathing support, visual rhythm, session flows, and the general feel of interaction. Not because I wanted to make something impressive, but because pacing matters. The way a tool moves, prompts, and holds attention changes whether it feels supportive or demanding.
I think people underestimate that.
A product can have the right intention and still ask too much. Too many decisions. Too much motion. Too much emphasis. Too much of that subtle feeling that the software is performing usefulness instead of quietly being useful.
Interaction tone matters as much as capability
So some of the work became less about capability and more about tone in the broadest sense of the word. Not writing tone. Interaction tone. Visual tone. The feeling of whether something gives you space or crowds you.
What I was trying to make was not just a feature. It was a kind of steadiness.
That does not mean making everything soft or vague. It means making choices that lower friction without lowering clarity. It means shaping the experience so it can meet someone who may already be overstimulated, tired, uncomfortable, or halfway to giving up.
This part of the work is easy to undersell because it does not always show up as a headline feature.
Support has to stay usable when someone is already overwhelmed
But I think it matters a lot.
If Caligo Relief is going to earn a place in real life, it cannot just be useful in principle. It has to feel usable in the moments when usefulness is hardest to reach.