Android UI design tips: Part I

Android's official developer blog posted a slide to introduce some tips on Android UI design. Roger came out here in the form of a picture, if you are interested, continue to the next step. The entire PPT is divided into five parts. Part I translates the first two parts.

As a developer, why do we need to care about the UI? A bunch of previous connections can be ignored and jumped directly to the last one. Because a good UI design can help us sell more copies and make more money ^_^

This PPT contains five parts:
1> what to do and what to do
2> design philosophy and considerations
3> UI framework features you must understand
4> new UI design mode
5> icons and guidelines

Don't:
1> do not copy your uidesign on other platforms. It should make users feel like they are using an Android software, balancing 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> cooperation with visual Interaction designers !!!

Design Philosophy:
1> clean but simple
2> focus on content rather than Modification
3> consistent storage, making it easy for users to invest in it, with slight changes available
4> use cloud services (to store and synchronize user data) to enhance user experience

Design Guidelines for excellent interfaces:
1> follow users
2> display correct content
3> give users appropriate feedback
4> rule-based Behavior Models
5> tolerate errors

Follow-up users:
1> learn about your users (age, skills, culture, requirements for your applications, devices used, and how to use devices whenever and wherever)
2> 'user First 'Design mentality (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> less commonly used functions 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 feature 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.

-Donald Norman, author of the design of everyday things

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

Design considerations:
6> it is important to know the differences between different devices!
7> Read CDD and learn the possible differences between devices.
8> understand screen size and density Classification

Via Android Developers