Traditional enterprises need UI consistency engineering more

Sometimes the UI design of some products is very delicate and praise on the Internet. However, these products are often Internet products. The products of traditional enterprises are just the opposite. Their UI is spit out and cannot keep up with the times. Traditional enterprises also have the demands of optimizing experience, but they are facing difficulties in the inconsistent pace of action. The author of this article analyzes the UI of traditional enterprises and shares it with you.

The degree of ignoring the product experience of traditional enterprises is unimaginable by Internet companies, so that roughness can be launched like a DEMO version. "Functional first" is not an exclusive concept of traditional enterprises. Internet companies are also features. The difference is that Internet companies are equal emphasis on "functions" and "experience". Traditional companies are "functions".

Traditional enterprises also have the demands of optimizing experience, but they are facing difficulties in the inconsistent pace of action. Under the circumstances of the construction period, simply improving the requirements for front -line developers is a matter of promotion. UI consistent engineering may be a direction for traditional enterprises to solve this problem.

1. What is UI consistent project

When it comes to UI consistency projects, many people may not know much, but when it comes to componentization, I believe many people are more familiar.

In the past, we said that componentization often refers to the development side, and usually refers to the front end, so componentization often refers to the componentization of the front -end code. The front -end code componentization is to extract some style code with a higher duplication rate in the page and make them into code components. In this way, when you encounter the same or similar style of development, you can use it directly instead of needing it without needing it without requiring it. Starting from scratch, it improves front -end development efficiency to a certain extent.

So what is the UI consistency engineering? What is the difference between it and the front -end code component?

The front -end code componentization usually only involves the development side, does not involve the design side, and its main purpose is to improve the efficiency of the development side. UI consistency engineering can be roughly believed that it is a relatively large upgrade of the front -end component. A single efficiency of the development side.

UI consistency engineering, the more important proposition is: how to maintain the consistency of UI. Between multi -business lines, multi -scenario, multi -channel multi -terminal, multi -departments and multi -project teams, if you want to maintain the consistency on the UI, convey a unified visual style and brand logo to the company's internal and external users. It is a dream that looks too luxurious. Its cost is extremely high, so that it seems that it is out of reach. As far as the designer as a visual source alone, the management and compliance of design specifications have become unsatisfactory. Under this background, the UI consistent project came into being.

To maintain the consistency of the UI, the important mission of the UI consistency engineering is: the unified implementation of design specifications. This implementation includes both the implementation of the design team, the implementation of the development team, and even the product team can be included in.

The design team that guarantees the design specifications through the UI consistency engineering guarantee can well implement the implementation of the design of the design and the management and limitation of design resources. The first task of UI consistency engineering is to component design specifications and design resources. By creating a side component and sharing reuse in the design team, it not only improves the design efficiency, but also avoids invalid innovation to achieve design unity. Through design resources, the entire design team maintains a unified design style, reduces misuse and abuse, to maintain consistency of experience.

Through the UI consistency project, the development team not only makes the previous precipitated front -end code component more standardized, but also includes the specified code of design resources. Through the reuse of component code and resource code, the UI design is more effectively landed, and the development of development is improved. There is no need to repeat the investigation and return frequently to form a closed loop of the design-development process to improve reuse and development efficiency.

UI consistent engineering is extracted through global variables and component associated variables, and the definition of design and development aspects has greatly reduced the cost of quickly realizing visual optimization, design upgrades and updates. It is difficult to achieve demand that is difficult to achieve.

The convenient connection between the design component and the development component plays a pivotal role in the actual design and development work on the subsequent projects. We have completed the componentization and resourceization of the design, and the component code and resource code are also completed, but if there is no convenient way to find the correlation method of the corresponding code fragment on the design draft, it will face a situation of losing money. Too much, the harder it is to find later. A collaborative platform that can automatically identify and code associations in design components and design resources in the design manuscript is essential. It is a vital part of the UI consistent engineering. With this platform, developers can directly see the designer's design drafts to directly use the created components and resources, and click to directly view the corresponding component code and resource code, which greatly improves the development of development. For reuse efficiency of component code and resource code.

2. The significance of UI consistency engineering to traditional enterprises

