Hot answers tagged


It is a combination of manufacturing and usability... but mostly manufacturing. Doing a quick web search for "why are soda cans round" (Google does a decent job) yields multiple insights in the issue. But the only result you need to visit is engineerguy's YouTube video (you should also be Subscribed to engineerguy, because he is awesome). The Ingenious ...


I think a start would be to make it clear the total number of tests and/or total number of cards at the top of each card. And also the breakdown of how many rows you seeing out of that total. e.g. Total Tests: 22 Page: 1 of 2, showing tests 12 of 22 Mockup 1


I'd go with a color that'll always retain stark contrast. I'd also avoid venturing too far outside of the styles that that users are generally familiar with. Because you're working in an atypical style, if you deviate and use unfamiliar elements you may risk confusing a percentage of your users. Here's what i think i'd recommend.


I would go with something in the shade of the background, but have a more red text in the alert. You can add a border in the shade of the text to make it stand out as an error more, as well.


An interesting question, and one that I think many of us might have pondered before without really diving too deep into the possible issues. From a purely design perspective, I can think of a number of plausible reasons: Convention: the first person did it this way, and then everybody else followed because "that's how it's done". Safety first: separating a ...


Switch sounds perfectly fine to me, but I'd suggest Toggle which is specifically a two-position switch. If you rather want to describe the type of the value, not the UI element, I'd go for Flag.


It matches the user's mental model, which is more important than matching real-world circumstances. Users view a refrigerator as something that "makes cold". Therefore the number 5 corresponds to "more cold" and 1 to "less cold". The mental model of "a device that holds its interior at a constant temperature" is more complex and harder to reconcile with ...


Because crappy designers are everywhere There is almost no excuse for this kind of ambiguous, uncommunicative control labeling when there are so many better patterns to follow with fridge thermostats. Here are some control formats that are far more effective. They communicate the polarity of coldness clearly They are color-blind friendly (some use shapes ...


When describing website functionality, you can usually use "Member" to imply a logged-in user. While someone could technically be a member but not logged in, this is unlikely to be relevant to your discussions. While not logged in, they are effectively seeing the "guest" view of the site. I think this is clear: On the home page, a member will have a ...


Other people have already said "manufacturing" so I will not repeat that. What is worth emphasizing though is that soda cans are pressurized to 2 atmospheres of pressure or more. Side-note: this is why the container is made of metal in the first place. Few other packaging materials can deal with this load ...


Save is a byproduct Save is a byproduct of early hardware- and software design. It doesn't have a common equivalent in the real world. Consider: If you take a pencil and make a mark on paper, that mark doesn't require an extra step in order to become permanent. In other words, it does not need to be saved. The paper may need to be stored somewhere so it ...


A Facebook or Google+ sign-in method can actually encourage people to sign-up at all. Most users value the uncomplicated experience they get when signing up via Google+ or Facebook. Hiding this option behind another click will make this valuable option invisible and prevent sign-ups by "lazy" users.


A bright yellow background with black text would work well. Fits the colour scheme of a warning sign.


How will the data be entered and shown to the user? Presumably a checkbox or tickbox.


The use of distinct colours (e.g. green, orange, red or bronze, silver, gold) can be subject to interpretation, as there are usual meaning associated with specific colours depending on cultural, language, context or any other number of factors. A similar question was asked previously on UXSE, where the target audience was for young children: Which colors ...


The standard color for error messages is red, see this question : One important point to understand is that using conventional colors for errors is important because they make the errors more noticeable. User being annoyed by the color of error message is lot less of a problem than user not being able to complete the form because they didn't ...


In my opinion, Option 2 is the most user friendly. Reasoning: If the hour has its own up and down arrow you do not expect that using the up and down arrow of the minutes can change the hour as well. to me, individual controls means individual effect. If you want to have the effect of changing the minutes influencing the hours, this is what you need: or ...


Authenticated For example: Windows user groups have defined names one of which is Authenticated. The Authenticated Users identity Any user accessing the system through a logon process has the Authenticated Users identity. This identity allows access to shared resources within the domain, such as files in a shared folder that should be accessible ...


You might try adding a white border, then play with the background color. The one color that communicates 'something is wrong' louder than red is the color of death, black.


Option 1: Print on multiple pieces of paper Just out of curiosity, is printing it on two separate pieces of paper an option? Having two papers and a staple indicates clearly to the reader that it isn't a single page document. Option 2: Add something to the end of the test to indicate it is done I wonder if there are workflow type triggers that you ...


There are many good answers about annotating the bottom of the page clearly (I like Dave Haigh's best), but as an alternative, how about making the last task (on each side) indicate that tests continue on reverse -- that way, it's directly in what they're (meant) to be reading/completing? I don't have an image editor to hand, but instead of: download ...


Visible not prominent Within a given component, help users know what to expect by visualizing app state. IOW, keep the arrow visible but clearly inactive. This way users will know where to find it at a glance and will have visual confirmation that the carousel is at the beginning/end. There has to be a better term for this but, recognition over recall ...


It's the same as the floppy disk icon: if there was a natural successor, you would already know what it was. If you don't, it means that no natural successor has emerged. And if one hasn't, frankly, who cares?


That's an accessibility nightmare! Try reversing your error message styles: Red text on a white background.


Both Find and Find and Replace are related functionally as you mention. But both actions seem to be orthogonal in terms of what user need (mindset) they cater to. You will know in advance either you want to find something or you rather want to substitute occurrences of something. In the latter case it just happens that you need to find occurrences of the ...


I think a thing that you can do is something similar to Amazon. When you try to access your bills or profile in amazon, you are asked to login again, since it may be possible that you just forgot to log off on some public pc. Other than that though I don't see much need for "masking" the data once you are logged in (with the exception of credit card ...


First i believe you are well prepared to use only star rating system. As there are other ways around to compare products or profile (artists in your case). Side Note: YouTube switched from a star-based system to the binary thumbs-up\thumbs-down, their ratings shot up many-fold. It could be same in your case, Up-votes/Down-votes would be fine i guess. For ...


I'd use contextual words that relate to the option / question rather than trying to find a one size fits all solution. You might find a good way of representing the options like this but you must consider the context of the language of the option. So for 'Activate Widget?' You would use 'yes' or 'no'. Or for a list of widgets, you might use 'enable' or '...


As you have pointed out, the double click is not a standard behaviour that your users are familiar with in the situation you are describing. It's not good practice to use non-standard interactions where you could use a standard one. Irreversible actions (such as deletion) are usually followed up with a 'sanity check' like "Are you sure? [Yes] [No]".

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