Gregory's ServerIt has to be A. Button already looks like a button, how much more indication do you need?
 16 comments
 There must be an indication on hover, it can be a different cursor or a hover effect on the button Because it let you click faster: the moment your eye see the feedback you can click instinctively. We don't always interact with UI by reasoning, often we know the right button is there and we want to just click as fast as possible and move to the next thing. @nikitonsky What makes it look like a button? Is that a consistent conclusion you could expect across all cultural and generational audiences? Whay about accessibility? What's wrong with adjusting the pointer - the primary input method for a human interacting with the UI - to indicate it's pointing at an actionable element? Why the user has to play a guessing game even to understand if the UI element is clickable or no? @ashald users have been playing the guessing game for 30 years now, and they are fine (no OS or native app change pointer on hover, only web) @nikitonsky I'm afraid this statement doesn't take into consideration experience of non tech savy bros and younger generations. Let alone visually challenged users. The real workd around us is full of visual noise abd somehow humans been living fine with that for forever. UI is not a minimalist exhibition in a museum of modern art. It's a tool with a mundane purpose. @nikitonsky Only B is marked as clickable. This is important on mobile and will become even more important in spatial computing. @nikitonsky But only the right one presents its "Clickability" on desktop.  @nikitonsky My mouse aiming is not too accurate, and I often rely on peripheral vision, e.g. I might be reading the dialog label and not looking at the button directly. So it's much easier to notice the cursor changing its shape than pixel-hunt the button's active zone. @nikitonsky I prefer B for consistency. If some parts of the app have it (e.g., links) and some don't, it adds extra cognitive load for my lizard brain. |
@nikitonsky Either works fine for me. What I dislike is inconsistency across a single site/app, where some buttons are like A and others are like B. In that environment after experiencing a B-like one, I then start to question the A-like ones (is it disabled but not showing appropriate styling...?)