blocks|key|364153|text|(窃取自Joel+:o)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|364154|不要禁用/删除选项-当用户单击/选择它时，会给出一条有用的消息。|364155|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

(Stolen from Joel :o) )

Don't disable/remove options - rather give a helpful message when the user click/select it.

blocks|key|364175|text|我试着适应环境。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|364176|在为Windows应用程序开发时，我使用Windows+Vista+User+Experience+Guidelines，但当我开发web应用程序时，我使用适当的指南，因为我开发荷兰网站时，我使用基于万维网联盟(W3C)的Web+Content+Accessibility+Guidelines+(WCAG+1.0)的"Drempelvrij"+guidelines。|offset|length|364177|我这样做的原因是为了减少新用户的学习曲线。|364178|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/aa511258.aspx|1|http://www.w3.org/TR/WCAG10/|2|http://www.drempelvrij.nl/richtlijnen^0|0|K|14|0|33|1B|1|4F|O|2|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]|$D|Y|E|Z|1|10]|$D|11|E|12|1|13]]|A|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]|R|$5|K|L|M|A|$N|S]]]]

I try to adapt to the environment.

When developing for an Windows application, I use the <a href="http://msdn.microsoft.com/en-us/library/aa511258.aspx" rel="nofollow noreferrer">Windows Vista User Experience Guidelines</a> but when I'm developing an web application I use the appropriate guidelines, because I develop Dutch websites I use the <a href="http://www.drempelvrij.nl/richtlijnen" rel="nofollow noreferrer">"Drempelvrij" guidelines</a> which are based on the <a href="http://www.w3.org/TR/WCAG10/" rel="nofollow noreferrer">Web Content Accessibility Guidelines (WCAG 1.0)</a> by the World Wide Web Consortium (W3C).

The reason I do this is to reduce the learning curve of a new user.

blocks|key|3157217|text|正如我的数据结构教授今天指出的那样:向普通用户说明你的程序是如何工作的。我们程序员经常认为我们的程序很有逻辑性，但普通用户可能不知道该怎么做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3157218|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

As my data structure professor pointed today: Give instructions on how your program works to the average user. We programmers often think we're pretty logical with our programs, but the average user probably won't know what to do.

blocks|key|364227|text|试着在对话框中使用动词。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|364228|它意味着使用|364229|​|364230|📷|atomic|offset|length|364231|364232|而不是|364233|364234|364235|364236|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/cb9cc3851fea10468245f81516e5fb6f.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/d3623a53e16f5f4af1d0c7d01b0a32c6.png^0|0|0|0|0|1|0|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|14|8|@]|9|@$I|15|J|16|1|17]]|A|$]]|$1|K|3|E|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@]|9|@]|A|$]]|$1|N|3|E|5|6|7|1A|8|@]|9|@]|A|$]]|$1|O|3|G|5|H|7|1B|8|@]|9|@$I|1C|J|1D|1|1E]]|A|$]]|$1|P|3|E|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X|Y|-4]]|Z|$5|T|U|V|A|$W|10|Y|-4]]]]

Try to use verbs in your dialog boxes. 

It means use 

<img src="https://i.stack.imgur.com/R8Jmu.png" alt="alt text">

instead of 

<img src="https://i.stack.imgur.com/Yrxwz.png" alt="alt text">

blocks|key|3370182|text|如果你正在为网络或任何前台软件应用程序做任何事情，你真的应该读一读……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3370183|Don't+make+me+think+-+Steve+Krug|offset|length|3370184|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0321344758^0|0|0|W|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

If you're doing anything for the web, or any front-facing software application for that matter, you really owe it to yourself to read...

<a href="https://rads.stackoverflow.com/amzn/click/com/0321344758" rel="noreferrer" rel="nofollow noreferrer">Don't make me think - Steve Krug</a>

blocks|key|3370205|text|试着考虑你的用户想要实现什么，而不是需求是什么。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3370206|用户将进入您的系统并使用它来实现目标。当你打开calc时，你需要在90%25的时间里进行简单的快速计算，这就是为什么默认情况下它被设置为简单模式的原因。|3370207|因此，不要考虑应用程序必须做什么，而是考虑用户将会做什么，可能会感到无聊，并尝试根据他的意图进行设计，尝试让他的生活变得更容易。|3370208|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Try to think about what your user wants to achieve instead of what the requirements are.

