Basic Idea of UI design

When designing the UI, we usually have some steps and principles. Below we list some commonly used ones, which may not be very accurate. I hope you can give me some advice on the UI design, there must be a consciousness here. When getting a UI design drawing, do not immediately think about how to implement it, but need to be carefully analyzed and designed.

1. clearly divide the parts related to and irrelevant to the UI

Based on the UI design diagram, we first need to extract the data displayed on the UI to view the UI performance. That is to say, extract the UI-related parts. For example, an interface may need to be composed of several parts, and how to design each part.

2. Split the screen size to clarify the jump relationship

Considering the screen size and DPI of your app, different screens and DPI may have different UI la S. The most typical version is the SDK version above 3.0, fragement elements may be introduced. The uidesign of mobile phone screen and tablet screen is completely different.

In addition, you can specify the jump relationship as much as possible, which can be marked in the form of some small cards. A card version represents a picture and the Migration relationship between different pictures is clearly defined.

At the same time, we also need to find out the similarities and differences between these pictures, because this will affect whether to decide to extract the common picture.

3. List the UI elements (widgets) to be used)

List the UI elements displayed on the interface, such as commonly used buttons and imagebutton, which are very simple. You can see at first glance that some UIS may involve custom views, you must consider more here.

In addition, for unified control, for example, a button may be extended, and a font size may be changed in the derived class. This method is usually used for the same font size of most UIS, A common button can be abstracted, so that the font size does not need to be set in each UI.

In addition, you can also extract common styles, such as textview style, text color, font size, and whether to bold them.

4. List which UI elements can use the SDK and which ones need to be customized.

In my experience, a project usually has custom components (Views), most of which are combined controls ------ combine different widgets into a layout. This needs to be determined based on the project's own needs.

Note: there must be a good design here to change as needed. For example, the first version may require no combination of views and can be completed directly using the SDK's own widgets. However, after some changes, the previous UI design is out of date, you may need to provide a custom view, so you may need to modify the widgets of the SDK. Such changes are both big and small. during design, you should consider such changes.

5. Draw the UI

In fact, this step may not be used. In general, self-painting is not involved, because self-painting is troublesome and time-consuming. However, in special cases, self-painting can improve efficiency, because layout, measure, touch event, and dispatch draw are involved in view layout, which may affect the performance.

6. Integrate the internal logic and UI

Generally, a view has some logic, especially a custom view, which may encapsulate certain attributes.

When using these views, the UI activity will have a logical integration with these views.

The above are some of my ideas. You are welcome to correct them.

About Android applicationsProgramThe Framework Design, please refer to the android Program Framework Design http://blog.csdn.net/leehong2005/article/details/8535306

Who knows how to insert a hyperlink to a csdn blog?