UNCLESOON'S BLOG

I want to introduce how a network feature including call back ruins our users’ experience today. I bet you may have more than one feature in your product at least, and you may be missing something to make users frustrated. That means your UX is able to be bad somewhere.    1. Prologue These days we can see lots of convenience features in the product like autocomplete, so you don’t need to type the full text keyword. This kind of feature makes it easier to do users’ tasks and also gives an advantage of data regulation.  By the way, when you consider the feature, please check this one.  2. Case 2.1. Successful user scenario Here is a simple case about autocomplete when you enter the keyword in the text field. Mostly it is used for the data of location that can be regulated. When you type the keyword in the first step as below, Text fields in the page You can see the keyword suggestion with the autocomplete feature like this.   Autocomplete in the text fields After you choose the keywor

I have encountered situations to solve problems that didn’t seem like UX problems. Furthermore, the directions were sometimes wrong to UX, and I struggled to explain what it was wrong. I want to introduce how I approach situations after many trials and errors. 1. Prologue When we talked about solving the problem in the project as a UX designer, that was not always clear or simple for me. The big question in my mind was, ‘How come the process of solving the problem is not not simple as a UX designer?’ I wanted to think about the reason for this, and thought about how I can approach the process clearer.  2. What is the UX problem? We may encounter problems not really related to the UX in the project.  For example, let’s think about a mission to increase the user traffic or more income from the product. Is this a UX problem or not? When we are pushed into the situation, there may not be a way out from that kind of mission. Nevertheless, we may have to design the product to the goal what