关于可用性和“美观”的争论
作为一名 UI 人员（编码和设计用户界面），我经常发现自己处于一种奇怪的境地，与程序员和其他“外行”争论用户界面的质量。
我发现争论颜色、图标或布局之类的事情有点困难，而且似乎没有事实的对错。 但是，尽管没有令人信服的论据，我仍然知道（即感觉）有时解决方案是错误的。 您对此有何看法？ 你会让昂贵的可用性测试甚至客户来决定吗？ 您自学过可用性工程吗？ 您知道有哪些提供论据的好书（例如 Joel Spolsky 的《程序员的用户界面设计》）吗？ 你会避免这样的讨论吗？
As a UI guy (coding and designing user interfaces) I often find myself in the odd situation arguing about the quality of userinterfaces with programmers and other "laymen".
I find it somewhat hard to argue about things like colors, icons or layout and it doesn't seem that there is a factual right or wrong. But still - without having a convincing argument I still know (i.e. feel) that sometimes a solution is just wrong. What is your approach to this? Do you let costly usability test decide or even the customer? Do you educate yourself in usability engineering? Do you know of good books (like Joel Spolsky's "User Interface Design for Programmers") that deliver arguments? Do you avoid such discussions?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我的很多客户都是小客户。 他们没有钱聘请可用性/UI 专家，所以我们必须这样做。 他们理解我的局限性，我们都尽力提供一些常识 - 了解我们正在构建足够好的而不是最好的（UI 方面）。
根据我的经验，大客户对内部应用程序也有同样的态度。 只有当你建造了一些东西来出售时，人们才愿意花额外的钱来解决这个问题。
就我自己而言，我相信没有充分的理由完全无知。 我确实花了一点时间阅读和闲逛。 我找到了很好的材料：
A lot of my clients are small. They don't have the money for a usability/UI expert so we make due. They understand my limitations and we both do our best to bring a little common sense to the table - understanding that we're building good-enough versus the best (UI-wise).
In my experience, large clients have the same attitude toward internal apps. It's only when you build something to sell that people are willing to spend extra money on the problem.
For myself, I believe there's no good reason to be completely ignorant. I do spend a little time reading and puttering. I've found good material with:
最终由客户做出决定，因为客户支付账单。 然而，客户通常付钱给我，因为他们相信我拥有他们不具备的技能和能力。 通常我会尝试向他们解释为什么我认为从设计角度来看特定的布局或颜色选择是有意义的。 如果我有足够充分的理由，超越个人喜好，通常就能成功。 如果没有，那么我就走客户的路。 有时，如果我知道客户真的讨厌他们“想要”的东西，我会完全避免争论/讨论，按照他们的方式去做，让他们告诉我把它改回来。
我要说的一件事。 通常这些讨论最终会产生比我最初的更好的第三种解决方案。 被迫认真思考我的选择来捍卫它们，通常会导致我思考如何解决问题，比原始设计更好地解决客户的观点。
就配色方案而言，您总是希望拥有有品味的客户。 遗憾的是，这种情况并不总是发生。 是的，有时我不得不整合一个解决方案，但由于这个原因，该解决方案并未纳入我的投资组合中。
Ultimately the customer makes the decision because the customer pays the bills. However, the customer is usually paying me because they believe that I have skills and abilities that they don't possess. Typically I'll try to explain to them why I believe a particular layout or color choice makes sense from a design perspective. If I have a good enough reason, beyond personal preference, that usually does the trick. If it doesn't, then I go the customer's way. Sometimes, if I know that the customer will really hate what they "want" I'll just avoid the argument/discussion completely and do it their way and let them tell me to change it back.
One thing that I will say. Often these discussions end up with yet a third solution that is better than my original. Being forced to really think through my choices to defend them often results in me thinking of ways to solve the problem that addresses the customer's perspective better than the original design.
As far as color schemes go, you always hope to have a customer with good taste. Sadly, that doesn't always happen. And, yes, sometimes I've had to put together a solution that doesn't make it into my portfolio for this reason.
Edward Tufte 始终是一个很好的来源。 Mark Miller 做了一个 播客 和一个 有关此内容的截屏视频 .Net 震撼！。 他实际上深入研究了 UI 原则背后的科学，例如最小有效差异原则。
Edward Tufte is always a good source. Mark Miller did a podcast and a screencast about this for .Net Rocks!. He actually went into the science behind UI principles like the principle of least effective differance.