The user will enter your system and use it to achieve a goal. When you open up calc you need to make a simple fast calculation 90% of the time so that's why by default it is set to simple mode. 

So don't think about what the application must do but think about the user which will be doing it, probably bored, and try to design based on what his intentions are, try to make his life easier.

blocks|key|362830|text|《日常生活的设计》--唐纳德·诺曼|type|unstyled|depth|inlineStyleRanges|entityRanges|data|362831|这是设计知识的典范，也是世界各地大学中许多人机界面课程的基础。你不会因为一个网络论坛上的一些评论而在五分钟内设计出一个好的图形用户界面，但是一些原则会让你的思维指向正确的方向。|362832|--|362833|MC|362834|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

The Design of Everyday Things - Donald Norman

A canon of design lore and the basis of many HCI courses at universities around the world. You won't design a great GUI in five minutes with a few comments from a web forum, but some principles will get your thinking pointed the right way.

-- 

MC

blocks|key|362849|text|避免在可能的情况下要求用户做出选择(例如，不要使用配置对话框创建分支！)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|362850|对于每个选项和每个消息框，问问自己:我是否可以提出一些合理的默认行为，|362851|362852|有意义吗？|unordered-list-item|362853|不会妨碍用户？|362854|很容易了解到，我将其强加给用户的成本很低？|362855|362856|我可以用我的掌上电脑作为例子:它的设置真的很简约，我对此很满意。基本的应用程序设计得足够好，我可以简单地使用它们，而不需要进行调整。好吧，有一些事情我不能做，事实上我不得不让自己适应这个工具(而不是相反的)，但最终这真的让我的生活变得更容易。|362857|这个网站是另一个例子:你不能配置任何东西，但我发现它真的很好用。|362858|合理的默认值可能很难弄清楚，简单的可用性测试可以提供许多线索来帮助您解决这一问题。|362859|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|Z|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

Avoid asking the user to make choices whenever you can (i.e. don't create a fork with a configuration dialog!)

For every option and every message box, ask yourself: can I instead come up with some reasonable default behavior that

<ul>
<li>makes sense?</li>
<li>does not get in the user's way?</li>
<li>is easy enough to learn that it costs little to the user that I impose this on him?</li>
</ul>

I can use my Palm handheld as an example: the settings are really minimalistic, and I'm quite happy with that. The basic applications are well designed enough that I can simply use them without feeling the need for tweaking. Ok, there are some things I can't do, and in fact I sort of had to adapt myself to the tool (instead of the opposite), but in the end this really makes my life easier.

This website is another example: you can't configure anything, and yet I find it really nice to use.

Reasonable defaults can be hard to figure out, and simple usability tests can provide a lot of clues to help you with that.

blocks|key|367703|text|向用户示例显示界面。让他们执行一项典型的任务。注意他们的错误。听听他们的评论。进行更改并重复。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|367704|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Show the interface to a sample of users. Ask them to perform a typical task. Watch for their mistakes. Listen to their comments. Make changes and repeat.

blocks|key|362881|text|Be+Powerful+and+Simple|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|362882|哦，还有请一位设计师/学习设计技巧。:)|362883|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/aa511332.aspx^0|0|M|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

<a href="http://msdn.microsoft.com/en-us/library/aa511332.aspx" rel="nofollow noreferrer">Be Powerful and Simple</a>

Oh, and hire a designer / learn design skills. :)

blocks|key|367731|text|永远不要问“你确定吗？”只允许无限制的、可靠的撤消/重做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|367732|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Never ask "Are you sure?". Just allow unlimited, reliable undo/redo.

