Mobile phone product design taboos

Posted by : http://developer.aiwgame.com/mobile-phone-product-design-taboos.html

My Friend is Baidu P6 senior interaction designer, dressed in the UE leather PM, focus on mobile Internet, concerned about the mobile phone product design, and her great experience of mobile product design, this time she summed up the 15 “mobile phone product design taboo” very useful also valuable. Do mobile phone product design process, meet a lot of seemingly small and can easily be overlooked, it is these small problems, again deeply moved by the user’s patience, let your heart resentment. The friends of the business for no real combat, few pay attention on details, often encountered similar problems, stressed repeatedly, I feel better to write down and give new encourage each other.

1, did not click on the effect of
The general button there will be four states not clickable effect, you can click on the effect of focusing the state, press the state. If your button is in an unusable state, then it must be greyed out or remove the button, or else give users misleading.

2, the menu hierarchy is too deep
Menu items 5 to 7 is appropriate if there are two menu, it is necessary to note that a reasonable classification of the menu, you can not have too many levels of menu, otherwise difficult to predict, it is difficult to find, to find and return will be a lot of trouble .

3, the text length is not to be limited
Mobile phone interface is very small, high cost of land, one can only display the list of six to 10, a line can only display 10 to 16 words, the number of words in the title bar to 5 or less, the tab bar 2 to 3 an appropriate, then this text is too long, must define the approach, if you choose, usually truncate or RBI abbreviated; if it is content to read, you can wrap. But the most reasonable way to streamline the text, to shorten the length of the text.

4, the text ideographic unknown
Since the phone is the fragments of time, fragmentary reading, so the requirements of the intended nature of the text on the table in the mobile phone interface higher, more demanding, we must cast a glance in the user to instantly and accurately convey information. In addition to the the ideographic clear, requiring language to streamline, to avoid Hello repetitious; use the language of the user rather than the language of the program; product copy reflect product personality.

5,Interactive process branch too
Do interact, there must be a task flow concept through to the end user to complete a task using the software, interaction designers, in addition to concern the interface elements, to jump logical and interactive feedback, but also focus on user tasks, distinguish the main task and the secondary characters, a clear process to the main task of a barrier-free, do not give too many possible branch to interfere with the main flow.

6, the related options are far apart
Related options must have continuity in the operation, the phone screen looks to be much smaller than the computer screen, but the cost of mobile phone on the screen, but better than moving the mouse on the computer cost of a large, if the phone on the relevant election election from very far away, the user first, easy to get lost and can not find the next step, the second is the need to move the finger to the screen the other end to trigger action.

7, a load too much data
Traffic, power, speed and stability of the four fixed target of mobile phone products to enhance browsing speed and browsing experience, to ensure the stable performance of the application, if your application can not reasonably help the user to save traffic, electricity, do not talk about user experience. You can preload the cache, bulk load, dynamic refresh, server-side data compression to ensure the province, fast, stable basis of experience.

8,Button click range is smaller than it looks
We all know that the mobile side there is a magic number “44″, according to the distance of the index finger, the smallest touch distance 7mm thumb minimum tap 9mm, the design can be deduced from the smallest touch distance is 44 * 32 px. You can design a nice small icon, but to define the size of its touch, but can be done to enlarge deal with, but you do not design a silly icon, tap the range than the icons smaller, which would give users obvious misuse frustration.

9, the tab has no affiliation with the content
Tab with the content need to have a good linkage between general an interface has two labels is complicated enough, do not have three labels, four labels. Each tab has its own unique content, when the switch labels, followed by switching. The tab is to click the switch, the content part of the overall refresh tab if it is a sliding switch, content pages have to follow the sliding switch, do not be a point, a slip.

10, all operations are exposed
Interaction design of mobile phone products to experience reduced, hidden, additional process of the organization, do not attempt to what function, what operations are exposed to highlight the strong. You need all the features of the application all operations to be a priority setting, and those commonly used in 20% of the functionality on the interface position, the other 80% of operating on a secondary position, or reasonably classified organization hidden.

11, no empty data interface design.
The design is often idealized scenario, users have come, how we play. However, often when the application has just launched, there is no users, even when the application of a certain user base, the new incoming users to open applications, the application may still be a data state, and then clear or when a user The full data for these three cases, the user may encounter the empty data interface. Novice designers often without design, this time users will see a blank interface, lost their sense. Experience in practice is to provide an emotional interface, tell the user currently has no content; more to guide the sexual practice is to guide the user to perform operations.

12, the user guide of abuse
Last year predicted that the user guide will be flooding, obviously design department like nice boot interface tells the user the new features or hide the application, but not all applications, all of the features fancy boot. If the function is generic, non-focus module, do not need to boot; if it is a lightweight boot function to inform only; version of the update instructions, manual style guide can be used, but be concise.

