Hot answers tagged

9

Avoiding the dilemma There's an possible solution without falling into this dilemma: Give users the choice, just by adding a checkbox below the search/filter input which specifies "Search in hidden columns too" or some similar text. download bmml source – Wireframes created with Balsamiq Mockups If for some reason that's not enough I'd choose ...


2

No references to offer, sorry. Only my opinion based on experience: An empty table tells the user that the current page could possibly have some relevant info (they can deduce the kind of info and layout from column headers). Rule of thumb I apply (in enterprise environment): empty table is useful if the user can do something on the same page to ...


2

So it boils down to whether the search is on the data or just the current view of the data? I'd personally go for 4. Sometime columns are hidden just because of space restriction rather than lack of interest, though obviously the user tends to keep the columns they are most interested in, however as rewobs said often a user will forget what they can't see ...


2

I choose (4) at first but after some careful analysis, I think (3) would fit your design better. The reason being that your search itself is already a filtering mechanism (keywords). It doesn't make sense to do further filtering on your results by hiding/showing relevant boxes. Also when I choose to hide a column, I am explicitly indicating that I'm not ...


1

In order to answer your own question, ask yourself how this UI works and dig deeper into what's being communicated to the user. What does each row do? The rows' function(s) should dictate their appearance. Are they clickable? Do they do something in the same page or link elsewhere? If they are clickable and navigate to a new page, you might want to ...



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