←back to thread

Hidden interface controls that affect usability

(interactions.acm.org)
559 points cxr | 1 comments | 05 Jul 25 23:10 UTC | HN request time: 0.204s | source
Show context
weinzierl ◴[06 Jul 25 03:23 UTC] No.44477561[source]▶
I get why you would hide interface elements to use the screen real estate for something else.

I have no idea why some interfaces hide elements hide and leave the space they'd taken up unused.

IntelliJ does this, for example, with the icons above the project tree. There is this little target disc that moves the selection in the project tree to the file currently open in the active editor tab. You have to know the secret spot on the screen where it is hidden and if you move your mouse pointer to the void there, it magically appears.

Why? What is the rationale behind going out of your way to implement something like this?

replies(8): >>44477624 #>>44477657 #>>44477684 #>>44477720 #>>44477854 #>>44478558 #>>44480234 #>>44484094 #
1. burnte ◴[06 Jul 25 21:12 UTC] No.44484094[source]▶
> I have no idea why some interfaces hide elements hide and leave the space they'd taken up unused.

UI has been taken over by graphic designers and human interaction experts have been pushed out. It happened as we started calling it "user experience" rather than "user interface" because people started to worry about the emotional state of the user, rather than being a tool. It became about being form over function, and now we have to worry about holding it wrong when in reality machines are here to serve humans, not the other way around.