Talk:User interface design

message: not sure whether these two should be merged. For ease of discussion please talk about this on Talk:Interaction design.  —Headlouse 18:29, 16 November 2005 (UTC)
thread_title: Comment

message: There should be a clear distinction between User Interface Design and User Interface Engineering.--Iteration 03:54, 10 December 2005 (UTC)
replies: text: Yeah I agree with that. That's not what I was stating should be merged. Headlouse 08:01, 23 December 2005 (UTC)
replies: text: If this particular user Mdd is allowed to pull everything that has to do with software development out from under that umbrella and put it under the umbrella of software engineering, then there will be no distinction. Pay attention to what's happening with the software development process and related articles under the template. Oicumayberight (talk) 00:57, 22 October 2008 (UTC)
thread_title:  Design vs. Engineering 

message: The external links section seems to have been taken over by self-promoters.  While I can imagine some good arguments for Norman's and Nielsen's links, I'm for getting rid of all of them, reminding everyone of the appropriate policies here, then letting people try again.  (Ronz 20:08, 26 May 2006 (UTC)
replies: text: Organized and cleaned them up a bit.--Ronz 19:08, 2 June 2006 (UTC)
thread_title:  External Links 

message: The term intuitive is discouraged by UI designers as meaningless (see ). I'll rewrite the lead paragraph to avoid using it. Diego (talk) 17:50, 7 February 2008 (UTC)
thread_title:  "Intuitive" is not intuitive 

message: Brenda Laurel has contributed interesting perspectives to UI design research. I think it would be worthwhile to add perspectives like this to this page. RedTech14 (talk) 18:21, 15 March 2013 (UTC)
thread_title:  Expand Interface Design Research 

message: Not sure what to do, but cite #5 is a dead link right now. Just thought I should let somebody know.
Mattrulz127 (talk) 16:49, 25 July 2013 (UTC)
thread_title:  Citation missing 

message: I have reverted this good faith edit from a new editor, but I make a mental note that the article needs expansion on the reasons why GUIs need good design and the benefits this provides (maybe with a summary of user-centered design). Diego (talk) 15:57, 30 April 2014 (UTC)
thread_title:  Benefits 

message: Add the following research:
According to a study by Stafford et. al, each member of an interface development team can be placed in one of the following four categories:
* Conceptual supervisors – People who envision the project. They know what they want the interface to be able to do and they are responsible for guiding the other members of the team to ensure that their vision is realized.
* Visual Designers – Professionally trained in the art of information design. They help conceptual supervisors visualize the interface.
* Programmers/Implementers – They are responsible for functionality; they interpret an interface design by writing the code to transform it into a functioning tool.
* User – They test the interface and verify that they find it usable. They give input that helps the Programmers/Implementers fine tune the interface, making the interface behave in a manner that is more familiar and easy to use. User study was invaluable in helping refine interface design. Thanks to user feedback, the interface design is now visually connected to the rest of the interface and behaves in a manner that users find more familiar and easy to use. 
Each type of contributor is invaluable and the most successful projects will have at least one representative of each category involved throughout implementation.
.
Hectorlopez17 (talk) 00:25, 4 February 2017 (UTC)
thread_title:  Research