Small Software Interface Design Guide

This article provides some methods and principles for general interface design and production of small software, as well as solutions to related problems.

1. Follow consistent standards, establish standards, and follow

Whether it is the use of controls, prompt information wording, color, window layout style, follow the unified standard, to achieve true consistency.
Benefits:

1: enables users to build accurate mental models. After a user is familiar with an interface, switching to another interface can easily deduce various functions, the statement does not need to be understood.
2: Reduce training and support costs, and support staff will not be able to provide guidance on a case-by-case basis.
3: Give the user a unified feeling, do not feel confused, have a good mood, and increase support

Practice:

Experienced persons in the project team should establish the UI specifications:
· The artist provides the color scheme and the overall color table.
· The interface control program personnel and user experience personnel propose a control library for reasonable and unified use. Refer to the standard interface usage specifications:

Controls comply with industry standards. For Windows platforms, see Microsoft user experience (in msdn, Chinese has been translated and published, and the project team must have one)

You can modify the style and tone of a widget within the allowed range.
Refer to the advanced operations of other software to extract functions useful to this project for use. It is absolutely not intended for blind access.
Design special operation controls as needed. The principle is to simplify operations and achieve certain functional purposes.

· The interface implementer and the artist discuss the feasibility of the control. (If this step is not implemented, it will lead to dissatisfaction with the work of the other party and inconsistency ). Repeat the above work.
· Establish a rational document UI standard to describe the above specifications,
· The interface designer is forced to understand and act as a development criterion,
· SQA personnel monitor the compliance of developers and warn developers in a timely manner.

II. (color) Use appropriate colors and follow the comparison principles

1: Unified tone. Select the appropriate color for the software type and the user's work environment:
Security Software, according to industrial standards, you can select yellow, green to reflect environmental protection, blue to show fashion, purple to show romance and so on, light color can make people comfortable, dark background makes people do not feel tired, etc.

2: If you do not have a series of interfaces of your own, you can use the standard interface to avoid this aspect, so as to be consistent with the operating system and read the standard color table of the system.

3: blind and weak users should use special indicators, such "! ","? "Duplicate numbers and icons

4: The color scheme also needs to be tested. Because of the display and video card problems, the color performance varies with each machine. Therefore, the color scheme should be tested strictly.

5: Follow the comparison principle: Use dark text on a light background, use light text on a dark background, blue text is easy to recognize on a white background, and red background is not easy to distinguish, the reason is that there is no contrast between red and blue, while the contrast between blue and white is very large. Unless in special cases, do not use strong contrast, people produce a sense of hate color.

6: use different colors as few colors as possible for the entire Interface

ITOP color table
For specific standards, refer to the academic standards of Fine Arts statistics.
The construction of the color table serves as a standard reference for the artist in the design and packaging design of the pattern, and plays a rule-based role for the design controls and form color of the program interface designer.

III. (Resource) Resources

A colorful human-computer interaction interface is indispensable for exquisite mouse cursors, icons, graphic images, and basemap.

1: you also need to follow the unified rules, including the above-mentioned establishment of the color table, the creation steps of the icon should also be as standard as possible, refer to the iTOP outlookbar icon design standard
2: Standard icon style design, unified layout, unified color tone, contrast, color level, and image Style
3: The basemap should be integrated with the basemap, with light color, low contrast, and as few colors as possible.
4: icons and images should clearly express the meaning, follow common standards, or easily think of objects on the user's machine. By default, fantastic patterns are definitely not allowed.
5: The mouse and cursor style are unified. Try to use system standards to prevent repeated situations. For example, the shape of a hand in some software may be four minutes different.