14 luglio 2016

Consistent terminology is crucial for a user experience (UX)

The User eXperience (UX) describes the interaction of a user with a website. It refers to the communication between the visual and textual data represented on the screen of the computer and the user. One could say that the UX is ‘the smell of a website’.

How quickly a user can make decisions and how efficient he/she can ‘navigate’ a website depends on various factors which are studied by the developers of the website. The developers’ aim is to create a friendly and easy environment for their consumers by paying attention not only to the images, colours, templates or other attracting visual features of their website but also to the textual representation. That means that UX is about the interface between graphic and content. A user is firstly attracted by the colours, the visual representations and the general sense of the website but to the next and most important level he/she needs to take some information, complete a task and interact with the website. If we imagine a website consisted only of images and colourful boxes it is beyond shadow of doubt that no effective interaction can take place.

How do you interact with this pop-up?


Text, thus, is crucial as it provides the most significant information for the user (e.g. login, payment, donate, cancel, etc.). The user needs the textual data. Nevertheless, the user does not want to think. He/she does not want to spend hours looking for his information or completing a registration or doing an electronic payment. He/she needs efficiency in time and that relies on the accuracy and the consistency of the terms which are used. As Bill Gates had mentioned ‘Content is King’, however as I often highlight ‘Terminology is Queen’.

The text which is represented should be clear, simple, understandable, up to date and based on the perspective of the user. It should not cause any misunderstanding or confusion.



Nessun commento:

Posta un commento

Inclusive GIT branch naming

“main” branch is used to avoid naming like “master” and  “slaves” branches “feature branch” for new feature or bug fix   The shift fr...