Summary of recent work

1. To prevent design omissions

For changes to the prototype, the list of changes needs to be given to the UI designer so that he can know where to change.

2. About design review

Before each design review, relevant personnel who need to participate need to be notified in advance.

Before explaining, you need to consider how well the relevant personnel understand the design. If you don't understand, you need to briefly introduce "why the design" and "solution".

When explaining the design, you should start from top to bottom, from large modules to details (you need to explain the reasons for the design).

3. In order to avoid delays in the project

It is necessary to understand the UI and development project progress in real time.

4. Consider developers developing according to the UI

In the future, the annotations will be displayed directly in the UI.

5. When the needs are not clear

You can produce abstract sketches to discuss with relevant personnel, saving costs and iterating quickly.

Personal design work:

1. Design process

I First determine who the user is, the scenario, and the goal.

II What functions do users need to accomplish their goals, and what doubts may arise during the process.

III. Start drawing the prototype based on the above structural process.

VI design review.

VII Modify the prototype and improve the details.

2. Design details to be improved

You need to sort out a list and find solutions in your free time.

3. Negligent design principles

When designing a multi-content page, you need to consider relevance. The content should not be obtrusive and text explanations can be provided. (eg: For example, the email address for insurance claims)

For the functions of behavioral operations, clearly define the hierarchical structure and put functions at the same level together.

4. Prototype display

Considering the audience of the prototype, engineers will more often check the annotations of the prototype to understand the interaction logic and various situations. UI designers pay more attention to the display of the interface. In order to prevent them from missing the page, it is best to display the various situations of the prototype in the form of an interface.

5. For copywriting

The copy must be concise and easy to understand. If it is explanatory copy, it needs to be structured.

6. About testing

After the front-end development is completed, the testing requirements are classified into: interface UI, functional interaction, adaptation, and copywriting errors.