Introduction to Web product design ideas

Two years ago, I saw "Emotional Design". The author divided the design into three layers: instinct, behavior, and reflection. According to my understanding, the interface, functions, and self-implementation, of course, the interface already contains everything about the product, but I only mean a simple interface level, not the functional level of the interface. The function refers to the features included in the product. Self-implementation is a bit awkward, but I can't think of other words. Use this for the moment. Self-implementation refers, the atmosphere created by the system brings pleasure to users and makes users feel interesting or interesting. The theory of this book is very classic. Unfortunately, I did the development and did not know much about product design. I cannot see the operability of these theories. I am confused and put the book down. Now, I have some knowledge about products and want to record these ideas as my accumulation.

 

A good design naturally looks good. This layer is unquestionable, but after all, this layer is after demand. That is to say, you must first have a function to design the interface. First, let's talk about functional design. What functions are used as good functions? For users, it is naturally the most desired and easy-to-use feature for users. When talking about this, you must first understand who your users are? The whole process is very important. If you don't even know who your users are, you can only guess that it is good to make a product that meets your needs, but this possibility is too low, therefore, the first step is to find out who is your real user. Here we talk about the difference between users and customers. Customers mean to pay for you, users refer to people who actually use your system. Once you understand the real users of a product, it is easier to do more. You can use various methods to communicate with the user to learn about the user's ideas and extract the target or task that the user wants to use your product, if you want to listen to users as much as possible, but not to say that all users listen to users, your own value will be lost. After communicating with the user, I have understood the user's goals and the data involved in accomplishing these goals. Now I have to start analyzing these goals, try to break down these targets into several tasks. if the task is large, you can split them. The final result is that the tasks cannot be divided into smaller tasks. After the task is analyzed, you can analyze the data involved in the task, extract metadata, and classify the data. This classification is very important and can be extracted using card classification or other methods.

 

Various tasks and user roles can be analyzed by means of brainstorming and other methods. After obtaining user roles, you can create specific typical user roles as a reference, these specific user roles need to be specific to the name, age, and occupation, and the more specific the better) to form a task path diagram (this figure is your website path diagram ), then, the function modules are grouped based on these tasks, and all the functions of the system are composed of each module. These paths are just block diagrams. You need to turn them into pages. After all, the pages are composed of one page. That is to say, you must break down the tasks in the block diagram Into one page, chain your system. An independent task can be created on a separate page. For a non-independent page, you must fully consider the relationship between each user and the steps of the tasks they need to complete, combine similar tasks into a single page.

 

After analyzing the page, you should consider navigation. The navigation here has a lot to do with the classification obtained from the above analysis. You can directly use this category as your global navigation, then, you can analyze and analyze the relationships between data. You can build your associated navigation by analyzing the results (associated navigation refers to the user's current content associated with more content, for example, if a user reads information about a book on a website, the information about popular books of the same kind is associated information, you can design a sketch based on the obtained page and navigation, and then design the page effect for the UI Designer to form a page. The level of the humble servant is limited, and the self-implementation level design has not yet been thoroughly explored. Finally, let's summarize this process: