Tag Info

Hot answers tagged

20

Users pick avatars that are not always representative of their "real life" appearance. Often picking an avatar which doesn't match their true age/gender/ethnicity etc. This concept of an avatar allowing you to present yourself differently than in real life I imagine is strongly embedded with users. So if you want to capture real data you would be best of ...


9

If you need a piece of information from the user, ask for it. Trying to trick it out of them is likely to get you bad data (in particular, female users will often pick male avatars to hide their gender, and a significant subset of male users will pick female avatars), and may backfire if users realize you're trying to trick them.


6

None of your avatars resemble my appearance at all, so I would have to select based on other criteria. I might pick the lower right one, because I think he looks cute. I'm a 60+ woman. Even among those who pick an avatar based on some similarity to their own appearance the similarity might be in skin color (already mentioned in another answer), hair color, ...


5

A few different ideas come to mind. 1 - make the label color match the associated line color, so even if they overlap it's clear which label belongs to which line. 2 - Put each label in a containing div, possibly giving that containing div a border the same color as its associated line, with an opaque white background ... and possibly when a user ...


5

Others have mentioned already that avatars not always correspond to the person's true gender and/or age. Another problem is that a number of people will struggle with understanding what avatar represents what age group. From the above avatars you showed, I'm struggling with figuring out who is the teenage woman and who is the 20-40 year old. I believe the ...


5

This is known as "microcopy" in the UX world. A couple of good resources include http://www.smashingmagazine.com/2013/06/17/five-ways-prevent-bad-microcopy/ Nielsen-Norman group has a number of articles and training conferences on writing for the web: http://www.nngroup.com/topic/writing-web/ One of the big problems with form fields and validation, ...


3

What about using the method most websites or applications use for credit card information and show the last or first few characters of the values, with the rest as blobs or stars. This could be in the placeholder attribute for a form field, or perhaps as normal text, with an edit button next to it, which swaps the text to a form field. Try this fiddle for ...


2

Is there any big difference when it comes to designing for people aged 60 + and people aged 50? Technological know-how, perhaps. For example, people who are 60+ might have never used a computer aside from simple tasks, but those who are 40-50 might have some experience with a bit more. This would depend on your user-base, of course. You should also ...


2

Create fields for all the main address components, including postal/zip codes, but don't make them mandatory or put restrictions on format. People who are used to always including postal/zip codes will include it when they see the spot on the form. If this is a shipping address, and they actually want to receive their purchase, they are motivated to ...


2

I would say there there is just as much change of a user missing a poorly sign-posted rollover on desktop as mobile. I use a + symbol to indicate more in these instances, and sometimes where there is a series of rollovers containing more info, I have the first one open by default to show the user what's there. Generally I really don't think we should be ...


2

Something like what coops suggested... Present two listboxes on the screen, on labeled "type 1" and the other "type 2". Start with all of your files in the "type 1" listbox. When any file is picked in that listbox, move all of the selected files to the "type 2" listbox. Only enable the submit button when one entry in each listbox is selected. You could ...


2

Mark the fields that are required for submitting the order. I work on a project with a similar situation. Users can Save the order any time (for completion later) or they can Submit the order to be processed. Saving the order triggers the usual invalid format errors inline and such and is triggered with a Save button at the bottom of the form. This is ...


1

One option would be to give the user the ability to hide one or more of the lines, and the ability to display hidden lines again. Postscript: Based on what dayluloli stated: The lines are often close together and overlap. The legend should follow the end-of-line. Thus, the lines and legend should be presented in the graph. With the four lines in the ...


1

Aside your questions you should take a look at accessibility, as ipavl already stated in his comment. To get started you could take a look at the anySurfer website, if I'm not mistaken the label is only valid in Belgium but they offer a complete and normative checklist with code examples and solutions for common problems. Personally I think the majority of ...


1

I don't see any problem in keeping the same interface as Excel, if you try something get sure of adding features without drawbacks for the user. If your concern is about keeping the headers visible all the time, you could take a look at this StackOverflow question where the answer mention the floatThead Plugin which gives you various options to display ...


1

I would attempt to make this form behavior vertical instead of horizontal. It's hard to know if this option is on the table - as I am not privy to the rest of the interface, but I think some of the problem stems from the horizontal growth of the form coupled with the confirm button under the textara. And pertaining to older users, a vertical orientation ...


1

Isn't this the perfect thing you can test for? Make some wireframes and test. Make some higher fidelity prototypes and test again. This is not something you have to guess about, nor does it make sense to ask others to guess for you. On a side note - if you are testing for nude/not nude then I think you can go a lot smaller than 240x240. I just went to ...


1

Just make them clear. Like "Please enter a phone number" for a missing required. Or "Please enter a valid phone number. The phone number you have entered is too short." Tell the user exactly what is required. It is also best to validate before submission with JavaScript and give them instant feedback. Show the error message right near the input field, and ...


1

What's wrong with an alphabetical list? Split them into five columns of 10 states each with the states read from to top to bottom before the next column.



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