What makes a button feel clickable — and what happens when it doesn't?

A button seems like the simplest thing in design. Press it, something happens. But beneath that transaction sits a surprisingly rich set of decisions: about visual signals, about feedback, about what it even means for an interface element to feel interactive. Get those decisions right and users never notice. Get them wrong and frustration accumulates in ways that are hard to diagnose and easy to blame on the user.

This episode takes apart the humble button — its states, its affordances, the small cues that make it feel alive or dead — and traces why something so ordinary turns out to be genuinely difficult to do well. The hosts move from the research that first named these ideas to the real products where the trade-offs play out, and they don't shy away from the counterarguments along the way.

A few of the threads the episode pulls on:

• Why the word "affordance" means something more specific than most design conversations let on

• What button states actually are, and which ones tend to get quietly dropped in production

• The case for flat design — and what was lost when skeuomorphism left

• How touch, cursor, and voice interfaces each change what a button needs to communicate

Whether you work in UX, care about the software you use every day, or just find yourself curious about why some interfaces feel effortless, and others feel like guesswork, this one is worth sitting with.