You’ve clicked one. You’ve probably designed one. And if you’re unlucky, you’ve had to explain one in a stakeholder meeting.
I’m talking about that gorgeous, shiny, confident-looking button in your UI\UX that does absolutely. Nothing.
Not a redirect. Not a modal. Not even a dignified error. It just sits there, smug and dead inside — like the ghost of roadmap features past.
Why Do These Buttons Exist?
Because hope is a hell of a drug.
The backend isn’t done. The feature isn’t scoped. But the pitch deck needs screenshots, and your PM is muttering something about "momentum." So the button gets shipped. Quietly. Maybe no one will notice.
They notice.
Users click. Nothing happens. They click again. Still nothing. At click three, trust is gone and rage has taken its seat. And now your support team is trying to explain why "Save Draft" doesn’t, in fact, save anything.
The Emotional Lifecycle of a Fake Button
Let’s not pretend it’s harmless. A non-functional button is a broken promise, shrink-wrapped in beautiful UI.
Click 1: Optimism
Click 2: Confusion
Click 3: Existential doubt about the entire product
Click 4: They never click again
Every time you ship a button that lies, a user learns not to trust your interface. It’s death by a thousand micro-disappointments.
When Is It Actually Fine? (Rarely, But Okay)
Yes, sometimes fake buttons serve a purpose — if, and only if, you:
- Clearly label them: "Coming soon," "Launching October," "Please don’t click me yet, Karen."
- Use a visual cue: a clock icon, dashed outline, or the unmistakable vibe of something not quite alive.
- Offer feedback: a tooltip, a modal, even a gentle message saying "Not yet, but it’s coming."
- Plan to deliver soon. And no, Q4 next year doesn’t count.
If your button’s a teaser, fine. But if it’s a trap? That’s on you.
When Is It Not Fine? (Most of the Time)
- If the button looks 100% functional but does 0% anything
- If it’s been fake for months and no one has the guts to remove it
- If users need that feature and you’re giving them an illusion instead
- If it damages confidence in your entire product (which it will)
This isn’t MVP thinking. It’s UI cosplay.
Let’s Talk About The Real Villain: You (Yes, You)
If you’re reading this and nodding along while knowingly leaving that fake button in your next release: congratulations, you’re the problem.
You’re not "moving fast." You’re moving deceptively.
And your users? They’re the ones paying the price — in confusion, in time wasted, in lost trust. That’s not agile. That’s just irresponsible.
Better Than Faking It
- Grey it out with a clear message.
- Use microcopy that actually communicates something useful.
- Link it to a feedback form if you want to gauge interest.
- Remove it entirely until you’re ready to deliver.
Just don’t leave it there, hoping people won’t notice. They will. And they’ll judge you.
What This Button Says About You
It says:
- You prioritise aesthetics over honesty.
- You fear difficult conversations with product.
- You think users are too dumb to notice (they’re not).
- You’re designing for a demo, not for reality.
You’re not just designing an interface. You’re designing expectations. Expectations that — if unmet — turn into resentment.
So What Do You Do Instead?
Be honest. Be clear. Be brave enough to ship what’s real, not what’s pretty.
Every interactive element is a tiny contract with your user. Break it once, maybe they forgive you. Break it twice, and they’re gone.
Design is trust. Buttons are promises. If yours is lying, either fix it — or kill it.
Because the truth is: a button that does nothing is worse than no button at all.
It’s a lie in a border-radius wrapper.
And your users? They’ve had enough lies for one internet.
Top comments (0)