When making interactive prototypes, it is often easy to overlook some details, leaving pits. When the development stage is picked up by the RD brother, the professional level will be questioned. Therefore, when prototyping, more Pay attention to details.
I have been very busy recently, and the APP in charge has just upgraded to a major version. I have always felt that people can’t always work with their heads down, and they have to take time to look up at the road. Therefore, when I returned from climbing the Fragrant Mountain on the weekend, I decided to summarize some of the pits I stepped on when designing products, that is, some details that need to be paid attention to.
1. Information Management by Role
Different roles see different content, even in different states of the same role. For example, the content accessible to visitors, first-level members, and second-level members may be inconsistent. Therefore, when adding any new function point, it is necessary to mark clearly which roles the content is open to, and whether the displayed information is consistent.
2. Abnormal situation
When designing products, abnormal situations are often more complicated than normal situations, so we must consider all kinds of abnormal situations comprehensively, and give an interactive design diagram of the product at the time of the abnormality. (Gray is often important, otherwise RD brother may develop ugly interactive prompts)
3. The display of the information list: There are two situations: no data and data
For example: log in to the short book to view “my attention”:
Situation 1: Without any dynamic information, the product design has to consider whether it is necessary to prompt the user to pay attention to more people or other
Situation 2: There is dynamic information. In addition to considering how to display each piece of information, product design also needs to consider whether the information needs to be paged, how to interact with pages, and how to prompt users when the information is displayed.
4. Time display: year, month, day, hour, minute and second
For example: the publication time of the article on the homepage of the short book:
1. Format: directly display the publication time point of the article, such as 13:15, or display 3 hours ago, depending on the usage scenario of the product.
2. Accuracy: The accuracy requirements for different time periods are different. For example, the first occurrence will be accurate to the second, but the one day ago only needs to be accurate to the day.
5. Default prompt copy
For example, when the input box loses focus, what information needs to be presented to guide the user to input.
6. Closed-loop inspection of complex processes
If the logic of a certain part of the function is complex, you may wish to draw a complete flow chart and consider the circulation in various scenarios.
Summary: Every PM needs to be responsible for every detail of their own design products, because if they are not fully considered, it is very likely that the products developed are also incomplete, or they will need to spend more energy to remedy them. The above are some of the pits that I have stepped on in actual combat. I sum it up. I hope I will not make the same mistakes in the future, and I hope it will be useful for everyone.
