At the page form level, we analyzed and reconstructed

[rifattryo.ut11]

Therefore, we worked with the business team to formulate relevant iteration plans based on the design goals of "efficiency", "brand temperature" and "consistency" and the results of multiple rounds of small iterative experiments in the early stage. Transformation form: committed to making it easier for users to find and make decisions, while taking on the demands of business information distribution. Experience Renewal: Combined with our new "simple, beautiful, lightweight, consistent" brand tone, we are committed to creating a more comfortable and friendly user experience for users. Explore new distribution space: Explore new distribution space and distribution style to help businesses achieve the goal of active distribution.



3. Exploration and implementation. Renovation israel phone numbers of form the large container framework (message center, personal center). ) Card Based on the experience of previous experiments "Flow Design Data Experiment" and related experimental data, we have clarified the problems to be solved in this revision: card information overload, visual flow confusion, and unclear key information of business cards. We further sorted out the key information of each major category of cards and deleted unnecessary information. In the future, the original mixed information arrangement method will be adjusted to the key information clustering layout method, and then the feature points will be enlarged.



The total card experience and data have been significantly improved. ) Message Center As an important entrance to promote conversion, we use the disassembly strategy. We clearly divide the message list from the original single list layout into the head atmosphere area, shortcut area, bulletin board, list area and permission notification area. The list area clearly groups new messages and historical messages. ) Personal Center We use the subtraction strategy for the personal center. Clarify the core goals of the product and remove redundancy; consider the function configurability and streamline the interface. The head focuses on the user's core information and assets, and then the common functions such as publishing are traced back.