Hands off the standard interface elements!
Many developers suffer from an obsessive desire to improve everything. Along with him in the kit, there is usually not enough insight attached to understand how, in fact, what was being improved worked before improvement.
My call: hands off standard system interface elements! Stop trying to replace them with your improved versions, stop trying to build them. Even if the improvement is successful, it will still cause inconvenience, because your program or website will be the only case where the new user habits (and you get used to the good quickly) will work. And most often, an improvement on closer examination will be detrimental.
As an example, I want to cite the adorable control I have - the scroll bar in Windows. She is beautiful the way it is. It can be done better, but first, please understand how it works now. I will not list all the subtleties of behavior (a single click on a blank background under the bar, a press and hold, a menu call, etc.), I’ll tell you about one thing:
')
If you click on the slider and hold, the content starts to scroll,
BUT
If, continuing to hold the mouse button, move the cursor about 50-100 pixels away from the slider, it will return to the same place it was before clicking, showing the previous position of the document.
I constantly use this opportunity to look forward or backward in a long document, but then it is easy to return exactly to the place where I was before (just by moving the cursor and releasing the button).
I hate any programs in which programmers specifically worked on the scrollbar to stop performing my favorite function.
Taking this opportunity, I want to say hello to the guys doing OpenOffice. Thank you for looking forward or backward, I can’t return in any way just by moving the mouse and releasing the scroll bar, I need to look again for the place where I stopped.
About why there is no kata, see the next series.
My call: hands off standard system interface elements! Stop trying to replace them with your improved versions, stop trying to build them. Even if the improvement is successful, it will still cause inconvenience, because your program or website will be the only case where the new user habits (and you get used to the good quickly) will work. And most often, an improvement on closer examination will be detrimental.
As an example, I want to cite the adorable control I have - the scroll bar in Windows. She is beautiful the way it is. It can be done better, but first, please understand how it works now. I will not list all the subtleties of behavior (a single click on a blank background under the bar, a press and hold, a menu call, etc.), I’ll tell you about one thing:
')
If you click on the slider and hold, the content starts to scroll,
BUT
If, continuing to hold the mouse button, move the cursor about 50-100 pixels away from the slider, it will return to the same place it was before clicking, showing the previous position of the document.
I constantly use this opportunity to look forward or backward in a long document, but then it is easy to return exactly to the place where I was before (just by moving the cursor and releasing the button).
I hate any programs in which programmers specifically worked on the scrollbar to stop performing my favorite function.
Taking this opportunity, I want to say hello to the guys doing OpenOffice. Thank you for looking forward or backward, I can’t return in any way just by moving the mouse and releasing the scroll bar, I need to look again for the place where I stopped.
About why there is no kata, see the next series.
Source: https://habr.com/ru/post/57206/
All Articles