User-allowed policy

    All of the following is a product of the vital activity of my brain and is provided “as is”.

    User-allowed policy is a term that I just coined to mean what the user can allow on the interface and what cannot. If someone knows the term better, tell us, we’ll be happy together. Google, Vicki and other sources tactfully kept silent.

    Nowadays, loyalty and user friendliness often become a fetish in our webdanolic times. After looking through (but, unfortunately, without having read) the book of the Circle “Do not make me think,” I was amazed at its title. 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 given in the name of the topic does not mean a set of agreements between the user and the resource providing the interface, but the principles of constructing the interface, the purpose of which is to limit the user from thoughtless and chaotic actions that will not benefit both the user and the administration. Often, the reason for the appearance of such actions is the desire to create the most convenient interface, meaning by this minimization of the number of clicks.

    A striking example is multivariate controls. Simply put, the Add as Friend link ! (an exclamation mark at the end is required!), which for the added takes the form Remove from friends :(. Webdwanol and AJAX did everything in order to add / remove it would be easy, with a single click. After adding, we got a new friend, and the link, as it should be for an obedient multivariate control, 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 in order to observe the process of change. In ancient times, when asynchronous requests did not exist, the user was held back by the prospect of a stick to reload the page. AJAX freed the user from this.

    This is a place for user-allowed policy. The link does not turn, but simply disables, becomes text, an alternative option appears only after a reboot. By the way, a convenient way to disable such links (except for clearing onclick , the stump is clear): kill the HREF attribute. This turns the link into a harmless anchor with a minimal amount of movement from the JS side and, in addition, leaves the content with all its styles that could fly, we replace the tag with SPAN or something like that.

    I think that there are lots of examples for applying user-allowed policy . I propose to speak and discuss.

    Also popular now: