It will lead to a lack of logic in the function. The reason for the frequent bugs is that the product design is such that the product quality is greatly reduced, and job function email list there will be "unreasonable" voices from users. Why make unreasonable demands? Why does the function lack logic? It is because the product manager lacks basic knowledge in the computer job function email list field, such as the development mode of front-end and back-end separation, front-end and back-end interaction capabilities, data structure, differences between different clients, network protocols, operation logic, performance impact, etc.
Case in point: For software product job function email list managers, there is the most common "search within a list" feature in software development. Today, you are faced with the search needs of small data volume, and users want to be able to search in real time, and the search job function email list can be completed even when there is no network. If you understand some basic computer knowledge, you will come to this implementation plan: the search can be completed even if the network is disconnected,
Then we cannot initiate a request to job function email list the backend. And our small amount of data means that data on the front end will not affect performance; real-time search job function email list can be transformed into "front-end filtering" (just an example, for most search scenarios, it is not a good choice to do it in the front-end). If you understand some technologies better, you will then ask questions like this: If the data is updated, doesn't it mean that the front end has to be released every time, how to solve it?