Hot answers tagged

3

The following are guidelines that I typically use when making this decision. Tables are good when comparing data points across records/sorting/filtering. Use a table display when: it is important to be able to visually compare values from several different records (e.g. which address records are from Spain, order records by users' last name) you'd like ...


3

"Loading" screens, progress bars, spinners, or the like are necessary for operations which take enough time that the user needs reassurance that the program hasn't crashed or become unresponsive. For shorter-duration operations, a spinner or loading screen can actually increase the perceived duration (if not the actual duration) of the delay. There has ...


2

Radio buttons with all 3 options This is a very common scenario, and many sites use either select or radio buttons interchangeably. However, it's recommended to have all options visible at all times, not to mention radio buttons take only one click, while select requires click-->travel-->select If possible, use radio buttons rather than drop-down ...


2

You could introduce some way to set a specific priority (an icon, double clicking the existing priority column, etc). If I need to move from 345 to 13, I double click the 345 and type 13, hit enter and that row zips up to position 13 (former 13->14, 14->15, etc). I would likely combine multiple solutions. Click and Type is good for setting a specific ...


1

No, there is no sensible reason for doing this. It is bad UX, plain and simple. Disabling pasting into a password field is actually encouraging bad passwords. Password managers automatically clear out the clipboard after pasting, so that argument is no longer valid.


1

There are guidelines about keeping your user adequately informed about system response and delays: Response Times: The 3 important Limits by Jakob Nielsen This article was originally written in 1993 but was updated in 2014. The basic advice regarding response times has been about the same for thirty years [Miller 1968; Card et al. 1991]: 0.1 ...


1

Why don't you ignore special characters and sort them based only on alphabetical characters?


1

You might do two versions and A/B test them to compare the user reception and content results. One with confirmation checkbox (additional step) that blocks the 'Submit' action. Second one could be sth simplified, like this: It's clear call to action and should raise the awareness of the newcomer but would not block the flow of the frequent user.


1

The best solution is typically option 3. Say the screen holds roughly 10 items, on page load send out the request for those 10 items and the 10 items immediately proceeding them (20 total). Then when the user scrolls past your first 10 items send the request for the third set of 10 items and load those in. This way the user will always have a buffer as they ...


1

I'm not normally an advocate for browser sniffing but this is one case where it may be highly useful. If you sniff out the browser (say Safari on iOS) you can display a message positioned correctly and give a directional arrow to indicate that the user can add to their home screen. Now doing this all the time and blocking part of the precious Real estate ...


1

I think you are talking about the carats. Jquery's UI library has defined line of code for every particular icon. But try not to use these on the headers. As for the headers the UI looks intuitive when we use icons like hamburger, kebab etc. Carats are for the in page navigation only.



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