Forum Posts

ziaur3 ziaur3
Jun 15, 2022
In Wellness Forum
As a product manager, I often encounter some bugs when I experience the product. At this time, the developer will ask if the bug can be Whatsapp Database reproduced by recording the screen. Take the most commonly used news feed as an example, you found a problem with the same feed before (such as UI dislocation, data confusion), etc., but you can refresh the feed again and there is no problem. [Step 1] Found a bug in Feed 1 [Step 2] Scroll Whatsapp Database down to see other content [Step 3] Brush back to Feed1 and find that the bug is gone At this time, the scene will be very embarrassing. The developer thinks that you are looking for something, and you did find a bug just now. With the above problems, we need to learn how the feed flow itself is implemented. We have a basic consensus: every feed needs to be created in order to be displayed. Let's think about it, since the feed needs to be Whatsapp Database created, what are the possible Whatsapp Database timings for it to be created? 1. When I swipe to n pieces of content, the page immediately creates n feeds This is the most intuitive and simplest: But a one-time creation operation is not advisable. You must know that every time you create a feed, you need to consume memory (it can be understood that every time you buy a bag and put it at home, the space in your home will be much less). For products like Toutiao, Zhihu, and Video Accounts, you may have watched hundreds of content after half an hour of reading; if the mobile phone also created hundreds of feeds at this time, then as you use it for longer , the more feeds will be Whatsapp Database created in the mobile phone (more and more bags are bought), the memory space of the mobile phone will gradually run out (the available rooms at home will be less and less), and the mobile phone will Whatsapp Database become more and more stuck until the memory is completely Being occupied and stuck (run out of space at home).
Reuse Mechanism for Whatsapp Database content media
0
0
2
 

ziaur3 ziaur3

More actions