Design of elastic window and floating layer in web design

In the tide of transition from traditional software to Webware, design pattern and technology realize double change and advance. We advocate that the task of the page is clear to the user group, the task is few. Back to our traditional background software system, for the face of system and process reengineering. We naturally have to think about migrating the design ideas in Web services to the backend software system. In most cases, this makes the system lighter, more structured, and begins to provide insight and optimization to the user base of the software.

But is there any improvement in the software system that helps to improve usability? Share an example today.

The background is:

1, a page contains a major task and several branch tasks and the page information architecture required to complete the main tasks.

2, the user role is many, the information is big, the page area is limited, only can show the main task the need information.

We face one such challenge:

1, when making a decision on a major task, you need to view the details of the branch task in order to support the decision under several conditions.

2, when making a branch task decision, you need to view the main task information to support the decision under several conditions.

In the beginning, we naturally classify and comb the information needed for the task, and the page is more structured. A lot of use of the presentation Layer scripting language, hoping to make the page smaller, so that the operation more smooth. As you can see from the diagram, change the previous page jump to the current page to eject a mask floating layer. At this point, we found that a problem was overlooked. After the page uses the floating layer, the relationship between the primary task and the branch task becomes the inclusion relationship, and the branch task is in the main task position in other environment of the system, and there is no inclusion relationship between the tasks. In a 3-screen page, the floating layer can do the free information combination, the information contrast and the free movement in the structure of the parallel relationship. But the information is complicated, move the floating layer, drag and drop the scroll bar, floating layer cover the part of the message and other reasons for users to frown on the environment test. The habit of parallel structures, free opening and hiding, irregular contrast and drag is not perpetuated. At this point, if you do not take into account the system structure itself, the use of pop-up layer here can make users more free and unfettered, but also reduce the business expansion and tension brought about by the system adjustment costs, and the current common floating layer will restrict the use of the process.

Measurement of a software system can improve the usability characteristics, it can adapt to a set of software systems. Not only does it need to be viewed from a usability perspective, but it also requires an in-depth understanding of such factors as system architecture, user habits, and technology costs. If it is a Web service product, it needs to be measured more comprehensively.