Ext js and Enterprise Software Interface Design

Because ext JS layout design, basically is to use out of the box, the layout of HTML-FREE, developers, almost do not need to know the layout of CSS technology, do not need to write HTML code, you can make a scalable, cross-browser interface that looks good.

Many people advocate blindly.
I think ext UI should be cautious in some aspects:

1) HTML free does not mean the workload is free. The clear HTML structure is replaced by complicated JavaScript, from form, grid to menu, armed to the teeth, open the page, what we can see is a line of JavaScript code, which completely breaks the front-end design idea of structure and behavior separation. It is not easy to maintain such a page. Considering that the interface is the easiest part for users to change, this cost cannot be ignored.

2) developers use ext's default style in a large amount. The lines on each part of the interface are too obvious and there is no soft transition. A large number of gradient colors are used, and there are obvious signs of stacking. If you don't need ext theme, you need to re-design a theme. This is not a simple process, and you still cannot get rid of ext's disadvantages of panel-based layout.

3) The component method seems to create an interface through the accumulation of blocks, but it is easy to abuse. It lacks flexible design for specific situations and user experience.

People involved in interface design are easy to decouple from front-line users. There is seldom a simple, direct, simple, and persistent design style. The first consideration is not the information organization and user experience, instead, I always want to use it and abuse the color to show my high design level, dynamic, progressive, translucent, sliding door, delay, accordion, and background images, in addition to visual fatigue and complicated operations, these services cannot provide a real user experience.

Traditional design thinking still exists. Many people design menus according to functional modules. During tree menu design, they do not take the initiative to consider users' operation and click habits. At the same time, when the designer sees the interface, he uses the super administrator privilege. Therefore, he can see a lot of menus and functions. I seldom think about the daily operations of real users. Generally, I directly copy a set of controls and often say, "I like QQ and Outlook interfaces. I am... ".

For example, the ext accordion interface is very dazzling. It is generally suitable for users with many features, but it has its own shortcomings.

The menus that need to be clicked most may be hidden. On average, you must click at least twice for a single function. If you are not familiar with the interface, you may need to click each menu one by one.

Users of common workstations perform almost the same things every day. They often reuse and operate a function, and there are not many functions with permissions, at the same time, their work is also the busiest. We should first consider the interface and their operation habits for them during design, provides direct and convenient back-and-forth switching, jump, and navigation for functions, which should be conspicuous, direct, simple, and in one step.

Another kind of user is the manager's Management Decision-Making user. Their time is precious, and it is best to design a silly operation. At the same time, the most critical and important information is stored, organize and place on a screen to achieve the at a Glance effect.