Android interface design specifications-1

Document directory

• Flexibility
• Optimize Layout
• All resources
• Policy
• Status
• Communication
• Boundary

In the past two years, apart from management departments, some projects should also be taken into account, but mainly for mobile projects. Recently, some interface and user experience content have been involved, and no one has done anything about it, learn it by yourself and use the learning record as a backup.

Style devices and displays

Android has millions of mobile phones, tablets, and other devices with various screen sizes. With the flexible Layout System of Android, you can create various applications ranging from mobile phones to tablets.

Flexibility

Stretch and compression la s to adapt to different heights and widths.

Optimize Layout

Additional screen space is available on large devices. However, you need to create a composite view on a mobile handheld device and use multiple views to display more content. These views are easy to navigate.

All resources

Provides resources with different screen resolutions (DPI) to ensure that your application looks good on any device, such as 32*32, 64*64.

Policy

Which of the following specifications should be used to design these multi-size screens? One way is to first design the standard device (normal size and mdpi), and then design the size in the ratio of up to down. Another way is to reduce the size from the largest screen, and find the UI we need to fold on a small screen.

Topic

The topic is a unified style of Android Machine Applications to applications or activities. Style specifies the visual attributes of the user interface elements, such as color, height, fill, and font size. To facilitate the cohesion between all applications on a larger platform, Android provides three system themes from which you can choose to build applications:

Bright theme

Dark theme

Full bright and full dark actionbar topic

GmailIs a fully bright topic.

SettingsIs to use a full-dark topic.

TalkUse full-bright and full-dark action bar topic.

Touch feedback

Use color and brightness to respond to touch, strengthen behavior gestures, and indicate what actions are allowed and what is not allowed.

When a user touches an operable area, the application needs a visual response. This allows users to know which objects are touched, and your application is "audible.

Status

Android UI elements have built-in touch feedback, including status, to indicate whether the touch element reacts.

Communication

When your object responds, more complex gestures help you understand what the operation results will be. For example, when you start to paint the thumbnail left or right recently, it starts to fade. This helps users understand that swiping the card will cause deleted materials.

Boundary

When you try to scroll up or down a rolling area in the past, the boundary visual effect should be displayed to the user. For example, if the user tries to scroll up the first main screen panel, it should be indicated that further up navigation is impossible. Many Android rolling UI parts (such as list or grid list) Support built-in boundary feedback. If you build custom parts, remember to make boundary feedback.

 

By Bruce Lee
Source: http://www.cnblogs.com/BruceLee521
This blog Original article is copyrighted by the blog and I share it with you. You are welcome to reprint it. However, you must keep this statement without the author's consent and provide the author name and original article connection clearly on the article page, otherwise, you are entitled to pursue legal liability.