Habitus

The project started from research rather than from an app idea. I ran a survey about personal boundaries — how often people agree to things they do not actually want to do.

The answers pointed at the same thing again and again. On an average day a person says yes against their own will three or four times, and by the evening they cannot recall a single one of those moments. People were not failing to hold their boundaries because they lacked resolve. They were failing to notice that a boundary had been crossed at all.

That reframed the brief. The product could not be a self-improvement tool. It had to be an instrument of attention — something that helps you catch the moment while it is still happening.

The survey finding set the hard constraint: whatever I designed had to work in the few seconds while the moment is still fresh. Anything that asked for a category, a rating, or a written note would lose it.

That ruled out the standard habit-tracker vocabulary. Streaks, charts, and completion rates turn paying attention to yourself into one more obligation, and they punish you on the days you gave in — precisely the days the app would matter most. I did not want a number telling someone they had failed at holding their own boundaries.

So I looked for a representation that could show a state without scoring it. I arrived at a single organic form that responds to your entries: it holds its shape while you are listening to yourself and loses definition when you keep giving in. It reads at a glance, it carries no good or bad value, and there is nothing in it to game.

The app is built around one action. Catch the moment is a single button on the main screen — you tap it when it happens, and that is the entire interaction. No categories, no rating, no mandatory note.

The state of your boundaries is shown as a living form instead of a graph: right now you hold the line more often than you give in, and the shape says so. Touching the form makes it respond, which turns checking in into contact rather than reporting.

The interface is dark and close to empty on purpose. It opens in the middle of a real situation, often with people around, so it should not demand attention or look like something being hidden. Entries stay on the device only — this is not material anyone wants sitting on someone else's server.

Habitus remained a prototype. It was finished as an interactive Figma prototype covering the full flow and was not taken into development.

The decision I would keep is the refusal to add a metric. Removing streaks and scores is what made the concept hold together — a tool meant to help you notice something cannot grade you on it at the same time.

The open question is whether the form reads to other people the way it reads to me. That needs real users moving through the prototype, and it is the first thing I would do if the project continued.