How the interface design process of an app is created

Liepewen
Links: http://www.zhihu.com/question/27088793

Complete process, layered design, bottom-up to complete:

1. Strategy layer, define product mission, value, target group
2. Vision/Function Layer: Define core scenarios, feature lists
3. Structure layer: Make flowchart, information architecture, determine main navigation, main menu
4. Frame layer: Comb the contents and layout of each main interface
5. Presentation layer: Visual design, involving icons, color, transduction.

Product managers are mainly concerned about one or two, before you go to find a designer, please ask yourself the following questions to ensure that the requirements are clear:

1. What is the value that the product brings to the user?
2. What is the competition? What advantages do we have in doing this?
3. What kind of user to do?
4. What kind of scenarios will users use this product?
5. What is the biggest bottleneck to complete this product? is a technical research? Experience the shine? Or an operational resource?

Interaction designers focus on the three-to-four, and ask yourself the following questions before you deliver the program to ensure quality of experience:

1. What is the most important task that the interface requires the user to accomplish?
2. Is this the simplest solution?
3. Is the information organized properly?
4. is the design easy to use and at a glance?
5. Is the standard consistent?
6. Can I reduce the number of user clicks?

Visual designers focus on 5, before the Product Manager PK Please keep asking yourself the following questions to ensure less rework:

1. What are the key points to be highlighted on the interface? Did it have an effective prominence?
2. How many levels are there in the interface, and are they presented in a clear visual language?
3. Are elements of the same level and nature used in a consistent design language?
4. Does the main tone and material fit the overall brand?
5. Is there any loss of detail? button click State, feedback, default state, the number of words exceeded, loaded, not loaded, load failure state, whether all provided?

In addition, cooperation is not easy, three roles need to pay attention to the problem: for the product Manager:

1. App design, do not just look at competitors to determine their own positioning, do not "because the competitor A and b did not do, so we have to do more than A and B Bull b xx function", but to be user-oriented, thinking of their own to provide customers with value. In describing your thoughts to others, please use this sentence to describe and think: xxx This type of people in XXX, XXX environment, want to do xxx things, met the xxx problem. And our app can help him solve this problem skillfully through XXXX way.
2. Do not take the wireframe directly to the interactive designer to see, directly describe your needs can be described clearly. Let the designer know what your goal is, then let the interaction to draw the prototype, let the more professional people do professional things.
3. Don't be too obsessed with vision, for some unimportant details, let go and try to reduce the subjective opinion.
4. Don't be too superstitious. User feedback, can be raised feedback, most of them are fans, deep users, advanced users, they can not represent the voice of all users.
5. Let the development supervisor evaluate the workload and split it into sub-tasks if the evaluation of a part of the workload feels too long.
6. One to two times a week to develop the results, do not frequent to disturb others.
7. Bugs are constantly being found, repaired, and found/repaired at less than 1, before they start to become controllable to determine the exact size of the bug and predict the release date accurately.
8. Do less wrong, the new version try not to add too much icing on the cake features, to meet the core of the line.

For interactive designers:

1. Do not mention the commercial headache, who do not want to be a clean and no ads app? Don't always think about the big, the goal is the most important. Through your design, so that users do not make a sound contribution to click, so that commercialization becomes humane, this is your ability.
2. Don't be too timid, do not say how to change the product, how to change, to contend with him, as the owner of the product, product data, planning, you have to know, so that the information is equal, only the right to speak, in order to have the opportunity to stand in the user's point of view to provide humanized design suggestions, otherwise it can only be a

For visual designers:

1. Brevity is not equal to good (in the industry talk about the simplicity of the supremacy of the atmosphere, there must be some people have doubts about this sentence, not detailed explanation, please first turn to Norman's "How to manage Complex" this book). Fit the user's mental model, let a person at a glance, is good.
2. Don't make a lot of plans, ABC plan to throw out to let the candidate, so tired not tired? First of all to decide which one is the best, to do its own satisfaction, feasible, take the hand, on the line, do not become art.
3. For the development of the visual manuscript, first think about it, how to implement the layout, different screen size how to fit. If there is animation effect, do not describe the imagination, can make the best animation, do not come out, also find a reliable signal. Don't let development gg too angry.

Finally, 90% of the problems are essentially communication problems! The argument of 90% is essentially a noun dispute!

How the interface design process of an app is created