When should I worry about UX?

5

Recently I've seen some posts about what UX is (User Experience) and this part seems to me to be understandable about "what is it?"

However, I wanted to know when I should worry about UX. I am a web developer and I usually make CRUD systems for companies. To what extent can UX help or hinder development?

What I mean is: Do I simply do what the client asks for in a functional and "cute" way or is it really good to create the whole experience?

    
asked by anonymous 23.08.2018 / 19:36

1 answer

10

"Always", from the most basic to the most sophisticated software, unless it has zero user interaction even indirectly, which I have never seen. Of course in some cases you need less worry, in most cases no one will die for having bad UX.

It does not matter if it will make development difficult, you do things for users, if they do not have a good experience, they are doing something bad. Of course there are other variables to be analyzed in each project. And it varies from case to case. If everyone worried about UX would not have software as bad as we have.

UX is very important! Point.

  • Running is UX.
  • Give the right result, expected, always, at the right time the right way is UX.
  • Using certain terms for the public is UX.
  • Do not be excessive is UX.
  • Being easy to use and to learn (intuitive to your audience) is UX.
  • Allowing agility and easy correction of misconceptions is UX.
  • To effectively guide the user with difficulty is UX. Monitoring can be UX.
  • Running on the easy platform with the right interface is UX.
  • Being nice and nice is UX.
  • Being fast is UX.
  • Do not give error is UX.
  • Do not fool the user is UX.
  • And the list can continue ...

UX is not just visual, let it be clear, many people confuse UX with UI. The first is the experience as a whole and the second is the interaction with the user directly, and even this part is not only visual. UX is to make the user feel good using their software. It is not he who is dumb for not using his software, it is you who failed to reach his goal of UX.

There are things that are natural, it's not a question of deciding whether or not to do it. There are aspects that can complicate the software by not having good UX. Many cases will cause recall , are you prepared for this? Is it in the contract? Do you have a budget for this?

Does the budget allow you to cope well with all aspects of UX? In a formal or just intuitive way? You can never analyze without looking at all this.

If you can do the best because you would do less than this?

    
23.08.2018 / 19:48