Next, let's talk about Android in the process of growth. This article describes the features of Android platforms different from those of other touch-screen mobile phone systems and desktop systems. These features require more performance in our developed applications, this is an Android app. These features may be difficult for users who are used to other mobile phone operating systems, so they need to learn and adapt again. In addition, the Android system will be insufficient during the growth period, the summary of these features helps improve the user experience of applications.
Android phones represented by milestone
First, let's briefly describe who is using the Android mobile phone. According to Nielsen's recent data survey:
◆ Among female consumers, the proportion of the iPhone to be purchased is 31%, and the proportion of the Android mobile phone to be purchased is 23%;
◆ Among male consumers, the proportion of the iPhone to be purchased is 29%, and the proportion of the Android mobile phone to be purchased is 33%.
◆ Gender differences can be obtained. Men prefer to buy Android phones. This also gives Android a personalized definition: technology, engineering, rules, and rationality.
In addition, we can think that most users who use Android phones have a history of using symbian. Users can understand the habit of arranging functional buttons and menus at the bottom of the symbian system.
The simple principle of interaction design is don't make me think. However, after using Android phones, it will make you feelIt makes me think a lot. Compared with the interaction principle defined by norman, I scored Android with a full score of 100 ):
Visible Visibipty-can is see it? |
50 |
Feedback-what is it doing now? |
80 |
Ideographic Affordance-how do I use it? |
60 |
Navigation Mapping-where am 1 and where can I go? |
60 |
Constraint-why can't I do that? |
80 |
Consistent Consistency-this is famipar |
40 |
Because menu and other elements are placed in the screen space, users seldom fully understand the page functions compared to the iPhone. You must click the menu key to display more functions, so the visibility is not good; consistency is a serious problem due to the multi-version, variety, multiple screens, multiple applications, and multiple users mentioned above.
Before the analysis, I summarized five principles of Interactive Design:
◆Reduces visual pressure. Simplified text
◆Reduce the thinking pressure. Regular icon, less choice
◆Reduce memory pressure. Consistency, using the "7±2" and "Block" principles,
◆Reduce the movement pressure. Display and Operation Proximity
◆Reduce or eliminate the burden of technology. It is a common term.
As the interaction subject and interface object, a person completes interaction through intent actions to implement a user's task. The interface is the information carrier that intuitively conveys what the user can do and what to do on the mobile phone. The interaction of the Android system is decomposed as follows:
◆ Layout
◆ Screen
◆ Box
◆ Intent action
◆ Click, hold, drag, and drop, pinch & helpp;
◆ Intent object
◆ Physical buttons, menu, placed on the Screen Object, Status Bar
◆ Feedback
◆ Navigation
◆ Others
Layout
Application Interface Structure
For an application, from the development perspective, a series of activities constitute an application. From the design perspective, an application consists of a series of screens and boxes, they are the carrier of information and operations in applications.
Screen
Comparison between Android and iPhone
In comparison, we can see that the title of Android does not carry the navigation function, because the returned function provides the physical key to save space.
The Android status bar must be visible in any application because it carries the notification mechanism, task management, and other functions. The layout feature is determined based on the operational features. It is required to pursue a visual balance, and more importantly, to meet the needs of mobile phone operations. For example, Android smartphones are full-touch mobile phones, the screen size requires a single-handed grip. To achieve the single-handed operation of the keyboard, we need to place as many operations as possible under the screen, especially for some emergency application functions. Therefore, we recommend that you place the Category tab below the page, when there is no fixed button. In case of conflicts between the two, the command button that needs to be placed on the screen is prioritized. This is also based on the principle of minimum movement.) There are several typical cases:
◆ Toolbar for external use of commonly used buttons;
◆ The position and number of menus, which are 2 × 3 defined by the system, are not applicable in more scenarios. More menus can be placed, we have defined a 2 × 4 arrangement method. The menu policy will be introduced later.
◆ The tab at the bottom is generally in the form of icons and text. We have given the max number 5,
◆ Unlike the bottom tab, the title must be omitted for the top tab. This is because the tab can be used to locate the current page.
Box
Why the box format? The reason is:
◆ Reasonable use can reduce the content level and make the application structure more flat.
◆ Box is more eye-catching than screen, and the content is clearer. Because the visible area is reduced, the information is more compact.
Is the box category. We can see that there are buttons and no buttons in the upper and lower layers. In addition, a weak toast prompt format is also included in the box.
Various boxes
The dialog box contains the following content:
◆ Warning dialog box: severe warning
◆ Select dialog box: Select one or multiple items. A confirmation button is required to confirm the selection.
◆ Input box: There is input space inside. If the keyboard is blocked, the input box needs to be moved to the top of the screen to ensure it is not blocked.
◆ List box: similar to the single-choice dialog box, the difference is that there is no radio button. How to distinguish it from a single choice depends on whether the content selection result has serious consequences.
◆ Context menu: a command set that appears with a long Android press. The format is similar to that of the list box, but the content is different. Here is generally an Action Command.
◆ Description box: mostly used for version description.
Note the following when designing a box:
◆ Title: A normal box must have a title. The title should be concise and the purpose of the box should be directly stated, such as "Exit" and "re-download, the title of "prompt" is meaningless. You cannot have any questions in the title.
◆ Content: It must be formal alignment, similar in structure, and clear and concise in meaning.
◆ Reclaim method: Do you want to put a "cancel" button? My experience depends on the situation. Basically, based on the figure above, I will try to use the return key if possible.
◆ Number of buttons: 1, 2, 3? Select as few users as possible. We recommend that you do not allow ambiguous buttons. The buttons are mutually exclusive.
◆ Text: the text on the title. The content text must be consistent with the button text. Try to use "OK" and "cancel ". Do not use other words.
Some box Cases