Focus on design details: A good web design can better reflect the quality of the product

There is a very difficult problem in the work, interactive designers and visual designers to make a high-fidelity prototype submitted to the front-end development engineers, the end of the Web products from the details and layout and the High-fidelity prototype has a gap, such as the mouse hand-type where there is no mouse hand type, resulting in users do not know this can point, or a line of text up and down uneven, looks very cheap without quality sense. Cause interaction and vision have to put down the work to one by one check these problems, and pointed out to the front-end development engineers to make it correct, and finally found that these problems can be quickly done, then why the front-end development is not willing to do this at the beginning of the work?

To look at this problem in several ways:

1. Meticulous professional to kill off the "tacit understanding." Believe that most of the people who have some Internet experience have done front-end development engineers, in that era from design to development are the same person, so the completion of things often and the expected degree of compliance is higher. Because in the front-end development of their own heart know where should be bold, where there should be spacing, which should make users more prominent to see. But now the division of labor more and more thin, each type of work more and more professional ability, so that the original kind of "tacit understanding" also more and more disappear. The front-end want to do is to write the code of Cow B, preferably to be able to exceed the technical level of Google products. But often the more professional the more deviated from the real purpose of the product. In a previous discussion, a front-end colleague said that the neat code was more important to them than the pages the user saw. I do not object to the code neatly embodies the professionalism of the front, but in a word, the code is neat is the basis of the front-end, the requirements of the front end is no matter what users see the page is more complex, how gorgeous, your code still want so neat, this is the most cow B.

2. Wait for the communication. In order to ensure the quality of the project, the product will usually be delivered to help each role communicate. I have also been "committed" to developing and update all kinds of specifications, but I found that no matter how detailed your product is, it will always consume a part of the delivery process, resulting in the back-end role is not complete to truly understand your original intention. Fortunately, in the process of passing the meeting to increase the form of communication, but a meeting for all to understand and make recommendations is not possible. What else can we do besides product delivery and meeting? What we need is active communication. There are words in the work, can use IM, never use the mail, can use the telephone, never use IM, can communicate face-to-face, never use the telephone. This is the best way to communicate, of course, experience tells us that after each communication, we must use the message cc all people to make a communication record, so that everyone is too much to forget the last. But communication will cause a problem, the front end, vision is often waiting for interaction and demand side to find their communication, that is, the post role has been waiting for the role of the predecessor to find their communication, in fact this is wrong. The so-called communication is mutual, don't wait! When the post role found the problem should be proactive and timely to find the corresponding predecessors to solve the problem, such a way can be sure to make up those doubts and uncertainties.

3. Not unified product idea. In each field of professional roles, everyone is saying go forward, meaning not to stay at the technical level, to go far. From backstage to product planning, we all have a tendency to move forward. Of course, this is related to the current situation of society, often code engineers will envy the designers in front of even the demand side, as long as the oral said, they will do a lot of work, who want to do upstream. I do not object to go forward, but I hope that we can clear positioning, the so-called forward is the hope that each character's thinking is unified, not only can have excellent professional ability, and can stand in a higher angle to see products, and their professional ability to reflect on the product. Now most people are yelling that we have to go ahead and challenge our upstream expertise, but I want to ask these people, are your own professional skills good enough? If you don't notice even the most basic web usability (such as mouse-hand-clicking, alignment between elements, and large area instructions to help users find goals, etc.), how can you go forward and how you might be able to apply your expertise to the best.

4. No planned technology. The so-called planning, everyone will think of product early market research, in fact, each role should be their own work planning. The problem I often encounter is, the current end of the development engineer finished products do not meet the requirements of the designer, front-end development will always say this what the DOM structure, what JS itself does not support, and so on, and even sometimes need to optimize and upgrade when only found that the front end of the code written dead, there is no optimization, can only rewrite In the face of these problems, there should be two solutions, one is to proactively find upstream to communicate the direction and objectives of the entire product, and put it into the technology, set aside good interface and open structure, so that upgrade optimization possible. Another is to carefully read the delivery product description, see each State and branch situation, when the problem should be found in before doing to others, so that everyone can come together to find a new solution, do not wait until the completion of what can not be done.

5. The details determine success or failure, to reflect the professional ability must be based on the details. First of all, the front-end development does not make the product details on the perfect, there is a front-end colleagues say, to do what they are interested in, they can pay attention to these problems. It is true that writing JS in front of the field is more exciting and motivating than writing CSS. I can only feel that the product is not a game, not because you are interested to do. Innovative things everyone likes, but not everyone can innovate, you just wait for the upstream role to give you exciting work, it can only show that you are not suitable for this job, the so-called innovation is in the professional field to do more than others professional things. In addition, I do not deny that writing CSS more boring than JS, but this does not mean that the CSS is not important, in fact, more often than JS css more important, many web2.0 Web site is to use CSS to guide users, describe products and so on. is not the interaction and visual attention to these layout and details of the problem, in other words, this is the basis of things, should be the front-end development of the engineer's own awareness to improve, so that people pay attention to the problem of more experience. I also hope that these basic areas around the ground, do a good job of the product, do their part, do perfect!

Finally, I would like to say is not to think that web design is rough, good web design is more able to extract the quality of the product, we have to upgrade the experience must be the foundation, the details are processed, we can have the energy to do innovation, to do experience.