Use the hand cursor
Not using it is an unjustified design flex 💪
Adam Silver brings up some solid points on why buttons (and other components) should not be accompanied by the hand cursor; however, I do not think his 3 part series does enough for me to stop what at this point is common practice.
Adam’s main point(er) is that e.g. buttons should have sufficient signifiers without the need for the cursor to change to a hand. But why not have an additional signifier? Sure, buttons that appear clickable and have sufficient hover over states do not NEED the cursor to change to a hand, but if it helps even just one user know that they can click on the button then it is worth it. Let’s look at one comparison.
In Figma, when attempting to click on a file I admittedly hesitated on where to click the first time. Do I click on the text or do I click on the canvas? Can I click on either? Furthermore, having the default cursor still makes me think I have to double click things, which is oftentimes unnecessary work for the user.
InVision, on the other hand, makes it very clear to me that you can select anywhere on the card.
Is this a HUGE difference? No, but as designers we should always focus on the little things.
If other signifiers help the user understand a button is clickable then the cursor type can be a nice confirmation. If the signifiers are not designed or sufficient (and let’s be honest, this will happen) then the cursor type can save the day!
In conclusion, apps that ignore this easily-implemented signifier I think are trying to flex on how intuitive their design is. As seen in the example above, this can come with drawbacks. As much as I love Figma, I think they can flex their superb UI elsewhere and stay on the safe side when it comes to cursor types.
Disagree? Would love to here your thoughts!