Traditional enterprises have insufficient attention to product experience, and lack of professional talents in products and design. Under this background, the existing product experience is unsatisfactory. Pay attention to functional development for a long time. In order to meet the fast launch of the business, it is difficult to implement the unified design specifications. During the development process, the problems caused by the lack of the UI's lack of standards are constantly prominent, which is mainly manifested in three aspects: due to the lack of standardized design specifications or implementation of the UI lack of standardized design specifications or implementation The design specifications are not effective. The design styles are not uniform on different products/systems and different development language platforms, and the user experience is inconsistent. At the same time, the design resources and code lack a unified management method. The component code is fragmented, there are multiple development, the quality is difficult to guarantee, the code API of each end is not uniform, the maintenance and expansion costs are high, it is difficult to change the theme and adapt to DARK MODE and other needs. Repeat the investigation and return frequently. Each time it is put into production, it is necessary to verify the quality and reduction effect of development. After the modification, it is necessary to confirm again. Because the efficiency is relatively low, the cost -effectiveness of the work of improving the product experience is relatively low. After the product manager enters traditional enterprises, the first thing that assumes is the heavy responsibility of the product experience optimization, but after a period of time, it will gradually discover that the layers of tasks on the shoulder's burden are only the controllable tasks of your own. Completed, and then you will encounter difficulty in promoting. Related demand for product experience optimization is always dragged by functional project needs. Even if the leader personally launched the task of experience optimization, it is difficult to resist the existing KPI evaluation system and business and development team's inertia thinking and habitual actions.

Combining the business operation scenarios and actual needs of traditional enterprises, the lack of systematic tools that effectively improve the product experience may be the key to the problem of product experience. UI consistent engineering may be a banner that product managers can rely on.

With the help of the UI consistency project, the product manager can not only solve the product experience problem of the product/system, but also use it to use it for other project teams. It is an integrated UI solution. Traditional enterprises are directly facing customers' technology products, and they can still reach a good level through the individual dense configuration of manpower, the degree of attention of the product experience, the increase of sensitivity and the improvement of development. There is basically no way to concentrate and improve the overall improvement of experience problems. It relies more on each team itself, unless relying on the overall project of UI consistency.

Before putting aside the corporate environment and human resources, the implementation of UI design and design specifications alone should also improve efficiency. One page one page draws, a element of one element design. Although each designer also has a set of its own design library, it is far from enough. There are still many links that can be improved and improved. Atomic theories of atoms, molecules, tissues, templates, and pages of the professional foundation of design, the design specifications should be compuied and resource -based in accordance with this theory. Speaking of this, I have to sigh that the development side is ahead of the product and design side in sharing, reuse, and collaboration. In terms of time, breadth and depth, this is the case. Perhaps this is because the product and design side have always emphasized creativity, innovation, and the development side is more pragmatic. It emphasizes efficiency and construction period.

Having said so much, in the final analysis of the UI consistency project, the problem of two aspects, one is the consistency of the product experience, and the other is the improvement of R & D efficiency. We must always recognize this in the large and complicated large projects of the UI consistency, and always seize these two key functions, and we cannot lose our own direction.

The research and development efficiency here includes both the efficiency of the development side, the efficiency of the design side, and a little efficiency of the product side. The efficiency here is more reflected in the work efficiency of UI designers and front -end development, and the cooperation efficiency that the two need to cooperate with each other, such as development reduction and UI check. Because the main work bottleneck of the product manager is not the output of the product prototype, it can improve a little efficiency. In addition, there is a little internal logical relationship in the consistency of product experience and the improvement of R & D efficiency. This logical relationship is: UI consistent project must first achieve improvement of R & D efficiency to further promote the consistency of the completion of the product experience. This is very important in traditional enterprises. Any improvement from the development of products and experience is not attractive enough.

The construction of the UI consistent project can help the design team improve the design efficiency, precipitate design language, and reduce the burden of investigation; so that developers can focus on business needs when facing new projects, without having to consume time consumption on components; reduce Test the workload of classmates to ensure that the quality of the control does not need to return to the test; help business classmates and product managers improve the iterative efficiency of the version and the volume of version requirements, and improve the rapid expansion of business.

Although the UI consistency engineering will increase the workload of developing students on the ground, it is also a difficult task to promote consistency construction. Due to the high cost and failure to quantify the assessment income, many teams have not achieved the expected results in the end, but once valid is valid, it is valid. After the operation, the team will get a generous return.

Third, besides UI consistency engineering

With the UI consistency project, can it solve all problems alone?of course not.

Although componentization and resourceization are a good way to take effect and unified experience, we cannot excessively strengthen the use of components and resources during the design process. It has lost the possibility of design innovation. Instead, in -depth awareness of product value2. The overall review of the design plan to make decisions to achieve the balance and value of the two.

Columnist

Thick, WeChat public account: thick language and text, everyone is a product manager columnist.Many years of cross -border product manager of Internet and traditional enterprises.

This article was originally published in everyone's product manager.Reproduced without permission

The title map is from Unsplash, based on the CC0 protocol

The point of view of this article only represents the author himself, and everyone is the product manager platform that only provides information storage space services.

- END -