http://embeddedgurus.com/usability-bites/2009/01/three-most-painful-gui-challenges/ A Blog by Niall Murphy Fri, 21 Jan 2011 16:47:04 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://embeddedgurus.com/usability-bites/2009/01/three-most-painful-gui-challenges/comment-page-1/#comment-5 Paul N. Leroux Fri, 06 Mar 2009 17:00:00 +0000 http://embeddedgurus.com/usability-bites/2009/01/19/three-most-painful-gui-challenges/#comment-5 Re Keep it simple. I always like to use the Google home page as an example. It's the most widely used user interface in the world and it serves as the front-end to an unbelievable variety of features, applications, and services. And yet, it is 90% white space -- just a text field and a few links. Which is exactly why everyone feels comfortable using it. Because they can! Re Keep it simple. I always like to use the Google home page as an example. It’s the most widely used user interface in the world and it serves as the front-end to an unbelievable variety of features, applications, and services. And yet, it is 90% white space — just a text field and a few links. Which is exactly why everyone feels comfortable using it. Because they can!

]]> http://embeddedgurus.com/usability-bites/2009/01/three-most-painful-gui-challenges/comment-page-1/#comment-4 Nigel Jones Sun, 08 Feb 2009 16:44:00 +0000 http://embeddedgurus.com/usability-bites/2009/01/19/three-most-painful-gui-challenges/#comment-4 I agree completely with your thoughts on too many features being crammed into products. I've noticed a couple of things that go along with this.1. The developer that resists adding features can easily get the reputation of being 'uncooperative' instead of what they really are - which is protective of the product.2. A lack of understanding that added features tend to have a very high bug rate. I think this comes about because they are tacked on, rather than designed in. I've found this to be a very persuasive argument when it comes to not doing something. I agree completely with your thoughts on too many features being crammed into products. I’ve noticed a couple of things that go along with this.1. The developer that resists adding features can easily get the reputation of being ‘uncooperative’ instead of what they really are – which is protective of the product.2. A lack of understanding that added features tend to have a very high bug rate. I think this comes about because they are tacked on, rather than designed in. I’ve found this to be a very persuasive argument when it comes to not doing something.

]]>