Eight Android tuyu Designs

Http://news.cnblogs.com/n/106763/

From the day when Android was born, this cute little robot, by virtue of its open-source power, squeezed Ios to the throne with the highest market share. Although the numbers are dominant, IOS is always the mobile platform with the best experience.

It is true that IOS has successfully simplified what you see is what you get on the interface, and reduced the hardware key of the mobile phone to one, so that you can control the items that you can operate in a very small space, this effectively reduces users' learning costs. However, as novitski is moving outward, it can still be defined as the best power forward in the world like Duncan, why can't Android be defined as the world's best mobile platform system like iOS?

Although android has a variety of hardware key designs, it is not as simple as IOS in terms of operational scope. For example, it can use different menu options on different interfaces for operations, for example, an application can run multiple processes and multiple services at the same time. However, if you can make good use of it, android can also provide another excellent experience.

A Zhi wrote an article titled "It is better to thoroughly study Android than to blindly copy android", which is about the lack of research on Android in China, leading to poor overall quality of Android apps in China. On Android, designers made a large number of shanzhai UI elements and design methods on other platforms, which eventually led to a big collection of shanzhai and a black hole in user experience. Some of the products we are familiar.

What we have collected here is some design methods that lack in-depth research on Android, copy the UI elements of other platforms, or rape users by nature, which are not intended to be accused, we hope to make everyone aware. After all, shanzhai is something we don't want to do.

1. Return in the upper left corner

There are two types of responses on the mobile phone interface: the previous interface and the previous interface. In Android applications, the buttons returned are not displayed on the interface, but are all completed through the hardware back key. Therefore, any return button on the android interface (including the IOS return button in the upper left corner) is incorrect and unreasonable.

Of course, there are exceptions, such as in a Configuration Wizard.

2. Resident notification bar

In the Android system, the notification bar contains two types of information, ongoing and notifications (some also include the shortcut function switch and the program running list Rom, which are not discussed here ). Their difference is that notifications are notifications of new information from various applications, such as text messages and new emails. It can be cleared directly. Ongoing indicates some programs or functions that are currently running and cannot be cleared directly.

However, we should note that ongoing should display the programs and functions that users must understand and may affect the use of mobile phones, such as playing music and making calls, uploading and downloading. If your application is in the exit or running status, it does not affect the user. You do not need to inform the user of the process that the system manages your application through the resident notification bar.

3. Confirm to exit

First, we need to understand the stack mechanism of the android interface. Each operation activity is saved. When the back key is used, for example, the system will automatically kill the previous activity.

However, if the root interface of the application is used, all processes of the application are automatically suspended with the back key, except for background services. It does not consume CPU resources, but occupies some memory. Android and Java are similar. The system has a rule to recycle the memory. For memory scheduling, there is a threshold value. Only systems lower than this threshold value will be from a list, close the application process from the back to the front. The benefit of this design is that it allows users to maximize the speed of multi-task switching, because the process is only suspended.

From the perspective of system design, exit requires confirmation or even a rogue action. This is also a paradox from the perspective of preventing user misoperations. When you press the back key, the process will be suspended, and the user will not have any risks such as information loss. Even if a misoperation occurs, the user can easily restore the application according to the android stack mechanism. You have never seen IOS Press the Home key. Can you confirm the exit box?

4. Check the update settings.

I deeply understand why developers are doing this: In the Android system, app updates are pushed by the market, and the premise of using the market is that the mobile phone is bound to the Google account number. The key to the problem is that Android phones of some manufacturers do not require users to bind their Google accounts. They even launch app malls and want to share a piece of cake.

This makes Android app developers suffer. In order to allow different users to instantly obtain the update information, they have to add the update check function in their own apps. Then, the update check settings are generated.

But let developers think about it. Do you really need to set it for users? Can your application be updated every day? Maybe you only need to set a default one-week check update.

5. No sharing

The sharing function is a feature of Android. With support from only two clients, users can share information between any two local clients, such as saving Weibo to the local Evernote application, select an image from the image library and send it to your friends through WhatsApp.

The sharing Function of Android allows two local clients to meet different task flows more efficiently. For example, for photo sharing, android can use camera 360 to take photos and then set various filters to directly send any local Weibo client to Weibo. Taking a photo first and then sharing it again is also in line with the user's operating habits.

In comparison, IOS is quite troublesome. developers can either make the filter function in the Weibo client, or users may need to take a photo first to set the filter and save it to the image library, then, select from the image library on the Weibo page.

The sharing mechanism of android can effectively avoid expansion of client functions, help developers Save the workload, and adapt to multiple user scenarios. The real implementation of the concept of allowing an application to solve only one problem for the user has to be said to be a joke of IOS.

6. No focus

Some Android mobile phones have trackball and other input devices. you can scroll the trackball to focus on a certain control on the interface. This can help users with some touch barrier. More importantly, with the release of Android @ Home, the android system may appear on refrigerators, washing machines, and other household appliances, and is controlled by a five-dimensional navigation key, this makes the focus state more important.

It is even more foreseeable that android does not provide accessibility solutions like voice over on IOS at present. If it is provided, trackball can bring a better mobile device experience to more blind users.

7. A large number of cached images

Android does not completely remove the file concept like Ios. Therefore, if your application does not process cached files, a large amount of these images will be accumulated in the system's gallery, slow down. To solve this problem, you only need to change the cached image to a type that cannot be recognized by Gallery.

8. No move to sdcard

If the size of your application exceeds 5 MB, you will not be able to use the move to sdcard function, because after all, a large number of users only have memory space below MB. Of course, Google's map applications have always occupied 12 Mb of body memory.

In any case, Android is an excellent Mobile Phone platform, and I love this mobile phone system as much as IOS does. I also always believe that although Android development costs are too high, Android applications can still be very good as long as you correctly understand its system design philosophy.

Http://azero.tsang.blog.163.com/blog/static/470052011516348755/