Improve Software User Experience

In addition to being stable, powerful, and user experience, a software is also important. Program While emphasizing its functions and performance, developers and testers often ignore the importance of user experience, or focus only on user experience interfaces and ease of use, while ignoring other aspects. I will talk about some of my accumulated experiences.
In general, the display system, organizational structure, and Operation prompts of an application system should be consistent. The consistency of the interface style and layout makes people visually feel that this is a unified system and a coordinated system. As for the style and color system used, the artist and the designer decide the function. The consistency of the organizational structure and operation prompt makes you feel that this is a unified system in terms of structure and response in terms of operation experience. In fact, the organizational structure is related to both visual experience and operation experience.
1. Display System
For most developers, it is not easy to design a good system interface, especially in color. It is indeed a little difficult for people who do not have the basis of art. I don't think it should be too fancy or too many colors. orients may like cool colors and westerners may like warm colors. Fortunately, the company has an excellent design team, and the interface is handed over to them. In this way, our developers can fully focus on internal programs. This is awesome!
Ii. Organizational Structure
1. Good Navigation System
A good navigation system allows users to find what they need in a short period of time. This requires that functions be classified accurately and functional text descriptions are appropriate, so that most users are not misled, meets the usage habits and living habits of most users. As we say, "There must be grass in three steps ". As the system functions become more powerful, navigation problems will become increasingly prominent. It takes a lot of time to organize large information resources and functional resources. A large website will be revised in a short period of time. In addition to being visually fresh, functions and content will inevitably be re-optimized, because the original organizational structure cannot display all the information and functions well.
2. Operation restrictions
Where there are operation restrictions on the current user, we should block the incorrect operation visually or before the user submits the information, instead of waiting until the operation is complete, when you submit it to the system, you will be prompted. For example, if the database string field corresponding to a text box is limited to 10 characters, we must limit the length of user input to this range. For example, A button has no permission for the current user. We should disable it or hide it, instead of waiting until the user clicks it to prompt that the user has no permission. In short, we try our best to prevent users from performing incorrect operations and reduce user detours. This will improve the user experience, so as not to blame us for not doing well and allow them to operate what they cannot do.
3. Operation prompt
The operation prompt is a popular saying. For us, the system response will be more appropriate. For any interactive system, it is necessary to give users appropriate operation prompts, including pre-operation prompts and post-operation prompts.
1. pre-operation prompt
The prompt before the operation should be placed next to the operation item, so that the user can only notice its existence when operating the item. For very important prompts, we can highlight it with colors and other elements. Of course, the existence of these prompts will affect the visual effect and organizational layout. You need to consider how to coordinate them.
2. Operation prompt
This is the so-called interaction prompt. In my opinion, do not use a pop-up dialog box to display the prompt information whenever possible. If you like to open a speaker, and the volume is not very small, I think, you must hate it, because the pop-up window will suddenly jump out, scared you. Isn't it a prompt? Why do you want to disturb the user so much? What's more, you need to click it? It is best not to display the operation prompt to the user on another unrelated page, which will make the user feel at a loss. The best thing is to give a prompt next to the operation item, because the user's eyes are still focused here, which shows that the user can really let it notice without interfering with his operation. For example, you need to verify the user input information in ASP.. net, you may choose to use the verification control to verify the input. In this way, when the user input is invalid, the page will not be refreshed, the response time will be affected, and the verification control will be placed next to the input item, when the user's input is invalid, a prompt will immediately appear next to it. It will not be told that the first entry is invalid until all user information is entered, therefore, the following items must be entered again. For some input items that must be determined through interaction with the server and determine whether the subsequent content is valid, we 'd better give a button next to them, this allows you to know whether the item is valid after you enter it. The "check whether the user name is valid" button on the registration page is a good example. A few years ago, I was very depressed when I registered with csdn. Only after all the information was filled in and submitted can I check whether the user name exists, password, email address, and other important information should be refilled, however, it will turn to another prompt page, and all the information returned will be lost, and you have to input all the information from the beginning, which makes me so angry!
Of course, for some very important or serious prompts, we can use a pop-up dialog box to prompt, or call it a warning. For example, if you want to delete a very important data, we should prompt whether you want to delete it to avoid misoperation.
Return to the page. For example, add Article Which page should be returned later is more suitable for users? Many systems still stay on this page after the user completes the operation on a single item. At this time, the user has completed the operation on this item. What reason does it stay on this page? Why not return to the page where you can view the operation results? I think what the user wants most at this time is to view the results of this operation. For example, in the previous article page, after the operation is successful, we can return to the article list page. After reading the article, the user can click to view the result. This is also the case for editing and deleting operations, and the parameters on the list page, such as page numbers and options, should be retained when returned, in short, try to be close to the user's status before the operation, so that the user can see more clearly the changes after the operation, to determine what to do next.
In recent years, the blog and other services with the idea of Web2.0 have been booming. What is the essence of Web2.0? It is user-centered and focuses on user experience. This also activates developers' enthusiasm for Ajax. If you use Gmail, you will feel a little refreshed, concise, and fast. In the industry, Ms software is undoubtedly the most user-friendly and easy to use. Its OS is not better than others, but closer to the public. Google's innovative capabilities are unmatched, and its products are even better because they focus on user experience. I remember that the exhibition hall of IBM was "thickpad experience center ". The service objects of software are users. Only by dropping the identities of developers and testers, reviewing the software from the perspective of users, and continuously improving the software can the software have a better user experience.