User-allowed policy
All of the following is a product of the life of my brain and is provided "as is".
User-allowed policy is a term I have just coined to denote what the user can be allowed on the interface and what is not allowed. If someone knows the term better, tell us, rejoice together. Google, Vicky and other sources tactfully kept silent.
In our web time period, loyalty and user friendliness often become a fetish. At one time, having looked through (but so, unfortunately, and not having read) the book of the Circle “Do not make me think”, I was amazed by its name. Fantasy helpfully provided me with a picture: millions of users surf the Web using only the spinal cord and not connecting the head. Of course, I guess that the book is not as simple as it seemed to me, but the first reaction was just that.
')
The term put into the name of the topic does not mean the set of agreements between the user and the resource providing the interface, but the principles of building the interface, the purpose of which is to restrict the user from mindless and chaotic actions that will not benefit the user himself or the administration. Often, the reason for the emergence of such actions is the desire to create the most convenient interface, meaning by this the minimization of the number of clicks.
A vivid example is polyvariant controls. Simply put, add a friend link ! (exclamation mark is obligatory at the end!), which for added takes the form Remove from friends :( . Webdwanol and AJAX did everything to add / remove it could be easy, with a single click. After adding we got a new friend, and the link as it should be, obedient polyvariant controls should go into the opposite (or alternative) state ...
Should it? Imagine the situation in more detail. The user in the process of studying the interface can click on the link about ten times, just to observe the process of change. In antiquity, when asynchronous requests did not exist, the user was restrained by the prospect of sticking to the page reload. AJAX freed the user from this.
This is the place for the user-allowed policy . The link does not turn, but simply disappears, becomes text, an alternative appears only after a reboot. By the way, a convenient way to disable such links (except for onclick cleaning, the stump is clear): kill the HREF attribute. This turns the link into a harmless anchor with a minimal amount of movement on the part of JS and, moreover, leaves the content with all its styles that could fly, we replace the tag with SPAN or something.
I think that you can find a lot of examples for applying user-allowed policy . I propose to speak and discuss.
User-allowed policy is a term I have just coined to denote what the user can be allowed on the interface and what is not allowed. If someone knows the term better, tell us, rejoice together. Google, Vicky and other sources tactfully kept silent.
In our web time period, loyalty and user friendliness often become a fetish. At one time, having looked through (but so, unfortunately, and not having read) the book of the Circle “Do not make me think”, I was amazed by its name. Fantasy helpfully provided me with a picture: millions of users surf the Web using only the spinal cord and not connecting the head. Of course, I guess that the book is not as simple as it seemed to me, but the first reaction was just that.
')
The term put into the name of the topic does not mean the set of agreements between the user and the resource providing the interface, but the principles of building the interface, the purpose of which is to restrict the user from mindless and chaotic actions that will not benefit the user himself or the administration. Often, the reason for the emergence of such actions is the desire to create the most convenient interface, meaning by this the minimization of the number of clicks.
A vivid example is polyvariant controls. Simply put, add a friend link ! (exclamation mark is obligatory at the end!), which for added takes the form Remove from friends :( . Webdwanol and AJAX did everything to add / remove it could be easy, with a single click. After adding we got a new friend, and the link as it should be, obedient polyvariant controls should go into the opposite (or alternative) state ...
Should it? Imagine the situation in more detail. The user in the process of studying the interface can click on the link about ten times, just to observe the process of change. In antiquity, when asynchronous requests did not exist, the user was restrained by the prospect of sticking to the page reload. AJAX freed the user from this.
This is the place for the user-allowed policy . The link does not turn, but simply disappears, becomes text, an alternative appears only after a reboot. By the way, a convenient way to disable such links (except for onclick cleaning, the stump is clear): kill the HREF attribute. This turns the link into a harmless anchor with a minimal amount of movement on the part of JS and, moreover, leaves the content with all its styles that could fly, we replace the tag with SPAN or something.
I think that you can find a lot of examples for applying user-allowed policy . I propose to speak and discuss.
Source: https://habr.com/ru/post/39208/
All Articles