Highly recommended! Many students do design when they often miss out on that, wait until the development to ask when the thought. Now have netease students self-created self-examination table, you can put some problems in advance prevention, article system comprehensive, well-organized, is a rare practical good text yo.
Flying spirit: For mobile applications, mobile scenarios are very complex and devices are diverse. Then in the design, before the design Review, your interactive manuscript to consider the details are perfect, the description of the special status is missing, how do you find some problems in advance and check the vacancy? To solve this problem, our team has established an interactive design self-examination table, and in the process of version iteration synchronization iterative, Supplement the new occurrence of the exception point.
This form combs out the various anomalies that the user has in the process of completing a specific task. It does not show all the details of the interaction, but it can provide a comprehensive perspective of the user experience for specific goals. This goal may be high-level, such as how to show when an operation is not networked, what to do when the network is poor, and so on. In this process, the solution may be different because of a special use scenario, but this form will remind you to think deeply about a solution. Here are some of my little experiences in summarizing these anomalies.
One, interactive design self-examination form how to build
Usually in the QA test, the user's task is generally the main line, that is, the product analysis and summary of all the tasks, and Output task list, go to check, identify the module, preconditions, use case title, implementation steps, expected results, and some important notes. If the interaction students also use this method, we need each version to spend a lot of energy to write, comb use cases, and we have spent less time to quickly check the leakage of the original intention of filling out. Moreover, the user task of the search in the design process will be taken into account, and the omission is often a number of anomalies.
Therefore, interactive designers in the self-examination, you can try another way: first of course, the actual function of the product can meet the needs of users. This is the most basic premise, that is, the availability of the goal of "feasibility." Then think about the user's core usage scenarios and the core impact factors when using the product, classify these factors in the blocks you are in, understand their impact on your user experience goals, list them, categorize them, and form them, and you can continue to do so in later versions, If there is a new anomaly, then add it in this way.
We can divide the process into the following 4 steps:
Figure 1:4 steps to establish a self-examination table
In order to better the people, machines, equipment, use scenarios and other factors to the design of the impact are taken into account, I have these factors in the module to classify, can be divided into the following categories:
1. Hardware and software features: equipment, systems, new and old versions compatible
Figure 2: Hardware and software features related
The diversity of mobile phone hardware and platforms brings challenges as well as opportunities for design. In addition to some of the above, we have to consider a lot of points, such as the larger screen, when in the rocking compartment, the big screen in a single hand operation, we need to consider how to design so that users can use more natural and smooth.
2. Network characteristics
Figure 3: Network characteristics related
Because mobile applications use the particularity of the scene, encountered data loading slow or no network situation will be many, at this time the long data loading waiting will make users crazy. At this time, the interface to deal with the loading, to ensure that the user does not have a long waiting sense, and the contents of the load after a clear expectation, it can provide users with a better sense of use. Therefore, in all the modules involved in network interaction, we must consider these points listed above, when necessary, reasonable use of caching, to enhance the interface response speed.
3. The middle state from A to B
Figure 4: Intermediate state from A to B
Even if your product is running well 90% of the time. But they won't forget it if they don't want help. --"Getting real"
In the process of accomplishing the task, the user is actually telling the story of a user, so it must include the beginning, the middle and the end. The middle part is the main part that shows the whole place that the user will pass from the start point to the destination. The one thing to solve is that if everything goes well, how to give users a smooth, flowing feeling, this is the dynamic effect can help us do; On the other hand, if you need more time in a task, users do not want to play, at this time can provide an occasional entrance, so that he and the application of "Farewell", Instead of letting him just kill the backstage program, stormed away.
4. Content presentation Related: such as books and information sources
Figure 5: Content Presentation related
For the content of this piece, the most unusual focus is on a large number of empty states, extreme values, network data expiration and so on prompts. Different apps vary according to their own type, and the content to consider is completely different.
5. User Personal Properties
Figure 6: User personal properties related
In most applications, each user has his or her own ID, and depending on whether or not the user can enjoy the same permissions. Therefore, it is particularly necessary to consider each possible state of the user and the effect of switching between States on the design.
6. Status under Special situations
Figure 7: State in a special situation
Special status refers to a pattern that exists in order to meet the specific needs of the user, which is often forgotten during the design process because of the fact that the exposure rate is not particularly large at ordinary times. But once not considered, the result will be a variety of abrupt and inexplicable. So it is necessary to pick up the state of this type individually and comb it.
Second, the self-examination form how to use
Repeated "design-self-examination", this self-examination (sometimes the user's test intervention) will be more comprehensive, more thorough, and ultimately be able to find and solve most of the problems. Interaction designers use feedback to correct ideas, and so on several times, they can be distilled to form specifications. This is especially important when designing new products. This iteration is unavoidable, because many times we cannot find a particularly complete and correct solution at once.
The above factors, different mobile applications will be based on their own unique scenarios to extract specific factors, these factors will have a greater impact on the design. The mobile scene is very complicated, besides the hardware and software characteristics, network characteristics, intermediate state, content, user's personal attribute, some special situations, the influence factors are many. The correct analysis and recording of various factors, handling and application in the design, can make the experience of the product improved, and in this ascension process, we can make them into norms. As each iteration builds new functionality, we can review the impact of these factors on the design in the current period and add the additional impact factors to the subsequent interactive design self-examination. This accumulation, we have to take into account the anomaly will be more and more, so that the consideration will be more and more perfect, so as to reduce the follow-up development process of the loss of blood ~ I have medicine! can be cured!