Deep misunderstanding of usability
More and more convinced that people do not understand usability. This is sad because a lot of these people rivet sites, programs, and more. People do not see the essence of the task and do not understand that even the best representatives of modern programs are a compromise of convenience related to the state and capabilities of technologies.
Let's start from afar and take a look at the technique.
Take the power button on the computer. So, the button to turn on the computer users DO NOT NEED. This is a compromise that had to be made due to limited technology.
')
The power button is an engineering decoration imposed on users for the wretchedness of technology.
The user is not interested in the process of turning on and loading the computer. He needs that the program instantly started and did what he needed. The power button is, albeit minimal, but inconvenience, evil.
Let's go back to the programs. The program close button is also evil. The user is not interested in the closed program or not. Suppose I need to fill some text. I want to activate the text entry box and type text there. Everything. All other actions _ _
For example, the program may ask for the name of the file and offer to select a directory on the disk to save.
But I, as a user, do not need a hierarchical directory system. I generally do not need directories.
As a user, I would be much more satisfied with a completely different search pattern for archived documents. I would like to see a detailed calendar in which the documents I have changed are tied to the days. It's easier to remember and find. I would like to search for any words, attach tags. Anything, but I don’t want to __ catalog, I don’t want to search or create the necessary folder documents \ dogovora \ postavki_v_kreml \ aktualno. Later, I may want and systematize the files, but why should I shove them into directories? Why can't I have a separate cataloger with links to files that are all in one place?
The hierarchical file system is convenient for _computer_. To the user, it is also _tangled_.
Just like the file name with an extension that defines the file type. This is also _notted_. The user is not interested to see “Photo_President.jpg”, this “.jpg” is the “guts” of technologies that stick out from under the glossy cover.
It must be understood. It doesn't matter what is done in the office or other commercial software. They are bound by tradition and __ users. They didn’t create a perfect and thoughtful interface, but __ started to make it uncomfortable. With guts like file system directories or file extensions.
and so on…
Let's start from afar and take a look at the technique.
Take the power button on the computer. So, the button to turn on the computer users DO NOT NEED. This is a compromise that had to be made due to limited technology.
')
The power button is an engineering decoration imposed on users for the wretchedness of technology.
The user is not interested in the process of turning on and loading the computer. He needs that the program instantly started and did what he needed. The power button is, albeit minimal, but inconvenience, evil.
Let's go back to the programs. The program close button is also evil. The user is not interested in the closed program or not. Suppose I need to fill some text. I want to activate the text entry box and type text there. Everything. All other actions _ _
For example, the program may ask for the name of the file and offer to select a directory on the disk to save.
But I, as a user, do not need a hierarchical directory system. I generally do not need directories.
As a user, I would be much more satisfied with a completely different search pattern for archived documents. I would like to see a detailed calendar in which the documents I have changed are tied to the days. It's easier to remember and find. I would like to search for any words, attach tags. Anything, but I don’t want to __ catalog, I don’t want to search or create the necessary folder documents \ dogovora \ postavki_v_kreml \ aktualno. Later, I may want and systematize the files, but why should I shove them into directories? Why can't I have a separate cataloger with links to files that are all in one place?
The hierarchical file system is convenient for _computer_. To the user, it is also _tangled_.
Just like the file name with an extension that defines the file type. This is also _notted_. The user is not interested to see “Photo_President.jpg”, this “.jpg” is the “guts” of technologies that stick out from under the glossy cover.
It must be understood. It doesn't matter what is done in the office or other commercial software. They are bound by tradition and __ users. They didn’t create a perfect and thoughtful interface, but __ started to make it uncomfortable. With guts like file system directories or file extensions.
and so on…
Source: https://habr.com/ru/post/48752/
All Articles