Hidden interface controls that affect usability

(interactions.acm.org)

561 points cxr | 2 comments | 05 Jul 25 23:10 UTC | HN request time: 0.627s | 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. devnullbrain ◴[06 Jul 25 12:33 UTC] No.44480234[source]▶

>>44477561 #

I really disagree.

An IDE, and the browser example given below, are tools I'll spend thousands of hours using in my life. The discoverability is only important for a small percentage of that, while viewing the content is important for all of it.

This is exactly when I will have the 'knowledge in the head'.

replies(1): >>44482852 #

2. xboxnolifes ◴[06 Jul 25 18:16 UTC] No.44482852[source]▶

>>44480234 (TP) #

What part do you disagree with?

↑