Asbjørn said "usually." Is "usually" not accurate?
How about "many times"? "In a lot of cases, given the right business
context"? (as was the meaning I took from Jared's post...)
Plus, what about Fred Beecher's point in his recent Johnny Holland
article (http://johnnyholland.org/magazine/2009/08/the-iphone-is-not-easy-to-use-a-peek-into-the-future-of-experience-design/
) that the iPhone - for one example of an Apple product - actually
*isn't* easy to use, but we don't care so much about that because it's
a lot of fun?
On Aug 27, 2009, at 10:26 AM, Andrei Herasimchuk wrote:
On Aug 26, 2009, at 10:53 PM, Asbjørn wrote:
A user-centered design (and development) process is usually a good
idea - if
you want your application to be usable to it's end users, that is.
It is? Then how do you explain Apple's products?
Joan Vermette
email: [email protected]
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
