Hot answers tagged

147

This is where UX gets hard There's nothing inherently wrong with your interface. It appears to be handling a large amount of information in a reasonably clear and standardized way. But there is something wrong with your interface: The users don't feel comfortable in it. That's a complicated problem to solve, but it is the heart of every UX design project. ...


94

Is not intrusive, and is barely noticeable. And Word users that are familiar with it, will recognize it easily, so you'll have some external consistency. Based on the comments, I edited this answer to note that is necessary to generate a difference between text and interpunct so I used a slighty bigger font size and changed the color from black to light ...


77

CSS / Javascript drop down menus that don't have a delay specified on them so you experience the "diagonal problem" (via Jakob Nielsen)


75

There's an easy way to approach user-select: none, and that is to ask a single question: Would selecting the text be the primary/secondary interaction a user would intend if touching the screen there, or would it be a hindrance to the task they were trying to carry out? Image Carousels (love them or hate them) are a fantastic example of this. In a touch ...


74

If your app is the same as your website, then why have an app? As a mobile user, it drives me crazy how every single website tries to convince me to download a dedicated app, which often turns out to be nothing more than the same web functionality repackaged. This adds no user experience benefit at all. I'm sure the company in question thinks it is a ...


72

My go to has always been an blank, ␣ (␣) or the underbracket character ⎵ (⎵), which is wider. You can see them here on w3.org. I've used the underbracket a bunch in my programming courses to show space in program output. For example ...


70

Poor form validation design. I hate it when I submit a form which fails validation and the application does any of the following: Fields are BLANK when the form reloads. This happened to me while signing up for a web app on my iPhone. I was royally pissed because there were over 8 fields. Displays only one validation error per form submit. Does not ...


68

Not putting clickable labels on checkboxes and other form fields. It's so easy to do. See the HTML <label> tag.


66

Context is important here. Sound feedback can be very useful when people need or expect it. The ATM. That annoying credit card pad that only accepts a button push every 3rd time at the pharmacy check out line. A cash register. And maybe it can be important for your web site, but realize that that is a very atypical behavior and not something your users are ...


65

Option 3 with no intrusive validation. 1 sucks because it's out of the norm. Copy and paste may or may not work. Tabbing to the next field may or may not work. People are good at correcting mistakes and the limited fields mess up their muscle memory. For example I might type 1912 When I meant 192 My fingers will nearly instantaneously correct ...


64

In general, you shouldn't use it globally. Oftentimes, users select some text, maybe to highlight something to show a part of the text to a friend, to copy text or to mark the text just to be able to read it better (which I do when the text is pretty wide and it's hard to follow the text wrap in the sentence). However, there are really good examples where ...


62

You could try to use a short description of the actual cause, e.g. no budget


61

You're looking at the problem from the wrong angle. A user could also open a different browser, or use a second device, which means you can't rely on the idea of opening tabs(and preventing it), nor on IP address. Your solution needs to be server-side. Signing them out would just annoy them. Either make it so your website show them the same game no matter ...


61

Repeating those table row labels for every game box is contributing a lot to the perceived clutter IMO. Also is all that information necessary? You could perhaps try simplifying, but add the ability to expand if necessary.


53

Neither. Settings are different from questions. This may seem obvious, but it drives a difference in UX design. Yes and No may be reasonable answers to a question: Are you a muggle? Yes / No However, in your case you are really asking the user to make a setting. For settings, don't make the user think too much: Describe what the radio button does ...


50

Poor design when it comes to Primary vs Secondary action buttons on forms. http://www.lukew.com/resources/articles/psactions.asp


50

Corners on a picture of a face (which most people will choose as an avatar) are not just unnecessary visual noise, they may make the image harder for us to process. Things with rounded edges are considered easier on the eye than things with sharp edges. Circles are easier for the visual system to process, so generate less cognitive load. However, many of us ...


47

Users use the back & forward buttons in their browser (or on their mouse). And they use the refresh button too. So be careful with form posts on your website. Nobody likes this... This dialog box appears when you refresh the page that the data is posted to. Fortunately, it can be avoided by using method="get" when possible, or method="post" ...


44

Balsamiq Mockups So, since you mentioned it, I'll add Balsamiq to start the list :) The Web version isn't in full release yet, but the desktop app is pretty nifty. When it does go live, the product will exist here: Balsamiq Web app project page Otherwise, there's always the desktop app (at the same URL, just click the "Desktop App" link).


44

10 seems quite a wide range for what is essentially a 'do I like this' poll. Does it really make a difference if Fifteen people rate Availability at 7 and Thirty people rate it at 8? I'm not sure you really need that much accuracy in such a subjective poll. Why not use a standard 5-point Likert scale? (Image from the Wikipedia article.)


42

On any site is is not ideal to break a user's expectations. As a user expects to be able to navigate the internet with tabs in their browser, you shouldn't break it.


40

JavaScript links. You can't middle-click open a new tab for javascript:loadPage(34576).


40

The short answer is: if you already account for 6 different mobile screen resolutions, you should also account for many large screen resolutions - keep things consistent. The long answer: You're over-complicating this. There're 28 "standard" resolutions and creating a dedicated layout for all of them takes too much precious time. Instead, you should follow ...


40

A checkmark represents something positive - usually 'good' or 'correct', so you shouldn't use it to represent something negative like 'serious violation'. I would focus on using either a X or a warning sign, with a preference for the warning sign. Icon aside, I don't see any good reason to have columns for both 'serious violation' and 'Overall alert'. The ...


37

HTML + CSS + JS That's pretty much the only option if you're looking at high fidelity prototyping. I'm an advocate of going hi-fi (code it) or stick very lo-fi (sketchy apps like Balsamiq). Unless you're testing relatively tame interactions, I find solutions like Axure and the like a bit dangerous. It implies hi-fidelity, but you can't finesse the ...


37

This is what I think. If you look at an image, all you need is the centre most area of it to understand what it is about. If the centre of the image is removed, it becomes really hard for us to understand what the image is about, whereas if the corners are removed and the centre is preserved, we can still figure out what the image was about. The above is ...


36

Double-clicking on the web should be avoided because it goes against the general practice of single-clicking links, and would likely be confusing. Jacob Nielsen says it best: ...double-click must die since it causes novice users great difficulties and since it conflicts with the single-click interaction style of the Web If your application does a good ...


34

If you're looking for the most SEO friendly URLs that are also human readable, then I would recommend using all lowercase, hyphenated URLs, as that is what Google recommends in their Webmaster tools documentation. However, if SEO doesn't matter for your web app (if, for instance, it all lives behind a login requirement), then you can use whatever ...


33

Asking mandatory personal information in registration forms when they are not necessary. Examples : asking an address on a website where this information is useless Forcing to enter a "real" name ... Making this information mandatory is the best way to get a really polluted database full of "dummy", "foo@foo.com", etc. because most people don't like to ...


30

There are a number of other ways you can look at as well The walk-through approach : The walk-through approach walks your users through the app like how Google does it. Its also called the joyriding approach. To quote this article The “joyriding” approach walks the user through the features of an app or highlights the key features. It’s great ...



Only top voted, non community-wiki answers of a minimum length are eligible