cd5a81f752
* Update research-empty.en-US.md Signed-off-by: CodeCompilerConduct <1376397133guoli@gmail.com> * Update research-exception.en-US.md Signed-off-by: CodeCompilerConduct <1376397133guoli@gmail.com> * Update research-form.en-US.md Signed-off-by: CodeCompilerConduct <1376397133guoli@gmail.com> * Update research-list.en-US.md Signed-off-by: CodeCompilerConduct <cs.guoli.huang@gmail.com> * Update research-navigation.en-US.md Additional links to recommended external articles Signed-off-by: CodeCompilerConduct <cs.guoli.huang@gmail.com> * Update research-navigation.en-US.md Signed-off-by: CodeCompilerConduct <cs.guoli.huang@gmail.com> * Update research-overview.en-US.md Signed-off-by: CodeCompilerConduct <cs.guoli.huang@gmail.com> * Update research-result.en-US.md Signed-off-by: CodeCompilerConduct <cs.guoli.huang@gmail.com> * Update research-workbench.en-US.md Signed-off-by: CodeCompilerConduct <cs.guoli.huang@gmail.com> --------- Signed-off-by: CodeCompilerConduct <1376397133guoli@gmail.com> Signed-off-by: CodeCompilerConduct <cs.guoli.huang@gmail.com>
5.8 KiB
| group | type | order | title | skip |
|---|---|---|---|---|
| Design Patterns (Research) | Template Document | 4 | Result Page | true |
A result page is a page that provides feedback on the outcome of an operation. It is the strongest form of feedback mode.
When to Use
When an operation process is completed and clear feedback is needed for the user, such as the final step of a step form.
When a large amount of information needs to be displayed on the result page.
Design Goals
Convey the task completion result to the user, guide the user to the next operation, and establish the user's trust in the system through effective feedback.
Design Principles
Use Cautiously
The result page is a heavy feedback method, only suitable for scenarios where strong user attention is needed, the information volume is large, and the page stays permanently. It is not recommended for other scenarios.
End Instantly
When the result status is successful, it can automatically jump after a few seconds (3-5 seconds is recommended).
Simplify Information
The information on the result page should be the result triggered by the submission action, such as validation should be completed in the form. The information on the result page should be concise, only displaying result-related content. Additional information can be added for special scenarios.
Design Suggestions
The title should be constructed as "Object + Action + Result/Status" or "Action + Result/Status".
It is recommended to limit the guidance operations to no more than 2 items, as too many operations can cause confusion for users.
For lighter feedback, it is not recommended to use a result page. Use global tips, warning tips, notification boxes, etc. Refer to feedback design guidelines for details.
If the result status is successful, inform the user that it will automatically jump after a few seconds on the main button.
How to Design
Basic Layout
The result page can provide the following content:
-
Result Feedback: Clearly inform the user of the submission result;
-
Result Explanation (optional): Used for brief explanations of the result if needed;
-
Suggested Actions: Guide the user to continue with subsequent tasks;
-
Additional Information (optional): Provide supplementary information to the user along with the result; marketing modules.
Template - Basic Result Page
Displays the result status and guides the user to the next operation.
Template - Complex Result Page
In addition to basic information like result status and guidance operations, it also displays related recommendations, process progress, error details, etc.
Additional Information Types
