The PerfectButton

Is this a problem that was solved in Windows 95? Sure. Are we solving it again? Yes.

It's Just a Button

That's what I told myself. It has two states. How hard can it be? I'd shipped software at Amazon and Microsoft. I knew better.

Here's the thing nobody talks about: users don't read your product. They feel it. Before they process what a button says, their fingers have already decided whether your app is a toy or a tool. A button is the first handshake between your product and someone's nervous system. Get it wrong and everything after feels slightly off — like a song played a half-step flat.

"Users don't read your product. They feel it. And they feel it first through their fingertips."

CONQR is a territory-conquest running app. The whole premise is that movement should feel powerful and earned. Our buttons had to match that energy — and they didn't. So I went deep.

Why Your Brain Cares

Humans evolved in a physical world. Every object you've ever touched gave you feedback. Your brain built its entire model of cause-and-effect on that loop. When you tap a digital button, it's running the same program — looking for evidence that something happened. When that feedback is absent, there's a tiny subconscious alarm: did that register?

That's why people tap things twice. Not impatience — the button lied to them. The closer you approximate physical depth cues, the more "real" your interface feels. So we got obsessive about it.

Every number was argued over. The 55ms down stroke is linear — no easing. When something heavy slams, the impact is instant. The 120ms ease-out on release is where physics takes over. The 5px depth shelf says "I am a physical object" before you touch it. When it drops to 2px on press, the shadow reduction tells you: this thing moved.

We also added a depth notch — a tiny blurred shadow at the bottom of the button representing the cast shadow from its physical thickness. Nobody consciously notices it. That's the whole point.

The Actual Buttons

Go press them. Feel the slam. Notice how the selected state sits lower than idle — that's intentional. It committed to the surface.

Was It Worth It?

Most users will never consciously think about the button. They'll tap it, it'll feel right, and move on. That's the goal — something that feels so correct it becomes invisible.

But here's what I know: when I test the app and tap a button, I don't get the little alarm of did that register? It feels done. Confident. Like the rest of the app should feel.

The button isn't just a button. It's a philosophy made tappable: CONQR is not a soft app for soft runners. Every territory you claim should feel earned. The button is the first place that feeling gets communicated. It needed to be right.