Flag

We stand with Ukraine and our team members from Ukraine. Here are ways you can help

Get exclusive access to thought-provoking articles, bonus podcast content, and cutting-edge whitepapers. Become a member of the UX Magazine community today!

Home ›› Customer Experience ›› Case study: Category hierarchy

Case study: Category hierarchy

by Tornike Kurdadze
3 min read
Share this post on
Tweet
Share
Post
Share
Email
Print

Save

Walk through the process of designing for hierarchy and learn its main challenges.

Everybody has chosen categories while filtering the content out. This action might have been overwhelming or boring for some of us while facing the ‘family tree’ of categories, their child categories, grandchild categories, etc. This endless hierarchy can make us feel lost at some point.

Case study - category hierarchy, categories

This problem is easily solvable if we have two levels of categories. To my mind, Reddit has found the best way to provide categories and subcategories in a visually appealing way.

After testing several potential users of our application, it turned out that the tree structure didn’t sound amusing for them either. Looking at the competitors of our eCommerce platform, it turned out that an optimal solution had yet to be found.

For example, on eBay, after choosing a category, you get redirected to the list of its subcategories, choosing which guides you to another list showing all the parent categories that are not highlighted enough to be easily differentiated.

I had to find a better solution for the eCommerce app with multi-levels (about 5) of categories.

The main challenges were the following:

  • Users should be able to see the path of his/her current selection.
  • Users should be able to return to the parent or any descendant category easily
  • Child categories should be different from the parent one
  • Users should not have to scroll a lot
  • Users should be able to search with keywords
  • The overall interface should be smooth and intuitive

Instead of a mere list of categories, I decided to present them in the form of chips — chips are easy to use and look cool and modern too. You will ask, how it is possible to show hierarchy via chips? After thinking it out, the following turned out to be the solution:

I provided categories as a default in the form of chips. Each chip that has subcategories — has an arrow, showing that users will be redirected to the second level when they tap on it. There are several subcategories shown right on the chips too so that users have a full expectation of what kind of interface they’ll have to deal with when they follow the flow.

In addition to the section with a bunch of chips, I placed the navigation bar at the top of the screen, right below the Categories’ search input. As a default, there is a single tab called categories, but as soon as the user chooses a category, the second tab with the name of the chosen category appears right next to the ‘Categories’. If the user goes deeper into the subcategory, the third tab appears with the corresponding name. In the end, the user has it all in hand — All the tabs to navigate or go back to any level, and easily scannable chips for the subcategories.

Category hierarchy - subcategories

Later on, after building the product, I tested the flow, and turned out that 87% of the users (132 participants) were satisfied while interacting with the interface.

Future improvement ideas:

  • When only two levels are left the Reddit model can be integrated into the process.
post authorTornike Kurdadze

Tornike Kurdadze
Mobile Engineer and UX Enthusiast with several years of experience in developing applications.

Tweet
Share
Post
Share
Email
Print
Ideas In Brief
  • Since choosing categories while filtering the content out can be complex and monotonous, it’s crucial to provide categories and subcategories in a visually appealing way.
  • Tornike Kurdadze, Flutter Engineer at Netguru, found a solution for the eCommerce app with multi-levels (about 5 of categories)
  • During testing and research, the author found that when creating hierarchical categories, there are several things to keep in mind:
    • Users should be able to see the path of his/her current selection
    • Users should be able to return to the parent or any descendant category easily
    • Child categories should be different from the parent one
    • Users should not have to scroll a lot
    • Users should be able to search with keywords
    • The overall interface should be smooth and intuitive

Related Articles

Design isn’t just about looks; it’s about human nature. Discover how simple psychological principles can make your product stand out.

Article by Canvs.in
Designing with Psychology to Make Products Stick
  • The article shows how psychology, not just features, makes products memorable.
  • It highlights principles like delight, internal triggers, and false consensus as keys to stickiness.
  • It argues that strong design balances trade-offs and roots choices in real user behavior.
Share:Designing with Psychology to Make Products Stick
7 min read

What makes players keep coming back? This piece explores the psychology of hot streaks — how momentum, perception, and smart design can turn short wins into lasting engagement.

Article by Montgomery Singman
The Psychology of Hot Streak Game Design: How to Keep Players Coming Back Every Day Without Shame
  • The article shows how hot streaks tap into players’ psychology, turning momentum into motivation.
  • It highlights the hot-hand fallacy, where players overestimate their chances of continued success.
  • The piece argues that ethical streak design should enhance engagement without exploiting addictive behavior.
Share:The Psychology of Hot Streak Game Design: How to Keep Players Coming Back Every Day Without Shame
26 min read

Trusting AI isn’t the goal — relying on it is. This article explores why human trust and AI reliance are worlds apart, and what UX designers should focus on to make AI feel dependable, not human.

Article by Verena Seibert-Giller
The Psychology of Trust in AI: Why “Relying on AI” Matters More than “Trusting It”
  • The article argues that “reliance,” not “trust,” is the right way to think about users’ relationship with AI.
  • It explains that human trust and AI reliance are driven by different psychological mechanisms.
  • The piece highlights that predictability, transparency, and control make users more willing to rely on AI.
  • It concludes that users don’t need to trust AI as a partner — only rely on it as a dependable tool.
Share:The Psychology of Trust in AI: Why “Relying on AI” Matters More than “Trusting It”
4 min read

Join the UX Magazine community!

Stay informed with exclusive content on the intersection of UX, AI agents, and agentic automation—essential reading for future-focused professionals.

Hello!

You're officially a member of the UX Magazine Community.
We're excited to have you with us!

Thank you!

To begin viewing member content, please verify your email.

Tell us about you. Enroll in the course.

    This website uses cookies to ensure you get the best experience on our website. Check our privacy policy and