After thinking about the sharing of interactive knowledge for a while, it should be expanded into a whole series of content, including the analysis of various components, controls and behaviors.
Based on my sharing habits, I will try to avoid using too theoretical or vague ways to explain, but focus on specific actual combat scenarios to help everyone understand how to make reasonable Number List interactive decisions.
1. What is the global framework of interaction
Interaction design is essentially the process of designing how the product is used, how to fill in the account, how to export the form, how to filter the data, how to sort the list, etc... For the use of each function, it can take a long time to consider its rationality. The interaction of a project is the sum of the ways in which all the features of the project are used.
So how does a designer start the interaction design of a project? Go directly to the details and start to follow the prototype to formulate the state of the input box and the expansion logic of the drop-down menu?
This is definitely not possible. The interactive content of the project is numerous and complex, and the designer will quickly get caught up in these minutiae. It is easy to cause lack of unity of project details, inconsistencies, and fragmented experience.
Therefore, to understand the correct idea of project interaction design, it is necessary to know what interactive content is in the project, and what are their corresponding levels and design objects.
Here, I divide the interactive objects that need to be designed into 4 categories, which are in descending order: