Does Luyan Information need to know how to code for zero-based learning UI design?

  Recently, some partners who are studying UI design often ask me a question, do I need to know code to learn UI design with zero foundation? If I don't know how to code, will I not be able to find a job in the future? Today, I will give you a detailed answer to this question.  
  First of all, we need to know what is the scope of work as a UI designer?  
  The UI designer mainly works around the user experience and the visual design of the interface. His responsibilities are mainly the research of the aesthetic habits and trends of the target users, the setting of the interface style, and the art production of details (the workload is mainly concentrated in this area. ), the elaboration of product character and the expression of emotion.  
  Nowadays, the division of this job in China is also quite chaotic. In many large companies, UI generally refers to interaction design---design for product and system behavior, find demand, analyze competing products, do information architecture, and draw high and low fidelity The kind of prototype, because of the cost in a small company, the UI may have to do both interaction design, visual design and front-end.  
  So we can get some answers from it. If you are a UI visual designer, then you don't need to learn code programs! Today's Internet company UI design is to work side by side with developers to make projects with beautiful visual effects and satisfying functions.  
  When several professionals work together, partnerships are important, and people pay attention to who is more skilled. But how should this boundary be drawn? It all depends on your personal ability. Those who are skilled at making beautiful web should be able to understand even very little HTML/CSS content.  
  So to what extent does UI design need to know about code?  
  This varies from person to person. Because it is impossible for everyone to master all the skills, how much code you need to know is mainly determined by the need for code in the aspect you focus on. But on the whole, if you are interested in this aspect and have the ability to learn, my suggestion is that the more the better.  
  So how to learn it? The first and most important thing is to understand the "technical feasibility boundary".  
  Two main ways to know:  
  The first is to read some programming books. I especially suggest you, when you want to do some Android or iOS design, you can find one or two books in this field, read them or read them quickly, and then you will know which ones are available. Controls, methods and basic common sense. The process can be over quickly, and we've all done it before.  
  The second is to look at a large number of products and see what functions or effects the current products have achieved. In fact, there are basically no difficulties related to UI at the technical level, so as long as you look at the effects in other software and how they are realized, after you read more, you You will find that, in the same way, these things can be realized in my design, or can be made soon. It's also a great way to understand and expand the "frontier of feasibility" of what can and can't be done.  
  In addition, there is another very important aspect, which is the cooperation between you and the development team when you are doing some specific designs. Because every point of design you do has different requirements related to technology when it is implemented, so at this time, it is necessary to have a particularly in-depth and close communication with engineers at work. Especially when you are doing work related to interaction or product design, you need to constantly communicate with engineers to understand whether your design or idea can be realized. If it is not possible, you need to know where the difficulty is and how to make it feasible.  
  After accumulating in this way, you find that you gradually understand a lot about technology. You may not be able to write code, but you will understand more and more things, which is very good for your knowledge accumulation. In this aspect, there is another point that needs to be paid attention to, that is, to ask more questions, and to ask questions with technical content, because some simple questions can be quickly made up by reading books, and only some related fields and business , Code, specific projects and other closely related issues are the ones that you need to pursue and fight and are not ashamed to ask.  
  You don't need to learn the code, but it is best to learn about it! Because your work can’t just show off, but also have to be considered by the front-end, whether your work can be realized, and what effect it can achieve is simple and individual, otherwise it’s useless if you can’t make a bunch of things, so , It is definitely beneficial to know more about this aspect!  
  There are also a lot of sayings on the Internet, but the summary is probably "UI design can not code, but this is a highly competitive industry. What you know may not be used in work, but it is a plus for you." sub-item”;  
  if you are doing development, then you also need to learn UI design. After all, you often need to communicate with UI during the development process. If you don’t understand anything, communication will become a bit laborious. The reason for your skills outside of work.  
  When you are struggling to learn a technology, it means that it is already relevant to you, so go learn it, but learning it does not mean you have to change careers, I The meaning is that it is better to start learning directly than to spend time worrying about whether to learn or not. You can learn skills other than work, but you should understand.  
  In fact, what an enterprise really needs is a designer who can really do a good job in design, a developer who can write good code, and designers and developers can collaborate seamlessly. It doesn’t matter whether the designer can code or not, but the designer needs to understand the workflow and principles of development and code, so that they can communicate well with the developers and make the work more efficient.