【原文】:[url=http://bokardo.com/principles-of-user-interface-design/]http://bokardo.com/principles-of-user-interface-design/[/url]

作者Joshua Porter为HubSpot的用户体验负责人(HubSpot是最早利用网络社交媒体,搜索销售情报和业绩的互联网营销公司)。

[quote]"To design is much more than simply to assemble, to order, or even to edit; it is to add value and meaning, to illuminate, to simplify, to clarify, to modify, to dignify, to dramatize, to persuade, and perhaps even to amuse." - Paul Rand[/quote]

[b]1、Clarity is job #1[/b]
Clarity is the first and most important job of any interface. To be effective using an interface you've designed, people must be able to recognize what it is, care about why they would use it, understand what the interface is helping them interact with, predict what will happen when they use it, and then successfully interact with it. While there is room for mystery and delayed gratification in interfaces, there is no room for confusion. Clarity inspires confidence and leads to further use. One hundred clear screens is preferable to a single cluttered one.

[b]2、Interfaces exist to enable interaction[/b]
Interfaces exist to enable interaction between humans and our world. They can help clarify, illuminate, enable, show relationships, bring us together, pull us apart, manage our expectations, and give us access to services. The act of designing interfaces is not Art. Interfaces are not monuments unto themselves. Interfaces do a job and their effectiveness can be measured. They are not just utilitarian, however. The best interfaces can inspire, evoke, mystify, and intensify our relationship with the world.

[b]3、Conserve attention at all costs[/b]
We live in a world of interruption. It's hard to read in peace anymore without something trying to distract us and direct our attention elsewhere. Attention is precious. Don't litter the side of your applications with distractible material…remember why the screen exists in the first place. If someone is reading let them finish reading before showing that advertisement (if you must). Honor attention and not only will your readers be happier, your results will be better. When use is the primary goal, attention becomes the prerequisite. Conserve it at all costs.

[b]4、Keep users in control[/b]
Humans are most comfortable when they feel in control of themselves and their environment. Thoughtless software takes away that comfort by forcing people into unplanned interactions, confusing pathways, and surprising outcomes. Keep users in control by regularly surfacing system status, by describing causation (if you do this that will happen) and by giving insight into what to expect at every turn. Don't worry about stating the obvious…the obvious almost never is.

[b]5、Direct manipulation is best[/b]
The best interface is none at all, when we are able to directly manipulate the physical objects in our world. Since this is not always possible, and objects are increasingly informational, we create interfaces to help us interact with them. It is easy to add more layers than necessary to an interface, creating overly-wrought buttons, chrome, graphics, options, preferences, windows, attachments, and other cruft so that we end up manipulating UI elements instead of what's important. Instead, strive for that original goal of direct manipulation…design an interface with as little a footprint as possible, recognizing as much as possible natural human gestures. Ideally, the interface is so slight that the user has a feeling of direct manipulation with the object of their focus.

[b]6、One primary action per screen[/b]
Every screen we design should support a single action of real value to the person using it. This makes it easier to learn, easier to use, and easier to add to or build on when necessary. Screens that support two or more primary actions become confusing quickly. Like a written article should have a single, strong thesis, every screen we design should support a single, strong action that is its raison d'etre.

[b]7、Keep secondary actions secondary[/b]
Screens with a single primary action can have multiple secondary actions but they need to be kept secondary! The reason why your article exists isn't so that people can share it on Twitter…it exists for people to read and understand it. Keep secondary actions secondary by making them lighter weight visually or shown after the primary action has been achieved.

[b]8、Provide a natural next step[/b]
Very few interactions are meant to be the last, so thoughtfully design a next step for each interaction a person has with your interface. Anticipate what the next interaction should be and design to support it. Just as we like in human conversation, provide an opening for further interaction. Don't leave a person hanging because they've done what you want them to do…give them a natural next step that helps them further achieve their goals.

[b]9、Appearance follows behavior (aka form follows function)[/b]
Humans are most comfortable with things that behave the way we expect. Other people, animals, objects, software. When someone or something behaves consistently with our expectations we feel like we have a good relationship with it. To that end designed elements should look like how they behave. In practice this means that someone should be able to predict how an interface element will behave merely by looking at it. If it looks like a button it should act like a button. Don't get cute with the basics of interaction…keep your creativity for higher order concerns.

[b]10、Consistency matters[/b]
Following on the previous principle, screen elements should not appear consistent with each other unless they behave consistently with each other. Elements that behave the same should look the same. But it is just as important for unlike elements to appear unlike (be inconsistent) as it is for like elements to appear consistent. In an effort to be consistent novice designers often obscure important differences by using the same visual treatment (often to re-use code) when different visual treatment is appropriate.

[b]11、Strong visual hierarchies work best[/b]
A strong visual hierarchy is achieved when there is a clear viewing order to the visual elements on a screen. That is, when users view the same items in the same order every time. Weak visual hierarchies give little clue about where to rest one's gaze and end up feeling cluttered and confusing. In environments of great change it is hard to maintain a strong visual hierarchy because visual weight is relative: when everything is bold, nothing is bold. Should a single visually heavy element be added to a screen, the designer may need to reset the visual weight of all elements to once again achieve a strong hierarchy. Most people don't notice visual hierarchy but it is one of the easiest ways to strengthen (or weaken) a design.

[b]12、Smart organization reduces cognitive load[/b]
As John Maeda says in his book Simplicity, smart organization of screen elements can make the many appear as the few. This helps people understand your interface easier and more quickly, as you've illustrated the inherent relationships of content in your design. Group together like elements, show natural relationships by placement and orientation. By smartly organizing your content you make it less of a cognitive load on the user…who doesn't have to think about how elements are related because you've done it for them. Don't force the user to figure things out…show them by designing those relationships into your screens.

[b]13、Highlight, don't determine, with color[/b]
The color of physical things changes as light changes. In the full light of day we see a very different tree than one outlined against a sunset. As in the physical world, where color is a many-shaded thing, color should not determine much in an interface. It can help, be used for highlighting, be used to guide attention, but should not be the only differentiator of things. For long-reading or extended screen hours, use light or muted background colors, saving brighter hues for your accent colors. Of course there is a time for vibrant background colors as well, just be sure that it is appropriate for your audience.

[b]14、Progressive disclosure[/b]
Show only what is necessary on each screen. If people are making a choice, show enough information to allow them the choice, then dive into details on a subsequent screen. Avoid the tendency to over-explain or show everything all at once. When possible, defer decisions to subsequent screens by progressively disclosing information as necessary. This will keep your interactions more clear.

[b]15、Help people inline[/b]
In ideal interfaces, help is not necessary because the interface is learnable and usable. The step below this, reality, is one in which help is inline and contextual, available only when and where it is needed, hidden from view at all other times. Asking people to go to help and find an answer to their question puts the onus on them to know what they need. Instead build in help where it is needed…just make sure that it is out of the way of people who already know how to use your interface.

[b]16、A crucial moment: the zero state[/b]
The first time experience with an interface is crucial, yet often overlooked by designers. In order to best help our users get up to speed with our designs, it is best to design for the zero state, the state in which nothing has yet occurred. This state shouldn't be a blank canvas…it should provide direction and guidance for getting up to speed. Much of the friction of interaction is in that initial context…once people understand the rules they have a much higher likelihood of success.

[b]17、Existing problems are most valuable[/b]
People seek out solutions to problems they already have, not potential problems or problems of the future. Therefore, resist creating interfaces for hypothetical problems, observe existing behavior and design to solve existing problems. This isn't as exciting as blue sky wondering but can be much more rewarding as people will actually use your interface.

[b]18、Great design is invisible[/b]
A curious property of great design is that it usually goes unnoticed by the people who use it. One reason for this is that if the design is successful the user can focus on their own goals and not the interface…when they complete their goal they are satisfied and do not need to reflect on the situation. As a designer this can be tough…as we receive less adulation when our designs are good. But great designers are content with a well-used design…and know that happy users are often silent.

[b]19、Build on other design disciplines[/b]
Visual and graphic design, typography, copywriting, information architecture and visualization…all of these disciplines are part of interface design. They can be touched upon or specialized in. Do not get into turf wars or look down on other disciplines: grab from them the aspects that help you do your work and push on. Pull in insights from seemingly unrelated disciplines as well…what can we learn from publishing, writing code, bookbinding, skateboarding, firefighting, karate?

[b]20、Interfaces exist to be used[/b]
As in most design disciplines, interface design is successful when people are using what you've designed. Like a beautiful chair that is uncomfortable to sit in, design has failed when people choose not to use it. Therefore, interface design can be as much about creating an environment for use as it is creating an artifact worth using. It is not enough for an interface to satisfy the ego of its designer: it must be used!

【转】Principles of User Interface Design相关推荐

  1. User Interface Design for Mere Mortals

    版权声明:原创作品,允许转载,转载时请务必以超链接形式标明文章原始出版.作者信息和本声明.否则将追究法律责任. http://blog.csdn.net/topmvp - topmvp User In ...

  2. 5 Best User Interface Design Pattern Libraries

    为什么80%的码农都做不了架构师?>>>    Elements of Design Pattern Tap Patternry UI Patterns http://uxmovem ...

  3. 2014.10.10 ——Jim Foley第二场讲座User Interface Design——An Overview

    昨天,听了Jim Foley的第二场报告,报告主题是UserInterface Design--An Overview.即讲座内容主要围绕用户界面设计. Foley教授首先从HCI(人机交互)谈起,继 ...

  4. Design with the User in Mind--从用户角度进行设计

    Back to Human Interface Design Design with the User in Mind 从用户角度进行设计 The success of a Mac app depen ...

  5. 用户接口设计的20个原则

    世界级图形设计大师 Paul Rand(保罗.兰德)曾经说过:"设计绝不是简单的排列组合与简单地再编辑,它应当充满着价值和意义,去说明道理,去删繁就简,去阐明演绎,去修饰美化,去赞美褒扬,使 ...

  6. Pair project(刘昊岩11061156 黄明源11061186)

    Pair project members:刘昊岩11061156,黄明源11061186 两周时间,工程下午刚刚结束,现做一些总结. 在现有工程基础上修改schedule 包下方法,主要思想是,也就是 ...

  7. Joshua Porter 20条UI设计原则

     原文链接地址: http://www.niushe.com/news/show-3683.html,转载请注明出处,侵权必究,谢谢! 设计师Joshua Porter发表了一篇文章--<P ...

  8. 【设计理念】Android UI

    以下是作为移动开发者应该清楚认识到的,无论在什么平台上安卓也好苹果也好,甚至HTML 作为开发者,为啥我们要关心UI,前面的一堆通通可以忽略掉,直接跳到最后一条.因为好的UI设计可以帮助我们卖出更多拷 ...

  9. UI设计师,UI工程师

    原文:http://blog.sina.com.cn/s/blog_715975790100vk8p.html 1.UI是什么? UI即User Interface(用户界面)的简称.UI设计则是指对 ...

最新文章

  1. dedecms 后台添加新字段
  2. linux 目标文件格式,Linux工具 - NM目标文件格式分析
  3. 自动化测试用java还是python_现在自动化测试用Java好还是Python好?
  4. OpenVINO——配置与道路分割案例
  5. 用 Visual Studio 和 ASP.NET Core MVC 创建首个 Web API
  6. 如何查看服务器当前的负载信息
  7. 小程序学习(一):点击爱心变色 -- 最简单的事件实现
  8. Docker从入门到实战(四)
  9. vscode 本地调试和本地服务
  10. FreeRTOS(2)---学习FreeRTOS前的准备工作
  11. 任务寄存器TR:GDT、LDT、IDT、TR、TSS之间的关系
  12. android go 刷机教程,安卓用的久了,如何刷机?安卓手机线刷教程
  13. C#多线程学习1——多线程的相关概念
  14. python编程入门书籍-python入门书籍推荐
  15. termux使用记录
  16. cound(count函数)
  17. OrCAD之Design Resources的文件导入新的.dsn文件后,旧的。dsn文件如何去除?
  18. 基于node连接广工大服务器获取信息
  19. php执行fastlane,Fastlane使用说明 自动化打包
  20. c语言如何画出多个散点图,如何制作多参数散点图

热门文章

  1. 开源mock server系统
  2. MySQL笔记:第06章_多表查询
  3. Linux Python离线下载模块
  4. 使用NanoHTTPD在Android上建立本地服务器
  5. Docker学习笔记 — Swarm搭建Docker集群
  6. 最全的Android单元测试教程
  7. 申请TexturePacker序列号
  8. 《数据结构》实验报告五:二叉树
  9. ORB-SLAM2源码阅读(四)—LoopClosing线程SIM3变换
  10. 使用蒲公英平台测试iOS APP(示例)