What I Learned Building Interfaces I Actually Wanted To Use

Early in my career as a builder, I was drawn to the "impressive."

I wanted interfaces that felt powerful. This usually meant dense dashboards, high-contrast layouts, complex animations, and a feeling of technical sophistication. I wanted to see the machine working.

But after living with the systems I built—using them day after day, year after year—my perspective began to shift. I realized that the interfaces I actually enjoyed returning to were rarely the ones that impressed me initially.

Many modern interfaces are designed for the first five minutes of usage. They optimize for "engagement" and visual novelty. They compete for your attention through:

• Interaction Fatigue: Subtle but constant animations that drain cognitive energy.
• Visual Competition: Every element on the page fighting to be the most important.
• Information Density: Cramming features into every available pixel to signal "value."

When you use an interface like this for an hour, you feel tired. When you use it for a month, you start to resent it. Stimulation is not the same as utility.

As I began building tools for my own daily workflows, I found myself stripping things away. I started prioritizing:

• Cinematic Whitespace: Giving content room to breathe, which in turn gives the user room to think.
• Restrained Hierarchy: Being incredibly selective about what is allowed to be prominent.
• Intentional Motion: Using animation only to provide context, never just for flair.

I stopped trying to make my interfaces look "smart" and started trying to make them feel calm. A calm interface is one that respects your attention. It doesn't demand validation. It doesn't perform.

There is a fundamental difference between an interface you "visit" and one you "live in."

Systems that age well are low-fatigue environments. They prioritize familiarity and comfort over constant change. They feel like a well-organized studio rather than a busy airport. By reducing the cognitive friction of every interaction, we create spaces that support deep thinking instead of constant distraction.

A tool can be functional without being enjoyable. But the systems that truly stick—the ones that become part of a sustainable practice—are those that provide operational comfort.

This isn't about aesthetics alone. It's about the "interaction tone." How does the interface respond? How does it handle errors? How does it guide you through a complex task? When an interface feels like a partner rather than a demanding assistant, the experience of using it changes entirely.

This realization led to the modular, editorial architecture of this website. I moved away from "one-off" features and toward reusable systems that prioritize readability and pacing.

I learned to prefer:

• Quiet Interactions: Simple buttons that do one thing well.
• Systematic Restraint: Not adding a feature just because I can build it.
• Focus-First Design: Ensuring the primary content is always the hero of the page.

The most valuable thing I learned building interfaces for myself is that simplicity is not a lack of features—it is a high level of clarity.

Sustainable interface design is about building systems that can fade into the background. Technology should be a quiet supporter of your focus, not a competitor for it. As we build more "intelligent" tools, the need for this kind of restraint will only grow.

I’m no longer trying to build the most impressive interface. I’m trying to build the one I’ll still want to use tomorrow.