blocks|key|362915|text|遵循基本设计原则|type|unstyled|depth|inlineStyleRanges|entityRanges|data|362916|362917|Contrast+-让不同的东西看起来像different|unordered-list-item|offset|length|style|BOLD|362918|Repetition+-在一个屏幕上重复相同的风格，对于其他的screens|362919|Alignment+-+Line屏幕元素！是的，包括文本、图像、控件和labels.|362920|Proximity相关元素。用于输入地址的一组输入字段应该组合在一起，并且与用于输入信用卡信息的一组输入字段不同。这是基本的Gestalt+Design+Laws.|362921|362922|entityMap|0|LINK|mutability|MUTABLE|url|https://www.andyrutledge.com/gestalt-principles-1-figure-ground-relationship.html^0|0|0|0|1|0|0|1|0|0|1|0|0|1|1Q|J|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|10|8|@$F|11|G|12|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|13|8|@$F|14|G|15|H|I]]|9|@]|A|$]]|$1|L|3|M|5|E|7|16|8|@$F|17|G|18|H|I]]|9|@]|A|$]]|$1|N|3|O|5|E|7|19|8|@$F|1A|G|1B|H|I]]|9|@$F|1C|G|1D|1|1E]]|A|$]]|$1|P|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

<h2>Follow basic design principles</h2>

<ul>
<li>Contrast - Make things that are different look different</li>
<li>Repetition - Repeat the same style in a screen and for other screens</li>
<li>Alignment - Line screen elements up! Yes, that includes text, images, controls and labels.</li>
<li>Proximity - Group related elements together. A set of input fields to enter an address should be grouped together and be distinct from the group of input fields to enter credit card info. This is basic <a href="https://www.andyrutledge.com/gestalt-principles-1-figure-ground-relationship.html" rel="nofollow noreferrer">Gestalt Design Laws</a>.</li>
</ul>

blocks|key|364697|text|在构造错误消息时，将错误消息设置为以下3个问题的答案(按顺序)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|364698|364699|发生了什么？|ordered-list-item|364700|为什么会发生？|364701|可以做些什么？|364702|364703|这来自“人机接口指南:+Apple桌面界面”(1987年，ISBN+0-201-17753-6)，但它可以用于任何地方的任何错误消息。微软的页面User+Interface+Messages也说了同样的话：“……在出现错误消息的情况下，你应该包括问题、原因以及纠正问题的用户操作。”|offset|length|364704|还包括程序已知的任何信息，而不仅仅是一些固定的字符串。例如，对于错误消息中的“为什么会发生”部分，请使用“原始频谱文件L:\refDataForMascotParser\TripleEncoding\Q1LCMS190203_01Doub+leArg.wiff不存在”而不是“文件不存在”。|364705|将其与臭名昭著的错误消息"An+error+happend.“进行对比。|364706|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/bb246405(VS.85,printer).aspx^0|0|0|0|0|0|0|20|N|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|13|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|14|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|16|8|@]|9|@$M|17|N|18|1|19]]|A|$]]|$1|O|3|P|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

When constructing error messages make the error message be
the answers to these 3 questions (in that order):

<ol>
<li>What happened?</li>
<li>Why did it happen?</li>
<li>What can be done about it?</li>
</ol>

This is from "Human Interface Guidelines: The Apple Desktop
Interface" (1987, ISBN 0-201-17753-6), but it can be used
for any error message anywhere.
There is an <a href="http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGIntro/XHIGIntro.html" rel="nofollow noreferrer">updated version</a> for Mac OS X.
The Microsoft page
<a href="http://msdn.microsoft.com/en-us/library/bb246405(VS.85,printer).aspx" rel="nofollow noreferrer">User Interface Messages</a>
says the same thing: "... in the case of an error message, 
you should include the issue, the cause, and the user action 
to correct the problem."

Also include any information that is known by the program,
not just some fixed string. E.g. for the "Why did it happen" part of the error message use "Raw spectrum file
L:\refDataForMascotParser\TripleEncoding\Q1LCMS190203_01Doub
leArg.wiff does not exist" instead of just "File does
not exist".

Contrast this with the infamous error message: "An error 
happend.".

blocks|key|3157532|text|我用我的祖母测试我的图形用户界面。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3157533|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I test my GUI against my grandma.

blocks|key|3370457|text|对于GUI，标准是特定于平台的。例如，在Eclipse中开发图形用户界面时，这个link提供了很好的指导。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3370458|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.eclipse.org/User_Interface_Guidelines^0|14|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

