Android UI tips

Android's official developer blog posted a slide to introduce some tips on Android UI design. Here, we will show you how to speak.

Don't: 
1. Do not copy your uidesign on other platforms. Users should feel that they are using an Android software to strike a balance between your trademark display and overall platform view.
2. Do not over-use the Modal Dialog Box
3. Do not use a fixed absolute positioning layout.
4. Do not use PX units. Use DP or SP for text.
5. Do not use a small font.

Do: 
1. Create resources for high-resolution screens (better overall zoom-in ratio)
2. The elements to be clicked must be large enough.
3. the icon design follows the android standard.
4. Use appropriate spacing (margins, padding)
5. Supports D-pad and trackball navigation.
6. correctly manage the activity Stack
7. Correctly handle screen direction changes
8. Use theme/style, size, and color resources to reduce unnecessary values.
9. Cooperate with visual Interaction designers !!!

Design Philosophy: 
1. Clean but not easy
2. Focus on content rather than Modification
3. Consistent storage, making it easy for users to invest in IT and adding a little change
4. Use cloud services (to store and synchronize user data) to enhance user experience (Big D: This is indeed very convenient .)

Design Guidelines for excellent interfaces: 
1. Follow the user
2. display the correct content
3. Give appropriate feedback to users
4. Rule-Based Behavior Models
5. tolerate errors

Follow-up users:
1. Understand your users (age, skills, culture, requirements for your applications, devices used, and how to use devices) (Big D: This is important)
2. Design mentality of "user first" (users are usually task-oriented behavior models)
3. Earlier, more frequently tested by real users

Display the correct content: 
1. The most common operations must be visible and available to users as soon as possible.
2. functions that are not commonly used can be placed in the menu.

Give the user appropriate feedback: 
1. Interactive UI elements must reflect at least four different States (default, disabled, focused, and pressed)
2. Ensure that the operation results are clearly visible.
3. Give more progress prompts to users, but do not interfere with their current operations.

Rule-based behavior patterns:
1. The behavior mode follows the user's expectations (correct operation of the activity stack, display the information and actions that the user expects to see)
2. Use the appropriate method to enhance the function visibility (clickable elements should look as clickable)
3. If you need complicated operations to complete a task, rethink your design !!!

Error Tolerance:
1. Only meaningful operations are allowed (some buttons are disabled as appropriate)
2. Minimize non-rollback operations
3. It is better to allow rollback (UNDO) than to use the confirmation dialog box (in fact, the confirmation dialog box should be used as few as possible, which is a disturbance to Users)
If an error occurs, it will happen.

Design considerations: 
1. physical size of the screen
2. Screen Density
3. screen orientation (vertical and horizontal)
4. Main UI interaction methods (touch screen or D-pad/trackball)
5. Soft or physical keyboard
6. It is very important to understand the differences between different devices!
7. Read CDD and learn the possible differences between devices
8. Understand screen size and density Classification
To put it another note, you must have an "exit" button so that you can close the software with peace of mind without worrying that it will consume system resources and traffic.