13, no load in the state.
Mobile phone products need networking, you need to exchange data, will need to provide a load in the state, whether it is the the chrysanthemum turn Toast or dialog box, you need to develop a global definition, and to inform the loading mode (front loading) or non-modal (background loading). And to take into account the load time is too long, the network switch is not turned on, the network is disconnected, respectively, how to deal with.

14, logic of undefined Back
Do the design for the Android, it comes to hardware interaction, including the use of Back button, is a science, the Android official there are some guiding principles can learn, but the specific development when there was still a lot of special circumstances, such as a single instance of replacement, keyboard, and some intermediate state, this case, the Back may need to be defined, the return to a previous instance (it would need to become a multi-instance) or the return to the initial state (empty input content or restore the initial state).

15, no landscape mode design
Due to horizontal screen mode, the vertical space becomes particularly valuable, navigation bar, tab bar, the keyboard needs to be squashed sideways patterns must consider the adaptation of the simple tension or re-design, if your application is not suitable in the transverse screen mode, the shield sideways if your application includes the application widget needs to support the sideways mode (or even cross-screen machines with a sliding keyboard), you need to design programs. If it is the S60V5 this vertical high machines, or even need to be redesigned.

As interaction designer of mobile phone products, designed to circumvent the problem, improve product user experience, the experience into value, is the realm of what we are after. Contraindications of mobile phone design, I encountered a number of design issues, and welcome brightest master synergistic complement to the problems encountered by common and to avoid reinventing the wheel.

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
资源包主要包含以下内容: ASP项目源码:每个资源包中都包含完整的ASP项目源码,这些源码采用了经典的ASP技术开发,结构清晰、注释详细,帮助用户轻松理解整个项目的逻辑和实现方式。通过这些源码,用户可以学习到ASP的基本语法、服务器端脚本编写方法、数据库操作、用户权限管理等关键技术。 数据库设计文件:为了方便用户更好地理解系统的后台逻辑,每个项目中都附带了完整的数据库设计文件。这些文件通常包括数据库结构图、数据表设计文档,以及示例数据SQL脚本。用户可以通过这些文件快速搭建项目所需的数据库环境,并了解各个数据表之间的关系和作用。 详细的开发文档:每个资源包都附有详细的开发文档,文档内容包括项目背景介绍、功能模块说明、系统流程图、用户界面设计以及关键代码解析等。这些文档为用户提供了深入的学习材料,使得即便是从零开始的开发者也能逐步掌握项目开发的全过程。 项目演示与使用指南:为帮助用户更好地理解和使用这些ASP项目,每个资源包中都包含项目的演示文件和使用指南。演示文件通常以视频或图文形式展示项目的主要功能和操作流程,使用指南则详细说明了如何配置开发环境、部署项目以及常见问题的解决方法。 毕业设计参考:对于正在准备毕业设计的学生来说,这些资源包是绝佳的参考材料。每个项目不仅功能完善、结构清晰,还符合常见的毕业设计要求和标准。通过这些项目,学生可以学习到如何从零开始构建一个完整的Web系统,并积累丰富的项目经验。
资源包主要包含以下内容: ASP项目源码:每个资源包中都包含完整的ASP项目源码,这些源码采用了经典的ASP技术开发,结构清晰、注释详细,帮助用户轻松理解整个项目的逻辑和实现方式。通过这些源码,用户可以学习到ASP的基本语法、服务器端脚本编写方法、数据库操作、用户权限管理等关键技术。 数据库设计文件:为了方便用户更好地理解系统的后台逻辑,每个项目中都附带了完整的数据库设计文件。这些文件通常包括数据库结构图、数据表设计文档,以及示例数据SQL脚本。用户可以通过这些文件快速搭建项目所需的数据库环境,并了解各个数据表之间的关系和作用。 详细的开发文档:每个资源包都附有详细的开发文档,文档内容包括项目背景介绍、功能模块说明、系统流程图、用户界面设计以及关键代码解析等。这些文档为用户提供了深入的学习材料,使得即便是从零开始的开发者也能逐步掌握项目开发的全过程。 项目演示与使用指南:为帮助用户更好地理解和使用这些ASP项目,每个资源包中都包含项目的演示文件和使用指南。演示文件通常以视频或图文形式展示项目的主要功能和操作流程,使用指南则详细说明了如何配置开发环境、部署项目以及常见问题的解决方法。 毕业设计参考:对于正在准备毕业设计的学生来说,这些资源包是绝佳的参考材料。每个项目不仅功能完善、结构清晰,还符合常见的毕业设计要求和标准。通过这些项目,学生可以学习到如何从零开始构建一个完整的Web系统,并积累丰富的项目经验。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值