New answers tagged

2

As far as what you have depicted, I would suggest collapsing the final node options, the same way it seems you have collapsed the options for the Tree and the Branch. Once a user makes a selection, there is no need to show the other options. This would clean things up a bit with your current design. (Assuming they do not need to rapidly switch back and forth ...


1

You could split them into Categories with the use of Chips just like Google Play Store does. Take a look at the screenshot below. How this helps is, that it removes any element of horizontal swiping. Since your question consists of Tabs, it is possible the user is confused to swipe between tabs which are swipe-able and bottom navigation which is not. ...


0

Typically with a hierarchy tree (even just one level deep) there are two scenarios you can model. Either the top level is a "parent" to the "children" or the top level is just a convenience "grouper" for the items under it. In either scenario there is an inherent expectation if you provide a top level checkbox that it will select all children underneath it....


0

Three-way checkbox might be what you're looking for. Multiple installation programs work this way, when you are selecting custom software components that you need. Node checkbox checked means - whole subtree is checked. On the other hand, checkbox unchecked = whole subtree unchecked. If only a part of subtree is checked, then the check box is in some third ...


0

Use the titles: Country, Region and Province (or whatever is appropriate) so users can click on these titles to see the pertinent list of Countries, Regions or Provinces. It will take space, but it's the only sensible way to offer the ability to navigate through your tree AND select within the tree, instantly.



Top 50 recent answers are included