With GUIs, standards are kind of platform specific. E.g. While developing GUI in Eclipse this <a href="http://wiki.eclipse.org/User_Interface_Guidelines" rel="nofollow">link</a> provides decent guideline.

blocks|key|367822|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|367823|使用谨慎/简单的动画功能来创建从一个截面到另一个截面的无缝过渡。这有助于用户在按钮上创建navigation/structure.|ordered-list-item|367824|Use短标题(如果可能，只有一个单词)的心理导图，清楚地描述操作的本质。|367825|在可能的情况下使用语义缩放(一个很好的例子是如何在谷歌/必应地图上进行缩放，当您将焦点放在某个区域时，可以看到更多信息)。|367826|至少创建了两种导航方式:垂直和水平。当您在不同部分之间导航时，保持垂直；当您在部分或subsection.|367827|Always的内容中导航时，保持结构的主要选项节点可见(屏幕的大小和设备类型允许的位置)。|367828|当您深入结构时，始终保留一个可见的提示(例如，以路径的形式)，以指示您所在的位置。当您希望用户专注于数据(如阅读文章或查看项目)时，|367829|隐藏元素。-但是要当心第5点和第4点。|367830|367831|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|S|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|T|7|@]|8|@]|9|$]]|$1|D|3|E|4|C|6|U|7|@]|8|@]|9|$]]|$1|F|3|G|4|C|6|V|7|@]|8|@]|9|$]]|$1|H|3|I|4|C|6|W|7|@]|8|@]|9|$]]|$1|J|3|K|4|C|6|X|7|@]|8|@]|9|$]]|$1|L|3|M|4|C|6|Y|7|@]|8|@]|9|$]]|$1|N|3|O|4|C|6|Z|7|@]|8|@]|9|$]]|$1|P|3|-4|4|5|6|10|7|@]|8|@]|9|$]]|$1|Q|3|-4|4|5|6|11|7|@]|8|@]|9|$]]]|R|$]]

<ol>
<li>Use discreet/simple animated features to create seamless transitions from one section the the other. This helps the user to create a mental map of navigation/structure.</li>
<li>Use short (one word if possible) titles on the buttons that describe clearly the essence of the action.</li>
<li>Use semantic zooming where possible (a good example is how zooming works on Google/Bing maps, where more information is visible when you focus on an area).</li>
<li>Create at least two ways to navigate: Vertical and horizontal. Vertical when you navigate between different sections and horizontal when you navigate within the contents of the section or subsection.</li>
<li>Always keep the main options nodes of your structure visible (where the size of the screen and the type of device allows it).</li>
<li>When you go deep into the structure always keep a visible hint (i.e. such as in the form of a path) indicating where you are.</li>
<li>Hide elements when you want the user to focus on data (such as reading an article or viewing a project). - however beware of point #5 and #4.</li>
</ol>

blocks|key|364807|text|我已经读了上面的大部分内容，有一件事我没有看到：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|364808|如果用户打算只使用一次界面，那么如果可能的话，只显示他们需要使用的内容是很好的。|364809|如果用户界面将被同一用户重复使用，但可能不是很频繁，禁用控件比隐藏它们更好:用户界面的变化和隐藏的功能不明显(或记不住)，这会让用户感到沮丧。|364810|如果用户界面是由同一个用户经常使用的(在工作中没有太多的变动，即没有很多新用户一直在线)，禁用控件绝对是有帮助的，用户会习惯事情发生的原因，但会防止他们在不恰当的上下文中意外使用控件，并防止出现错误。|364811|这只是我的观点，但这一切都是为了理解你的用户配置文件，而不仅仅是一个用户会话可能需要的内容。|364812|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I've read most of the above and one thing that I'm not seeing mentioned:

If users are meant to use the interface ONCE, showing only what they need to use if possible is great.

If the user interface is going to be used repeatedly by the same user, but maybe not very often, disabling controls is better than hiding them: the user interface changing and hidden features not being obvious (or remembered) by an occasional user is frustrating to the user.

