Thinking: What factors should be considered in a complete interactive manuscript? How to judge whether an interaction design is excellent or not?

As a bridge between design and development, interactive draft inherits the logical integrity of development. For design, it is the superiority of experience. The foothold of demand analysis, user survey, competing product analysis and data analysis all need a complete design document to realize.

Step 1: Define excellent design standards.

If you want to make an excellent design, you must first make clear what an excellent design is like. Only by knowing beauty can you pursue beauty. Playing more excellent products is of great benefit to improving our design level. If the standard of excellent interaction design is refined, it can be divided into two standards: "usability" and "innovation".

1. "Usability" standard We can refer to the LEMES principle proposed by Luke Miller in User Experience Methodology, that is:

A. easy to learn

B. Efficiency-efficiency

C. Easy to remember-Memorability

D. Error correction-error

E.- Satisfaction

2. For the "innovation" standard, we can refer to four integration+1 concerns.

A. advantages of integrating competitive products

B. integrating popular functions

C. integrating a plurality of operation steps

D. integrating multiple user groups

E. Pay attention to details

The purpose of defining the standard of excellent design is to help us check and fill the gaps and move towards the goal.

Step 2: Define the functional logic.

After defining requirements, don't rush to output interactive drafts to avoid logical loopholes. Do three steps first:

1. Organize the business flow chart

From the development point of view, determining the function involves adding, deleting and checking data, including the data flow between a single page and multiple pages. By communicating with developers on the business flow chart, technical problems can be sorted out in advance to avoid the difficulty or impossibility of technical realization after functional design.

2. Make clear all the scenarios where the requirements appear.

Exhausting all possible situations of requirements with logical thinking is a process of testing logical integrity, and brain map software can help us traverse the scene. Of course, our maximum probability will still be missed, and we need to closely cooperate with the test and strive to cover all scenarios.

3. Determine the core experience

Clarify the "key points". A function is often only 1, and two design points are the most important. Defining the key points will help us to learn the advantages of competing products and optimize the core experience. Restraint is like wechat. In the era of "supply far exceeds demand" of mobile Internet, big and complete is far less than small and refined.

If we need to design a "square" function, feed stream layout, browsing mode, like, share, comment and so on. It's just an auxiliary experience. There is only one core experience-"content".

Step 3: Object-oriented functional attribute analysis

How to output a complete interactive manuscript? Learn to develop thinking and analyze functional attributes with object-oriented thinking to help us avoid omissions to the maximum extent. The steps include:

A. enumerate all the attributes of the function;

B, determining the interactive event for modifying the attribute;

C. determine the modified attributes.

Step 4: Output the documents that meet the design specifications.

The first interactive draft that meets the design specifications is visually beautiful and enhances product expectations. The second is to reflect our professionalism and take the lead in product design. For logic specification, we refer to Don Norman's interaction design principle:

A. intended use-sacrifice

B. signifier indicator-signifier

C. restrictions-constraints

D. matching mapping

E. Feedback-feedback

F. Mental model-conceptual model

Visual norms refer to the design principles mentioned in Robbin Williams' Design Book for All. The author's common design attributes are: location, size, font size, color, spacing, hierarchy and consistency.

After the prototype is completed, we need to use design standards to check what can be improved and the details.

1. The treatment of "limit value/particularity" usually includes:

A. character truncation;

B. the page is empty;

C. adaptation of long screen (12max) and short screen

The difference between D.d.Android and IOS

2. Combining design and development business:

A. sort out all the copywriting;

B. sort out all dynamic logic;

C. combing all audio;

D. combing complex business logic;

E. combing the page flow chart required by the visual designer

Step 1: Define excellent design standards.

The abstract definition is based on the LEMES principle: Is this function easy to learn? Is it efficient? Is it easy to remember? Correct the wrong operation? Does it satisfy users? Excellent competitive experience We can take the top products in IOS as the benchmark.

Step 2: Organize functional logic

***7 situations:

A. Scene 1: The owner invites a player who is not in his seat to designate a seat. (normal)

B. The host invites the players in the seat to sit in different seats.

C. The host invites the players in the seat to sit in the same seat.

D. The host keeps inviting players who are not in their seats to sit in the same seat;

E. The host keeps inviting players who are not in their seats to sit in different seats.

F. The host keeps inviting the players in the seat to sit in the same seat;

G. The host keeps inviting the players in the seat to sit in different seats.

The core experience is that the host invites players who are not in their seats to designate seats (scene 1), and we can enjoy a smooth experience in the simplest way by focusing on the design of this scene experience without affecting other scene experiences.

For the live 1, in order to ensure the privacy of the invited contestants, the invited party needs to confirm before going to the wheat field to ensure that their voices will not be exposed in public without permission. In order to invite players to get on the Mac quickly, we provide a search box to support the query of nicknames and comments.

Scenario 2 is similar to scenario 1, and the optimization scheme is to display the players on the Shanghai player list in order. Scenario 3 is a meaningless operation, which we don't support. We chose not to show the players in the seat in the player list. For scenarios 4, 5, 6 and 7, in order to avoid and prevent users from receiving invitations continuously, we design that the inviter can invite at will without restriction, but the invitee will only receive an invitation once within the set time threshold.

Step 3: Object-oriented functional attribute analysis

Step 4: Output the documents that meet the design specifications.

What we need to do to deal with "particularity" includes:

A. character truncation, user name is limited to 8 words; 、

3. The old scene, "Invitation failed, player version is too low".

Interaction design involves a wide range of fields, from psychology to ergonomics, which requires our unremitting efforts and continuous accumulation. Read more excellent books and articles in theory, learn more excellent products in practice and design more copywriting.