← Back to all insights
Design

Design should feel like home

Your color palette is not decoration. It is the atmosphere your product lives in.

Angus Uelsmann Angus Uelsmann 4 min read
Consistent color, spacing and motion make a product feel calm enough to trust.
AI-generated image

Good design is not about making every screen look impressive. It is about making every screen feel connected. The same rhythm. The same level of calm. The same standards repeated often enough that users stop noticing the interface and start trusting the product.

  • design
  • systems
  • color
  • trust

Interfaces should guide, not negotiate.

Core claim

  • Design is not about individual screens, but about consistency across them.
  • Inconsistency creates friction, even when users cannot explain it.
  • Coherent systems reduce cognitive load and build trust.

The problem with random

A lot of products feel assembled instead of designed.

One page uses a purple accent. The next uses blue.

Buttons have different hover states. Cards use different spacing. The modal feels like it belongs to another company.

Most users will never describe this out loud. They will just feel that something is off.

Every inconsistency becomes a small decision the user has to resolve.

That feeling matters more than people think.

A palette is a system

Many people treat color like decoration.

Pick a few nice shades. Apply them. Move on.

Good defaults are invisible decisions.

But in a real product, a palette has jobs to do.

  • Background — sets the mood.
  • Surface — cards, panels, inputs.
  • Surface 2 — secondary layers, hover fills, code areas.
  • Border — separation without noise.
  • Text — clarity first.
  • Muted text — metadata and secondary hierarchy.
  • Accent — where attention should go.
  • Accent dim — softer emphasis.
  • Accent glow — depth and energy.

When each token has a clear role, decisions get easier. The interface starts to feel coherent because it is coherent.

Design system test

If a color, spacing value or motion curve has no job, it becomes noise. A system should explain why each piece exists.

Years of refinement

I did not build my palette in one sitting.

I changed it over years. Sometimes dramatically. Sometimes by one percent.

The dark background needed to feel technical, but not cold. Pure black felt harsh. Flat grey felt lifeless. A subtle violet undertone solved both.

The accent color took the longest. Too bright felt cheap. Too soft disappeared. Too saturated felt noisy.

The current lavender sits in the middle: visible, calm, confident.

Even muted text colors took time. If secondary text is too weak, usability suffers. If it is too strong, hierarchy collapses.

Small inconsistencies accumulate. So does refinement.

The details nobody mentions

Some of the most important design work happens in places nobody talks about.

The text selection color matches the palette instead of using the browser default blue.

The scrollbar is styled to belong to the interface.

Hover states move with the same timing and same energy across buttons, links and cards.

Theme switching is not a hard flash. It expands outward from the toggle like a ripple.

Interfaces communicate through behavior, not just appearance.

Users may never point at any of this directly. They still feel the difference.

Why consistency builds trust

Consistency removes friction.

When every page speaks the same visual language, users spend less energy decoding the interface and more energy using the product.

Users should not have to think about what the system already knows.

That is what feeling at home really means in design.

Not copying something familiar. Not chasing trends.

It means every part belongs to the same world.

Final thought

A palette is not decoration.

It is the atmosphere your product lives in.

What you remove matters more than what you add.

When colors, spacing, motion and hierarchy all pull in the same direction, users feel it immediately.

Good design should feel like home: familiar enough to trust, refined enough to remember.

Clarity scales. Complexity breaks.

Found this useful? Support the work →

If this is the kind of thinking you want in your product, say hello.

Start the conversation.