Face uidesign-read [software Concept revolution] [2]

[Design method]

Previously, we saw a lot of theoretical descriptions of how to make a software with excellent UI. However, in practice, many problems will be difficult to solve. For example, how to explore users' goals and their mental models. Such problems require a set of practical guidance solutions.

The book provides a complete set of solutions and guidanceProgramPersonnel for uidesign. Practice, understanding, and rational use of this solution can make your uidesign easier.

I am afraid to write too many things due to my practical experience. After I have accumulated some experience in the future, I will read this part again. Here, I just want to briefly list some of the points mentioned in the book and some superficial personal understandings. If you have enough practical experience, please read the first part of the book carefully, and surely you will not go back empty-handed.

18 ~ Page 19 provides a detailed description of the overall steps of the uidesign. Roughly speaking, it is divided into five stages, sorted by time, namely research, modeling, requirement, framework and optimization. Two Adjacent processes iterate each other. Specifically, we need to conduct qualitative research on the software problems. It means to learn about the basic information of users, users' understanding of problems, and their requirements for products through various means of human species. Then, go to the user modeling process. There are two important concepts in this process. One isUser RoleThe role is to abstract the information of all users and classify user abstraction of similar information into one role. The other isTargetTo understand the role, you need to determine the specific target that the role wants to use the software to accomplish. This is the key to goal-oriented design. After understanding the user goal, we also need to use some means to convert the goal into a design. This is the script outline. As the name suggests, the script outline describes the process of daily use of the software. Just like writing a story, you can record the entire process of using software and the details. Of course, this process is fictitious from the information you have obtained through investigation.

This method reminds me of how FCL designers set class library interfaces in. net design specifications. They will invite (or Virtualize) some users to write someCodeSimulate the process of completing a function, and then sort the importance of the scenario to help complete the design of the class library interface. This method, which uses user virtualization as the starting point, to reverse extract the design scheme is indeed worth learning from.

 

[Software posture]

People who have learned the design model know that in the huge gof project, three major design principles are proposed, and 23 classic design patterns are also proposed. These 23 modes are applied to different scenarios. Whenever we encounter problems similar to a certain mode scenario, we will consider and flexibly apply this mode. This reduces our design burden because we stand on the shoulders of giants.

In the UI design, we have seen the basic theories and ideas above. However, we still need some inherent models for fast application and practice. One mode is divided by software attitude. The attitude of software is the way in which software expresses its own information to users. Generally, we can divide desktop applications into several kinds of gestures:

1. Monopoly posture

An exclusive gesture is a full screen program that requires a long time to take user attention. Such as office suite and Visual Studio. Basically, the vast majority of people who use such software are always intermediate users (well, think about it, there are several people who dare to say they are proficient in word, several other people who have used word won't use word to type ). Therefore, in software design, we should fully consider their feelings. For beginners and experts, we should try our best to satisfy their needs while meeting the needs of intermediate users. A program with an exclusive attitude should regard its space as the whole screen and make full use of every pixel of the screen. Some auxiliary tool bar, as long as useful, do not be afraid to put too much. In terms of vision, we should use less and less conservative colors to provide more non-pattern feedback. Bright colors may be cool, but they will make people who are using them for a long time feel uncomfortable. You need to enrich your input methods, such as menus, toolbar, and shortcut keys, because for intermediate users, they want to quickly enter as they like. In addition, you should try to expand your document area (which is the main function part), because this is what users really need and they need to grasp the overall situation without any effort.

2. Temporary posture

Temporarily open and close the program, and use a very limited set of additional controls to display some single functions. For example, the Windows volume adjustment and calculator also includeAll dialogs. For transient programs, bright and clear colors should be used, and the controls should be as large and concise as possible. Users are likely to be new users (for transient programs, there are a large number of intermediate users who are rarely used, and they will be temporarily degraded to new users). Only such interfaces can help them get started quickly. Unless necessary, you only need to use a window or view (for example, the design of the dialog box stacked dialog box is not good), otherwise it will increase the difficulty of getting started. In addition, the transient program should remember the last state used to help the user quickly complete what he needs to do at the next startup. This is very effective for transient programs because no user wants to spend too much time on transient programs.

3. Genie posture

The genie posture refers to those programs that run quietly and silently in the background. Many applications are converted into this posture when they do not need to interact. In Windows, most of the genie pose programs will leave a flag in the taskbar tray, which is basically all the UIS of the genie pose program ^_^.

4. Secondary posture

A program that combines a temporary and exclusive posture has an auxiliary posture. For example, the floating Prompt window of thunder. They occupy screen space for a long time like an exclusive program, but occupy a small amount of space and only play a secondary role. It exists to provide users with the most needed information about its working conditions through a limited window. Therefore, the information it provides must be concise and conspicuous.

I don't know much about web programs and other programs. This book is not a book focusing on web design.