Standard design experience: Who is the user, what is the demand?

The background system uses a whole set of UI, why the form is different? Can you unify and bring a better experience? Based on the inner doubt of the interaction designer, we are eager to produce a set of design specifications used to unify the background operating system, to facilitate the cultivation and continuation of user habits, reduce learning costs, improve the use of efficiency, and effectively improve development efficiency , convenient function optimization expansion. Based on the existing system, we cobwebs, only now the phased results.

Who is the user? What are the requirements? The basic understanding of an interaction designer for a project stems from these two issues. The same is true of our specification ...

You know, or don't know, the norm is there, not sad, not happy.

Who is the user? Who is our system for?

The initial stage is to give us the second, the late system will be open, external businesses or commissioned to use our system. So the first time we do system specification because the merchant or the client's information can not be mastered, it is mainly for our small two.

What are the characteristics of our little two? What are their current methods of inputting information?

Small two this role in our part can be subdivided into: certification small two, logistics small two, industry operation Small Two (industry operation small two inside also points: buy hand, buy hand assistant, shop operation second, website operation small Two ...) Each role to the purpose of this system is different, the industry operation of small two, come in mainly input information, tracking orders. Logistics small two mainly to view the audit industry small second application, tracking orders, view the report. Certification of small two mainly audit industry small two or business applications, tracking certification, analysis of data.

What are the requirements?

Because the original system development situation uneven interactive resources, front-end controls did not do, resulting in users extremely difficult to use. In the process of system opening, frequent alternation, vision and front end lead to the difference of individual system interaction, while multiple systems present to the same user, although the basic framework is no problem, but the efficiency is low in the process of operation.

Solution: Users need an easy-to-use backend system to improve their efficiency.

The purpose of our specification is to unify the visual + Interactive specifications of the existing three systems, and then deliver the front section and the front end to specify their code specifications. Let's move on to the first step in improving the efficiency of our small two.

You read, or do not read, the norm is there;

From which latitude does the specification design unfold?

1. Control

In computer programming, controls (or widgets, widgets, or control) are graphical user interface elements. is a basic visual widget block, contained in an application, that controls all the data that the program handles and the interaction of the data.

Based on the PARC Research Center's research into Xerox's Alto computer (Xerox Alto) user interface, a set of reusable controls that contain general information are now emerging. Different combinations of regular controls are usually packaged in the part toolbox, and programmers can build graphical user interfaces (GUIs). Most operating systems include a set of controls for programming, and programmers simply add them to the application and specify their behavior.

Group controls

Description: In order to realize a certain function in the product independent of the module, its characteristics lie in a relatively single function, in the structural layer and behavior layer should have a strong reusability, in the presentation layer should be consistent and user-friendly identification. Multiple combinations of controls can be derived from a single control to accommodate different functional operations, such as uploading a combination control and a list combination control.

Define dimensions: Control descriptions, control gestures and dimensions, user feedback, design concepts, control applications.

You love, or do not love; the norm is there;