Timeline for What are common UI misconceptions and annoyances?
Current License: CC BY-SA 2.5
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 14, 2012 at 0:23 | review | Low quality posts | |||
| Aug 14, 2012 at 10:21 | |||||
| May 24, 2011 at 0:57 | comment | added | Nick Bedford | The user interface is one of the most important parts of a piece of software. | |
| Aug 30, 2010 at 2:02 | comment | added | jeef3 | I believe requirements should be designed first. Requirements define functions (not functionality) without mention or implication of graphical appearance. Then a user interface is designed around the requirements. I actually hate the reverse: "We will build the back-end first and then you can skin it" as then you just end up with an interface that exposes the "back-end" rather than a user-centred design. | |
| Aug 22, 2010 at 14:49 | comment | added | Tim Sullivan | For all intents and purposes, the UI is the functionality, from the perspective of the user. Of course you need to know what the application is going to do, in broad strokes, but the UI design is going to bring up what is really important. | |
| Aug 18, 2010 at 9:54 | comment | added | naugtur | Functionality is designed first, otherwise you don't know what you're doing. Functionality is "what the app's for" not "what came from implementation" | |
| Aug 17, 2010 at 19:34 | comment | added | GSto | I disagree. I think that the UI should be designed first, and the functionality figured out later. or simultaneously, if you have people working on a form of MVC architecture. | |
| Aug 16, 2010 at 21:49 | history | answered | Dan Udey | CC BY-SA 2.5 |