Current location - Music Encyclopedia - Dating - The correct posture of disassembling an app-interactive articles
The correct posture of disassembling an app-interactive articles
For how to disassemble an app correctly, I think we must first understand its composition. Just like disassembling a car, you should know that a car is mainly composed of several parts, such as the shell, chassis, engine, tire gearbox and so on. Similarly, a complete & mainly includes product strategy layer, interactive logic layer, UI visualization layer, development & background layer, and finally operation promotion layer. Each layer can be disassembled for detailed analysis, but as the title, the interactive logic layer is mainly disassembled here.

When we get an app, the first thing we see is UI vision, just like the shell of a car, but what we want to see is its core skeleton, that is, the information architecture. At this time, it is necessary to take out a pen and paper or draw the information architecture diagram in the app in the form of a tree diagram with Xmind and other tools, so that you can have a general understanding of the app.

As we all know, there are a lot of competing products in almost any type of products on the market, so the core functions and characteristic functions are particularly important. Here, the importance of the functions of our team's products is graded (pay attention to the grading of the overall functions of the products, not the grading of each layer of information). This method can determine the core functions and characteristic functions of products, such as WeChat of IM products, instant messaging chat is its core function, and grabbing red packets is its characteristic function (although most IM products can grab red packets now).

At the same time, any app has its usage scenarios, whether on a crowded bus or subway, on a warm and comfortable bed, or on a noisy street ... It will be more helpful for us to understand the product by fully combining the actual usage scenarios and considering the user's usage habits and mental models.

After we summarize the information architecture of the product, we should analyze its logical structure and layout (note that the layout is not UI). In the logical structure, on the one hand, we should consider the "level" and "degree" of product functions. Too deep a level will increase the user's operation difficulty and learning cost; If it is too large, it will cause too much information on the page, and users will ignore some functions when using it. Generally speaking, an operation flow of a product should not exceed five layers. As for the degree, it depends on the product type. As for page layout, this is a matter of different opinions, but in an ideal situation, we should adhere to the principle of user first (as for reality, we should balance commercial interests). Here, personal advice is to appreciate and judge from an objective perspective. Most of the products we disassembled and analyzed have been tested by the market and recognized by users, so their designers also have a great basis for this. For example, Alipay's homepage is neat but as dazzling as tofu, but millions of users are unwilling to use it, and can you say that Ali's designer level is very low? ......

All of the above are just the basis for disassembling and analyzing an app. Similarly, in today's era, micro-interaction has been paid more and more attention. In my opinion, it is also a product's emphasis on "extra points". At this point, I appreciate Netease's products very much, and I have made great efforts in interaction, which is very comfortable to use. Take chestnut as an example: the popular dating software "Detective" in China and the dating product "Huatian" among many younger brothers of Netease have the function of turning over brands, which excludes the objective factors of UGC quality. When you press the user card (picture) for a long time, the user card in the "altar" has no response at the moment, while the user card in "Huatian" has the effect of swinging down, which simulates reality. This unobtrusive micro-interaction will invisibly give users a warm feeling and increase their goodwill.

When disassembling a product, although most of the time we report the attitude of learning, we should also take a look. No product is perfect, and it is impossible to satisfy all target users. So at the same time, we should also bring a few questions:

1. After getting the product and using it for a period of time, can you know the main functions and special functions of this product?

2. Experience the complete process of a core function, whether the process encounters twists and turns, and whether the experience is smooth;

3. Experience a minor but relatively in-depth function, whether it can be found through the information architecture. Doing the above points shows that the basic interactive logic of the product is possible.

To sum up, the steps to be done are: draw an information architecture diagram-analyze the importance of functions-analyze the page structure layout-analyze micro-interaction-experience core functions and secondary functions with problems.

Finally, I want to say that I personally think that the stronger the purpose of disassembling an app, the better the final effect may be. Aimless disassembly is likely to be a cursory tour.

Thank you~