Ten common UX errors in Android Application Design (1)

Every day, the Android developer relationship team tries countless apps or apps sent by countless developers for evaluation. After evaluating so many applications, They summed up some of the most common errors and presented them to everyone in this program.

Before officially introducing these errors, I would like to mention a little bit. These errors are very common errors. That is to say, you may encounter these 10 errors with ten applications, or even all 10 errors in one application. This situation is more severe in tianchao. Therefore, I hope this article will free you from the dilemma of crossing the river by feeling the stones and avoid common mistakes directly.

The top 10 users experience "anti-pattern". The Android developer contact Team presents your intentions. Every typical error has an interesting title. I hope you can see it in the middle) heart (GUN ).

10: You must load these things ...... Otherwise!

Loading here actually refers to the kind of dialog box in the left graph, Which is circled and converted. This kind of dialog box should be avoided. In addition, compared with such a dialog box, those dialog boxes that do not respond to the Back operation are too unreasonable.

The solution is actually very simple, just use embedded loading instructions. Of course, it would be even better if you could load data in the background.

Ninth: You cannot touch me!

The first problem is the small touch area. Android Design emphasizes that all touchable objects should be at least 32dp high, and the ideal size is 48dp, unless your target user is a very small person like a baby.

Another bad error is that there is no touch feedback. Some developers do not want to use standard button controls, but the advantage of standard buttons is that they provide visual effects of touch feedback. For users, finding buttons without feedback will make them think that your application is faster than itself. For users, the perceived speed is what they can understand, while the real loading speed and running speed are not as easy as the perceived speed. In addition, the highlighted touch feedback can indicate the actual touch area. For example, when a user presses a list item, the entire line of this item will be lit up, but there will be a 16dp blank on both sides, which is equivalent to telling the user, the 16dp item closest to the screen edge is not a touch area.

8. Design = Photoshop

First of all, do not learn the metamorphosis in the small picture on the right. I know that everyone is very/interested in the various effects that PS can achieve, however, improper/excessive use of these effects will only make your application seem outdated or worse-very amateur.

When designing your application, be sure to focus on the content rather than those highlights. The app is not installed by the user to see the glittering buttons. All these visual designs should end with content services, rather than decoration.

In addition, ensure that the visual style of the application is consistent. Users who are useless will want to see an application with half of the Holo and half of the grass mud. The name criticized Feedly for its glamorous appearance, but set it as an application of the Jurassic era. In addition, an application should not have too many buttons, select boxes, or dialog box styles. One is enough. Directly calling Android-style controls is a simple and effective method.

There are also some developers who have neglected the details, such as inconsistent measurements, incorrect spacing, the colors used by ghost animals, and the font selection of mourning ...... These are details that make users feel uncomfortable. as developers, there is no reason to ignore them.

7. Jurassic guests

If your application was created in 2009, your users will suffer ......

The first question to be mentioned here is the Menu key, or the shame of the Menu button. Now we have an Action Bar to replace the menu keys of the Jurassic age, right? Backward compatibility is not an excuse, because if you set the appropriate parameters, the Overflow button will not appear on the machine with the solid menu key. Of course, you can also enable a machine with an entity menu key to forcibly Display Action Overflow to increase its visibility. However, in any case, do not allow the Menu key to be called out only through the solid Menu key (the three dots on the right of the Nav Bar will be changed on a machine with only the virtual key.

Although the latest Android API has reached Lv 18, you do not have to set targetSdkVersion to 18, as long as it is more than 16. If you set the API to Lv 14 or even lower, your application will force three dots to be displayed on the Nav Bar, this is really a tough thing for users of some devices, such as HTC One.

Another scenario is to continue to follow the visual style of Android 2.3 or even earlier. This kind of App sometimes looks pretty Holo, but when you press a button or a list item, the orange visual feedback in the Android 2.3 style appears, such as MIUI ), or you can see the scroll bar of the 2.3 style when rolling, or the circle of the 2.3 style when loading. This is definitely not what the user wants. Roman Nurik emphasizes the circle during loading. the Holo-style loading Ring actually rotates the two circles at different speeds at the same time to create a smoother animation than a single lap.

Sixth: Pure BloodHybrid Android

The principle problem here is: do not violate the "Pure Blood Android" statute.

Just like the title, the content of this chapter is to say, do not move elements from other platforms to Android. I have mentioned this issue many times in my previous articles. I will not talk about it here. Several special errors are also common:

• Right Arrow: the secondary navigation has no horizontal ing on Android. In other words,Secondary navigationAndHorizontal navigationTwo things
• Bottom tab bar: for Android, the top is the position of the tab bar.
• Learn from other platforms: Android users want Android applications