Taboo cell phone product design

In the process of designing a mobile phone product, we encounter many problems that appear to be very small and easily overlooked. It is these small problems that prompt the user's patience one after another and let users resent their products. Just after the debut of a friend did not go through the actual attention to the details of the small, often encounter similar problems, stressed that after many times, feel better to write down, to encourage new people.

& http: //www.aliyun.com/zixun/aggregation/37954.html "> nbsp;

▣ 1, no clickable effect

The general button will have four states, not click effect, click effect, focus state, press the state. If your button is not available at this time, then it must be gray, or remove the button, otherwise it will mislead the user.

▣ 2, the menu level is too deep

Menu items to 5 to 7 is appropriate, if there are two menu, we should pay attention to the reasonable menu classification, can not have too many levels of menu, or difficult to expect, it is difficult to find, find and return will become very troublesome .

▣ 3, the text length is not limited

Mobile phone interface is small, high cost, a page can only display the next 6 to 10 list, his party can only display the next 10 to 16 words, the title of the word to less than 5 words, tab bar also 2-3 A suitable, then this time there is too long text, we must define the treatment, if it is the choice of type, generally truncated or RBI; if it is content-based reading, you can fold. But the most reasonable way is to streamline the text, shorten the length of the text.

▣ 4, the word meaning is unknown

As the phone is fragmented time, fragmented reading, so the text on the phone interface is more demanding, more demanding, must be in the user to the moment, accurate communication of information. In addition to the clear, but also requires language streamlining, to avoid long-winded; the user's language rather than the language of the program; product copy reflects the product personality.

▣ 5, interactive process too many branches

When doing interactive must have a concept of the task flow throughout, the user is to complete a task and use the software, interactive designers in addition to the interface elements, jump logic and interactive feedback, but also pay attention to user tasks, Get clear of key tasks and minorities, give a clear, unobstructed flow to the main task, and do not give too many possible branches to disrupt the main processes.

▣ 6, the relevant options far away

The related options must be operationally continuous. Although the phone screen looks much smaller than the computer screen, the cost of moving the phone over the screen is much greater than the cost of moving the mouse over the computer. If the relevant election is far away, the user one is easily lost and can not find the next operation, and the other one needs to move his finger to trigger the operation on the other end of the screen.

▣ 7, once loaded with too much data

Traffic, battery power, speed, and stability are four hard metrics for handsets. If your app does not properly help you save traffic, power, browse speed, and browse experience to ensure your application's stability, do not talk about user experience. You can use the pre-load cache, batch loading, dynamic refresh, server-side data compression and other ways to ensure that the provincial, fast, stable basic experience.

▣ 8, button clickable range than looks small

We all know that there is a magical number "44" on the mobile side. According to the minimum touch distance of the index finger of 7mm and the minimum touch distance of the thumb of 9mm, it can be deduced that when designing, the minimum touch distance is 44 * 32px. You can design a beautiful little icon, but in defining the size of its touch, but you can do amplification, but you do not want to design a silly big icon, the touch range is smaller than the icon, this will give Users bring obvious sense of frustration frustration.

▣ 9, the tab has no affiliation with the content

Tabs and content need to have a good linkage, in general, there are two interfaces within an interface is complex enough, do not have three labels, four labels. Each tab has its own unique content, when switching labels, the content with the switch. Tab if it is click to switch, the content part of the overall refresh, if the tab is sliding switch, the content page also follow the sliding switch, do not be a point, a slip.

▣ 10, all the operations are exposed

Mobile product interaction design to go through the reduction, hidden, additional, organizational process, do not vain attempt to what functions, what operations are exposed to highlight the powerful. You need to prioritize all operations for all of your functions, those that are typically used by 20% on the main part of the interface, and the other 80% on secondary or reasonably organized , Hide it on it.

▣ 11, no free data interface design

When we are designing, we tend to provide idealized scenarios where users have come in and how we play. However, when the application is just launched, there is no user. Even when the application has a certain user base, the application may still be a state without data when the new user opens the application, or when the user knows All data, in all three cases, users may encounter empty data interface. Novice designers often do not design, this time the user will see a blank interface, at a loss. Experience is to provide an emotional interface to tell the user that there is no current content; a more guided approach is to guide the user to perform the operation.

▣ 12, user-directed abuse

Last year predicted that the user will be flooding boot, it is clear that the design department like to use the beautiful boot interface to tell the user the new features or hidden applications, but not all applications, all of the features require fancy boot. If it is a generic function, non-key modules, there is no need to guide; If it is function to tell, only light-weight guide; If the version of the update instructions, instructions can be used to guide, but to concise.

▣ 13, no load state

As long as the need for mobile phone networking, the need to exchange data, you need to provide a loading state, whether it is daisy-or Toast dialog box, you need to give developers a global definition, and to inform the loading mode Loaded) or non-modal (background loading). And to take into account the loading time is too long, the network switch is not open, the network is unreasonable and so on how to deal with the situation.

▣ 14, the logic of Back is not defined

In the design for Android, it will involve hardware interaction, including the use of the Back key is a knowledge, Android official guidelines can learn from some, but the specific development, there will be many special circumstances, such as a single instance The keyboard, and some intermediate states, in which case Back may need to be defined, either back to the previous instance (which needs to be a multi-instance) or back to the initial state (emptying the input or restoring the initial status).

▣ 15, no horizontal screen mode design

As the horizontal screen mode, the vertical space becomes extremely valuable, navigation bar, tab bar, the keyboard needs to be flattened, sideways mode must consider whether the simple stretch adaptation or redesign, if your application is not suitable for horizontal Screen mode, the shield sideways, if your application includes the application of widget you need to support sideways mode (even with sliding keyboard horizontal screen machine), you need to provide design. If it is S60V5 this vertical machine, and even need to re-design.

As the mobile phone product interaction designer, using the design to circumvent the problem, enhance product user experience, the experience into value, is our pursuit of the state. Taboo cell phone product design, is the author encountered some design problems, welcome to master all the way to complement the problems encountered, to jointly avoid the invention of wheels.

Source Address: http://elya.cc/2012/02/26/taboo/