System development in the perspective of designers

Intermediary transaction SEO diagnosis Taobao guest Cloud host technology Hall

The company has been developing a system for some time, the function has been a number of customers affirmation, but the interface is not good to see has been a big problem, so the first two or three weeks specifically to do this improvement. Faced with the design of N-interface, n++ a miscellaneous, broken, messy page finishing, is really a headache thing. Luckily it's all done for the two or three weeks of busy summing up a few points.

First, a brief overview of the system interface beautification of the workflow

1, the preparation stage: Familiar, look at the system-related documents, the system has a general grasp, not design a dead end, estimate, probably summed up the need to improve the detailed page problems;

2, the facilities Stage: design, design system needs to beautify the key interface, specifications, the layout of the display structure, standardize CSS, modify, participate and guide the program developers in strict accordance with the formulation of good structure, specifications modify the page, this process is quite cumbersome.

3, review stage: Fine check, such as the transparent background of the icon, pop-up box size, and so on; remedy, manual for each interface simple operation, summary remedy left-behind problems;

In fact, many programmers pay attention to product function development but ignore the interface ease of use and aesthetics, resulting in the development of the product roughness, unsightly. They forget that system development is for human use, the inconvenience of operation, ugly, the same will not let users. But if each development is to let the interface designer to make up, for designers, programmers are very tired. It is better to incorporate the presentation layer early into the development agenda.

To provide some suggestions for system development from the perspective of designers

First, the designer must participate in the system design.

The role of designers should not just be a single interface beautification, on the other hand, if he does not understand the development of the system, his perspective will be very low, can not stand in the system of the height of the overall design ideas, a dazzling interface can only solve the surface problems, is not to solve the deeper problems. Mars thinks this is probably the difference between art and designer.

Recently looking at Jesse James Garrett's "Elements of User Experience", which spoke about the user experience of the five aspects (such as the figure): Strategic layer, scope layer, structure layer, frame layer, performance layer. Mars appears that the first two levels of designers must fully understand that Mars in the development of this system to ignore these two points, so that the latter to make up work, the latter three levels of designers must be directly involved, out of the interface, set norms and so on. In this way, the system design, development will be "one" road smoothly, not to take the "Z"-shaped road.

Second, the Design System Key page effect chart

Mars found that the effect of the map must be fully understand the premise of the system, so that the design of the interface can be interpreted on the page system, and not just pay attention to the crystal effect of a button or something. In this link, designers need to be responsible for system development, testers (here play the role of "user") Full exchange of communication, from the future expansion, ease of use, aesthetics and other aspects of the design. Compared to the development of the program, the plot or the small cost of things, in order not to take the "Z"-shaped road, these interfaces must be carefully weighed.

Third, the designer assists the program development person responsible design development specification.

Among them, designer assistance may include, System directory architecture, facilitate future style replacement, display page, page layout of the program structure, name specifications, layout structure tags, CSS style, picture-related name specifications.

The above work and the relevant specifications of the proposed, for future program development provides convenience, style this piece, just apply the general structure on the line.

IV. System Development Personnel Organization

Requirements of the system developers strictly follow the design drawings and specifications to go, do not only focus on their own development of that point function, the code structure is not clear, the style in the page head, labels everywhere defined are, consider how to do after the revision, can not be thousands of pages to rewrite it. System development is not likely to one or two people, many people collaborate without a standard for reference, each in their own thinking to write the program eventually come out of the system may be rough, disorderly.

Above four points is the Mars in the designer's point of view on the system development of some suggestions, if you want to make the system fine, suggest a reference.