Principles of mobile Internet product design

1. do not consider the web form. All considerations are based on the app.

2. Product priority:

(1) the product must be more interesting than the function. Cool is required for communication and reputation.

(2) functions are higher than interactions. Clear functions meet clear needs, and users do not care about cool interaction effects.

(3) interaction is higher than UI. Convenient and fast interaction is designed first. UI is implemented based on specific functions, rather than a high-quality UI solution.

3. Focus: an app only does one thing. A large and comprehensive app means full mediocrity.

4. Always one-dimensional: to allow users to solve specific problems in one dimension, Twitter's timeline is a good example. A slide menu like Facebook and path is a disaster, because it gives the product two dimensions and makes it more difficult for users to understand.

5. Keep the trunk clear and branches moderate. The product's main functional architecture is the product's skeleton. It should be as simple and clear as possible, and cannot be changed easily, so that users are at a loss. Multiple secondary functions are supported, so you cannot hide them as much as possible instead of placing them on a level-1 page.

6. Do not select a user. There are multiple entries in the same page. The same function has multiple implementation methods. The same interface has multiple display methods. This is a pain rather than enjoyment for users, because they only feel confused and afraid. Users prefer to adopt a long and fixed operation path for repeated operations, and do not want to use a variable shortcut.

7. Hiding Technology will always show simple, user-friendly and intuitive interfaces. Development cannot display functions for the sake of high technology, and products cannot build functions to show off.

8. Reject personalization. In addition to the personalized design that relies on the design features of the app and skin replacement, there is no value in addition to the product manager's illusion of doing a lot of work and self-satisfaction. It can only prove that product managers are not confident in their products, because confident product managers can satisfy users by default. Extended, a good product should meet global user needs without special customization for the region.

9. To a certain extent, the product is intended to satisfy the greed and ignorance of human nature. This is a pain point for users. After the product manager can grasp it, the product manager should surpass it and use the product to help people free themselves.

10. I want to know what I want to do, not cater to my superiors, or please users.

11. category! CATEGORY! CATEGORY! This is the only thing that the product manager should do for users after determining the product's main functional architecture. Classification does not help reduce the difficulty of using products, but helps users understand products and the world around them.

12. Always design around functions and never do it over.

13. The basic functions of a product are not recognized by users, and addition is useless.

14. I 'd rather not do it before I can't figure out a function.

15. Do not allow users to "manage" anything in the product.