Hot answers tagged


Try Recommending instead of showing equal choices. The paradox of choice is a funny thing. You can give someone so many options that they no longer have any options at all. There are plenty of psychological studies that show how paralyzing too many choices can be. Presenting tons of options can be a barrier to entry. In order to combat such analysis ...


I would reduce the information and show the user a window per attribute, but only attributes, where the value will change: When the user clicks on 'Discard' or 'Apply Changes' the next attribute will be shown until all attributes are merged. Update: If you do not want to use one window per attribute, I want to suggest you to list all changes and work ...


The solution I've seen is to not use a fixed grid, but a set of fields as required. Each condition has its own row, containing the necessary fields. Since every operator needs one value, one value field is always visible. When the user selects "between", a second field is added for this row only. I have no specific testing results supporting or ...


If I got you right, what you are looking for is an Identicon. It is similar to the text based representation you mentioned, and it's widely used on the web (take Stack Exchange for example). Here is an example:


No, no, no. I currently work with an engine for searching flights. Basically you got two major variations: Cached searches that searches flights in a database containing cached entries (fast, around 1-2 seconds or less per search depending on how large the cache is) Real-time searches via a GDS like Sabre, Amadeus, Worldspan etc (slow, 5-12 seconds per ...


The only responsive industry solution i've met is . With a few adjustments it might even work nicely on the smallest viewports. Just take into account not to use too many products for comparison.

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