User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So I have tableview where I got different categories for huge amount of items. Would it make more sense to put the categories in grouped tableview or in a normal, or does it matter at all?

share|improve this question
Some more information would be helpful. When to do it one way vs. another way really depends on the context. I'll provide some thoughts in an answer but they'll be fairly general. – Jonathan Jul 7 '11 at 21:40

Some things to think about:

  • Does the user need to access a certain group of records more frequently? Perhaps then a grouped view with this group at the top will be best.
  • Does the user need to look at multiple records in the table view and compare them? What groups of items do they need to look at? If this is grouped by a single field, then displaying grouped tables may make more sense.
  • Do different fields create groupings that matter to different user users, or matter at different times? Perhaps a general-purpose grouping is not the answer, but column sorting may work better.
  • How many records are part of table? Will they all be displayed on the same page or paginated? If you are paginating records then groups may provide an additional cue to keep track of place.
  • How much space do you have for columns? pulling a field out to define a group will give you more horizontal space.
share|improve this answer
Well. I will post image soon. – Samuli Lehtonen Jul 8 '11 at 14:54

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.