---
Title:ios Man-Machine interaction
date:2016-06-04 19:36:27
Tags
---
# # Human Interaction Summary
1) put important content and functionality in a more important position so that users can more easily focus on the main tasks
Some possible ways to do this are to place the main elements in the upper part of the screen and close to the left side of the screen (based on the reading habits from left to right):
2) give each interaction element enough space for the user to manipulate the content and controls
"The clickable area of the clickable control is not less than the X 44 points
3) If only some of the features are not available, provide an explanation interface or hint when the user uses these features
4) If all features are not available, show the user an interface to describe the problem and suggest how the user can correct
This gives the user a feedback that makes them feel that your app is not going wrong. This also gives the user a sense of control and lets them decide whether to take corrective action and continue to use your app, or switch to another app.
<!--more-->
5) The APP resumes its status after restarting so that the user can continue to use it from where it left off, rather than letting the user remember how to return to the previous location
You can go to "state preservation and restoration" to learn more about how to efficiently rebuild and restore app status.
6) Display a splash screen very similar to the first screen of the app
Displays a splash screen that is very similar to the first screen of the app. IOS will display this splash screen in the instant your app launches, which allows users to feel your app is very fast and gives you plenty of time to load content. See "Splash Screen" (page 180th) to learn how to create a splash screen.
7) Avoid requiring users to provide setup information
8) Postpone the landing as much as possible
It's a good idea to navigate through your app and use some of the features when the user is not logged in. Users often leave the app that forces them to sign in before they can do something useful.
9) Avoid inconsistent styles in the interface as much as possible
In general, elements with similar functions should look very much alike. Users often think that the inconsistencies they see are necessarily profound, and then take the time to understand them.
10) Ensure that the main content can be read and understood in the default size
For example, users should not need to scroll to read important text, or enlarge a picture to see the main content.
# # navigation bar Style
* Navigation bar Style principle
1) Hierarchical style: is the app commonly used interface jump style;
2) Flat: It is the style of jumping between the bottom tab bar;
3) content/experience-oriented: When playing the game, mobile map to see the different style of the close number;
# # using modal
1) Modal usage scenario Limitations:
"It's very important to attract users ' attention
You must complete the self-contained task (or explicitly discard it) to avoid having the user's data in an ambiguous state "
2) "Keep the modal task short and concise.
You don't want the user to view modal views as a small program in your app. If the subtasks are too complex, the user ignores their primary task when they enter the modal context. You need to be especially cautious when creating a modal task that involves a hierarchical view, because the user is confused and forgets how to return on the original path. If the modal task must contain subtasks in multiple views, ensure that the user has a unique, clear path between the tiers and avoid looping. For guidelines on using modal views, see modal View (Page 170th).
3) always provide a way to clearly and safely exit the modal task.
When the user exits the modal view, they usually know that their task will be ended. ”
4) "If the task requires a series of multi-layered modal views,
Make sure that users know what happens when they tap the Finish button in the top-level view. Check the task flow to determine whether the finish button in the secondary view completes only some of the tasks in the view, or the entire task. In view of the possibility of confusion, avoid using the Finish button in the satellite view as much as possible.
5) Use the warning box to communicate the necessary-and actionable-information.
The warning box interrupts the user's experience and requires one click to end, so it is important to let the user know that the warning box appears to be reasonable. For more information, see "Warning Box" (Page 165th).
6) Respect the user's settings for receiving notification information. In Settings, users set up how they want to receive notification messages from your app. Be sure to follow these settings to prevent users from shutting down all notification messages from your app. ”
Summary-Human-Computer interaction
