As a UGC-based product, Pipi Shrimp makes executive list users "addicted" with its colorful and interesting content, and has won praise and continuous executive list use from many users. So what is the product architecture and logic behind this product? How did they support this interesting product? The author will analyze it carefully. An overview of the documentation 1.1 Document Properties 1.2 Product Overview 1.3 Requirement sorting 2. Product description .
Functional permissions 3.1.1 Login/Not logged in executive list Logged in users can browse all interfaces and activate all functions. Users who are not logged in can browse posts as tourists (can't reply, can't insert eyes), watch movies (can't reply), watch live broadcasts (can't speak), go executive list shopping in the mall, play mini games, use mini programs, and use the search function. 3.1.2 Ordinary users/appraisers users Ordinary users only have the like function.
The user of the God Review Appraiser executive list has a one-click "Send God Review" function, In the registration and login module, the end user executive list has to go through the process of binding the mobile phone number. The authenticity of the bound mobile phone number, user information and traffic data is greatly improved, which lays a solid foundation for the product, operation and other departments to make further decisions.