Shulou(Shulou.com)06/03 Report--

This article mainly explains "what is the whole process of UI design". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what is the whole process of UI design".

Design flow

The fragmentation era makes it very easy to distract attention, and intensive projects are often multi-threaded. A clear design process helps us to allocate time and energy more reasonably and improve work efficiency. I usually divide the project design process into three parts: before design, during design, and after design. Of course, many designers will divide the design process into requirements collection, goal setting, prototype confirmation, design review, detail polishing, follow-up development, result tracking, and so on. In fact, the details are all the same, but I divide the whole design process into three milestone-like nodes, which are easier to focus.

1. Before design

The link before the design is the most easily overlooked key link, we are easy to fall into the misunderstanding of starting the design as soon as the demand comes, but we do not realize that doing so will leave countless holes in the follow-up work. for example: repeatedly modify the design draft, the demand side temporarily add a few pages, design delivery delay, the effect is not as expected, and so on, which slows down the pace of the whole project and deviates from the original intention. "pre-design" is the most difficult and important stage in my design process, so at this stage we must find a way to buy time to prepare, so what do we have to do?

Have a chat

The first thing before the design is to understand the business, pull up the demand side and ask him to talk about the project background, business objectives, user groups, competitive product analysis and association with the existing business, which has a lot of benefits. On the one hand, we can understand the most real demand and product objectives through the description of the demand side, so as to facilitate the decision-making in the follow-up design; on the other hand, we can inversely require the demand side to sort out the business objectives more thoroughly to avoid mistakes in the general direction. Finally, it can also let the demand side know that we are also thinking towards the business goal, which is more conducive to the long-term cooperation and trust with the demand side, rather than making the demand side feel that we are just a page.

see

After the first communication with the demand side, the next step is to see if there are any related competitions. If there are competitive products in the project, then these competitive products can quickly see the whole picture of the future of the product, and also allow us to find some bright spots and think backwards about whether there are scenes that are not covered by our products. These contents will be sorted out as an important basis for future design. If there is no direct competition, you can also take a look at products of the same type or industry.

Think about it.

With a chat and a look, we basically stand in the overall perspective, but it is not yet time to start the design, we still need to think about it, such as: A. Combined with my findings in the process of looking at the competition, are there any questions about the business and demand? Collect the question points and find the demand side again for confirmation to ensure that the understanding is consistent with the demand side, so as to ensure the smooth progress of the follow-up design process. b. What are the opportunities for the designer of this project? What is the design goal? What are the areas that designers can focus on? What is the cost of development landing? Can the design input be verified? This will help us to better allocate the focus of time, but also facilitate the precipitation of follow-up design experience, and know which designs can bring changes in data. c. Think about how the design is planned? What are the other design risks? Do you need external support, etc.? It is convenient to help us to give a relatively accurate design schedule.

two。 In design

With the full preparation in front, you can basically start the design with confidence, and then follow the following process step by step:

Prototype design

Before visual design, we need to constantly polish the interaction prototype to ensure that the experience at the interaction level is elegant and in line with user habits. If the team is equipped with an interaction designer, you can have some discussions with the interaction students, reconfirm with the demand side after finalizing the prototype, and align the opinions of all parties; if there is no interaction designer involved, then be sure to graphize the ideas. so that people can understand our ideas more accurately, which can be drawn on paper or expressed with prototype tools. At the same time, it is strongly recommended that designers should be highly sensitive to the information architecture and copywriting, a good information architecture can ensure the smoothness of the basic page experience, and accurate copywriting can better ensure that users do not deviate in their understanding of information.

Style exploration

After finalizing the prototype, we can explore the style. I personally understand that this part of style is quite perceptual, and there is no standard answer, as long as the definition of style is based on and pays attention to the current popular trend, there is basically no big problem in setting the style, and we can also do targeted design according to some opportunities prepared before design, such as illustration, texture, details, dynamic effects, and so on.

Detail polishing

When I look back at my previous design output, I often find that there are a lot of things I don't like. In order to avoid this situation, we can try more and polish more in the design stage. Instead of letting the "future me" or the demand side point out the problem, it is better to examine yourself first and polish out the most ideal plan before making a review. You can also take a look at your colleagues and friends, invite them to choose a plan and give a reason. Finally, the final plan is output with the combination of design goals, business objectives and everyone's opinions. If you encounter difficulties in the plan, you should communicate well in time or ask Leader for help.

Design review

A formal review meeting can be organized when the plan is agreed upon within the team. Design review can quickly focus on the discovery of problems, and can effectively avoid the situation of disagreement and delay in finalizing the final version. We should be fully prepared before the design review, and we can ask the upstream and downstream key roles to participate, such as the demand side and R & D personnel. Preset the problem in advance to manage the expectations of all parties to ensure that the plan is rigorous enough and good control field. In the evaluation stage as meticulous as possible, the designer wants to land the small details, small bright spots are clearly mentioned, causing the attention of R & D personnel. Finally, the conclusions reached by the review are documented to avoid wrangling during the follow-up design acceptance.

Establish Kit

At the beginning of the design scheme, it is necessary to consciously sort out the specifications and components to ensure the efficiency and consistency of the subsequent functional iterations. Summarize the basic specifications through the key pages; through the continuous deliberation in the design process, extract the interface elements again to form a component library.

3. After design

After the design review is passed, in addition to outputting the design content and filing the design documents, the next thing to do is basically to promote the design landing and design verification.

The participation of designers in the design landing link is very important, and all the previous work is ultimately based on the on-line effect, so in order to make our efforts without discount, we need to adhere to the design acceptance carefully to ensure that the design effect is perfect. In addition to urging the developers to make adjustments and marking the design details more clearly, the complex interaction outputs an animated demo, which can help the developers to accurately understand the design intention.

There are many ways to design and verify, such as data burying points, user feedback, online inspection, user interviews, usability testing and so on. Sometimes we ignore the link of design verification because of the busy business requirements, the data is not buried, and we do not want to do verification. These reasons boil down to the lack of attention to design verification. But design verification can help us review the achievement of the original goal, find the existing problems, and become the basis for the following iteration; at the same time, it is also the accumulation of our own design experience. So we should still pay attention to design verification, and if we work hard, we will see the results, for better or worse.

Thank you for your reading, the above is the content of "what is the whole process of UI design". After the study of this article, I believe you have a deeper understanding of what the whole process of UI design is, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.