Software Interface Design

 

Note: This is an outline of PowerPoint. It is prepared for the actual situation of a specific project, so some of the individual principles are particularly introduced, and we usually do not mention these too basic things (it is really embarrassing ). This article is the experience and application of the research results of the predecessors of the interface design. The correct credit belongs to the predecessors, and the wrong responsibility lies in me. In addition, xprogrammer is an electronic magazine that can download www.umlchina.com for free. Unfortunately, there are only 51 issues.

Software Interface Design
Written in: ZB ++
2006-12-5
Publicity slogans
The interface is software, or the software is the interface-for the user
The interface design is not an artist
The interface is part of the requirement-Requirement Specification
People-oriented
Xprogrammer -- Non-Programmer
Outline: Principles
Consistent, consistent, consistent
Inconsistent
Simple task simplification
Intuitive
Exercise caution when using colors and Fonts
Concise, group, and gray
Security

 

Outline: interface specifications
Details determine success or failure
Interface consistency
Use of the wizard
Interface Response Time
Help System
Error and warning information
Interaction principles
Information Display principles
Data input principles

 

Dancing Bear
People are very excited when they see the bears dancing, because a bear can dance, but no one cares about it.
The miracle lies not in the progress of the bear, but in the progress of the bear.

From the path to software innovation, Author: [us] Alan Cooper (father of VB)
Basic principles: Consistency
Consistent, consistent, or consistent. The most important thing you can do is to ensure the consistency of user interface operations. For the list box, if you double-click the items to cause some events, double-click the items in any other list box to have the same event. The positions of all window buttons should be the same, the labels and messages should be the same, and the color scheme should be the same. User interface consistency enables users to establish precise psychological models for interface operations, thus reducing training and support costs.
Establish and follow standards. The only way to maintain consistency in application software is to establish and follow design standards. The best way is to adopt a set of industry standards to supplement their own special needs. Existing industry standards, such as IBM standards (1993) and Microsoft standards (1995), usually meet the needs of 95% to 99%. Using industry standards, you only need to take advantage of existing results and make your applications look or feel more like other applications you have purchased or created.
Take Microsoft's gun ......
According to the consistency principle, it is the most cost-effective to follow the Windows interface style (this is not the case for entertainment software ).
Do not invent your own interface specifications unless you are sure that your new design is absolutely necessary.
Jun Chen, father and son -- menu button tree list
Principle: inconsistent things are inconsistent
Something that looks consistent must have internal consistency
Something inconsistent inside should look different.
Do not set the width of the input element to the same for "beautiful". The width of the edit box is related to the number of characters that can be entered.
Do not use complex controls as simple controls
"Neatly arranged" is in line with the logic and appropriate grouping requirements
Principle: Do not complicate simple tasks
Typical UI design mistakes. As software functions become more complex, operations on simple tasks become more complicated.
Keeping simple tasks simple means a larger amount of coding.
Programmers hate this principle.
The interface is no longer designed by programmers.
Principle: conforms to the business logic and is intuitive
Complying with business logic is an intuitive and easy-to-use basis
Violating the business logic is all nonsense
Objective: To use it without the need to read the manual
You can understand your business needs.
Design operation methods from the user/business perspective rather than the program design perspective
Principle: exercise caution when using colors and Fonts
Do not use complex colors and fonts without expert review. Keep the default colors at least.
Use as few colors as possible. The effects of a different machine will change. The standard colors are the most common.
Takes care of blind users, and adds fonts or symbols to emphasize
Use a readable font
Use as few fonts as possible
Principles: concise, group, and gray
No unnecessary things interfere with the user's attention
Correctly Use blank spaces, grouping boxes, and other interfaces to group interface elements by function or logic
Temporarily unavailable should be dimmed rather than hidden
Uneditable should be read-only, rather than gray
When the form is changed, the relative position of the interface elements cannot be changed (User psychological model)
No unnecessary pop-up message box
Principle: Prevent Users From making mistakes
People make mistakes.
The software should help people, rather than getting into trouble.
A good interface is not prone to misoperations
Incorrect business data cannot be input
Prompt users as much as possible
Supports undo and cancel
The default button should not be disastrous, such as deleting
Details determine success or failure
I am afraid of being "serious" in everything.
The interface is detailed everywhere
The user interface is no small matter. The layout of the form, the business mode, the button size, and the font color are all related to the user experience.
Develop interface specifications
Is the basis for Interface Design
Ensure the consistency of the interface style
Consistency brings ease of use
Ease of use saves training costs
Ease of use reduces maintenance costs
Interface consistency
Consistent display information: font, size, color, and alignment
Reasonable layout: Important and important items should be entered first, and the tab order should be left-to-right, top-to-bottom
Corresponds to mouse and keyboard operations, supporting full keyboard operations
Shortcut Key: The same as the operating system practice, must be consistent in the system
The usage of standard interface elements cannot be changed
Use of the wizard
Must be used for a fixed Process
No less than three processes
The wizard must be complete. When the wizard ends, all services are completed.
To avoid service operation failures due to insufficient basic data, either add required data in the wizard or do not start the wizard
Failed wizard execution is one of the worst user experiences
Interface Response Time
A progress bar or hourglass is required for time-consuming operations.
A prompt must be displayed when the action is completed for a long time.
Allows you to cancel operations that take a long time.
The execution time is too short, and the execution effect interface is not easy to show. You can add a mouse animation to delay the time.
Help System
The Status Bar provides some help
Complete help system provided by menu
Context-related help provided by F1
"What is this" button on the dialog box
Mouse refers to the small prompt displayed above
Specific operation instructions provided by text in the blank area of the interface
Error and warning information
Use understandable text
Provide reference for solving the problem
Indicate possible consequences of errors
Correct use of the prompt icon
The language is gentle, so it cannot be judged or criticized.
Interaction principles
Consistent data display mode
Meaningful feedback on operations
Operations that have an important impact on data must be confirmed
Undo allowed
Minimum user memory information
Interface layout Logic
Action classification Logic
Allow users to make mistakes and the system can be recovered
Information Display principles
Only display context-related information
Unnecessary information is not displayed. Secondary information can be obtained through additional operations.
Display specific meanings with appropriate colors and tags
Screen cannot be overly crowded
Select the best Interface Element
Data input principles
Meet business Constraints
Consistent input and display
Minimize user input and minimize the use of default values
Flexible interaction and quick input, such as automatically jumping to the next Input Point
Data that can be computed by the input program is not required
Help all input
Conclusion: Next Step
Windows interface specification is not optimal
At least the Mac interface is better.
The next-generation interface is user-centered and will provide a brand new user experience. Everything is obvious and no one needs to learn software (excluding business knowledge)