Tag Info

New answers tagged

0

Personally, I think your main issue is to use a table, which complicates things and provides an affordance that collides with what you want to achieve. Think about this: I see your categories list, and see there are 10 per page. Great. Now, I expand your category... and now I see subcategories but some of the categories I was seeing disappeared! This is a ...


1

You are right that a good option would be to eliminate the overall parent/child relationship from the results table. Users don't 'search' for a category, they browse it; meaning a user would select Computer Hardware from some sort of category listing and then browse its children for further refinement. Both Amazon and PCPartpicker handle their content in ...


0

I think an easier way to look at the problem is by thinking about the rows as "denormalized" by including the category as part of the name or another column for each "child row". And when the user searches for something then include both the name and the category in the search. So if the search string matches a category then it would match all items ...


0

I dont think one big list is the way to go. Show all the parent categories as big tappable boxes. Let user drill down. It will be easier to find what they are looking for that way vs having to scroll through a big list. For search, show all entries that match. In each entry you can show a clickable hierarchy of its parents.


0

I wouldn't auto-collapse because it's unexpected. It could cause a drastic change in the appearance of the list upon drag initiation. Plus it raises the question of "do you automatically uncollapse after the drop or cancel?" I'd also avoid a special reordering mode - I think that would cause more confusion than it's worth. Drag/drop + scrolling is always ...


1

If you have a menu in the left rail for the top categories, perhaps then you could use drag and drop for sorting by the category names. Similarly to Asana.



Top 50 recent answers are included