If the user interface is going to be used VERY REGULARLY by the same user (and there is not a lot of turnover in the job i.e. not a lot of new users coming online all the time) disabling controls is absolutely helpful and the user will become accustomed to the reasons why things happen but preventing them from using controls accidentally in improper contexts appreciated and prevents errors.

Just my opinion, but it all goes back to understanding your user profile, not just what a single user session might entail.

What is your best practical user-friendly user-interface design or principle? 

Please submit those practices that you find actually makes things really useful - no matter what - if it works for your users, share it!

<hr>

Summary/Collation

Principles

<ol>
<li>KISS.</li>
<li>Be clear and specific in what an option will achieve: for example, use verbs that indicate the action that will follow on a choice (see: Impl. 1).</li>
<li>Use obvious default actions appropriate to what the user needs/wants to achieve.</li>
<li>Fit the appearance and behavior of the UI to the environment/process/audience: stand-alone application, web-page, portable, scientific analysis, flash-game, professionals/children, ...</li>
<li>Reduce the learning curve of a new user.</li>
<li>Rather than disabling or hiding options, consider giving a helpful message where the user can have alternatives, but only where those alternatives exist. If no alternatives are available, its better to disable the option - which visually then states that the option is not available - do not hide the unavailable options, rather explain in a mouse-over popup why it is disabled.</li>
<li>Stay consistent and conform to practices, and placement of controls, as is implemented in widely-used successful applications.</li>
<li>Lead the expectations of the user and let your program behave according to those expectations.</li>
<li>Stick to the vocabulary and knowledge of the user and do not use programmer/implementation terminology.</li>
<li>Follow basic design principles: contrast (obviousness), repetition (consistency), alignment (appearance), and proximity (grouping).</li>
</ol>

Implementation

<ol>
<li>(See answer by paiNie) "Try to use verbs in your dialog boxes."</li>
<li>Allow/implement undo and redo.</li>
</ol>

References

<ol>
<li>Windows Vista User Experience Guidelines [<a href="http://msdn.microsoft.com/en-us/library/aa511258.aspx]" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/aa511258.aspx]</a></li>
<li>Dutch websites - "Drempelvrij" guidelines [<a href="http://www.drempelvrij.nl/richtlijnen]" rel="nofollow noreferrer">http://www.drempelvrij.nl/richtlijnen]</a></li>
<li>Web Content Accessibility Guidelines (WCAG 1.0) [<a href="http://www.w3.org/TR/WCAG10/]" rel="nofollow noreferrer">http://www.w3.org/TR/WCAG10/]</a></li>
<li>Consistence [<a href="https://rads.stackoverflow.com/amzn/click/com/0385267746" rel="nofollow noreferrer" rel="nofollow noreferrer">http://www.amazon.com/Design-Everyday-Things-Donald-Norman/dp/0385267746]</a></li>
<li>Don't make me Think [<a href="https://rads.stackoverflow.com/amzn/click/com/0321344758" rel="nofollow noreferrer" rel="nofollow noreferrer">http://www.amazon.com/Dont-Make-Me-Think-Usability/dp/0321344758/ref=pdbbssr_1?ie=UTF8&amp;s=books&amp;qid=1221726383&amp;sr=8-1]</a></li>
<li>Be powerful and simple [<a href="http://msdn.microsoft.com/en-us/library/aa511332.aspx]" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/aa511332.aspx]</a></li>
<li>Gestalt design laws [<a href="http://www.squidoo.com/gestaltlaws]" rel="nofollow noreferrer">http://www.squidoo.com/gestaltlaws]</a></li>
</ol>

Best Practices & Principles for GUI design

你认为最实用的用户友好的用户界面设计或原则是什么？请提交那些你认为真正有用的实践--不管是什么--如果它对你的用户有效，请分享它！摘要/排序规则原则明确和具体地说明选项将实现什么:例如，使用动词来表示选择之后的操作(请参阅：KISS.Be。1).使用适合用户需要/想要实现的明显默认操作。使UI的外观和行为适合环境/流程...

问GUI设计的最佳实践和原则
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问GUI设计的最佳实践和原则EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问GUI设计的最佳实践和原则
EN