Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

Is it a good idea to use tree-view UI structure in iPhone or other Mobile devices? (e.g. for file browsing etc.)

share|improve this question
    
Problems with tree-view UI in mobile devices: make the items too big and you have to scroll both vertically and horizontally; make the items too small and you can't select one without accidentally selecting another. Which is the worse of the two evils? –  Michael Lai Sep 19 '13 at 3:00
add comment

4 Answers 4

I would suggest a breadcrumb on the top and listview/icon view to keep it consistent with other tree like structures.

share|improve this answer
add comment

I don't think so, tree-view is hard enough to use on a full scale computer.

Microsoft had a study on it's own tree view and recommended to the developers not to use it if the users for that specific application are not computer savvy, experimented.

share|improve this answer
    
Do you have the link to this study? It is always interesting to see things published by Microsoft and see what their reasoning and research methods involve. –  Michael Lai Sep 19 '13 at 2:56
    
Nope, sorry. I read about it in Steve Krug's "Don't make me think". –  Adrian Sep 19 '13 at 8:51
add comment

Tree navigations is a simple and effective solution to discover hierarchical structures. I would test two different solutions.

  1. Accordion: http://ui-patterns.com/patterns/AccordionMenu
  2. Drilldown lists: http://mobile-patterns.com/lists

Accordions work if you have flat hierarchies (e.g. one sub level). They keep the user in context and you don't have to remember the other category names since you stay in the screen. The handler for open/collapse the category shouldn't be a small button, but the whole list item instead.

Lists are pretty ease to use and fits perfectly if you have to use multiple sublevels. The following items you should provide for smooth content discovery within subs:
- header with title of the current category
- shortcut which takes you to the top level in the hierarchy
- backup which takes you one level up

From an interaction pov, the main challenge is that browsing trees requires a lot of scrolling up and down to re-find items. Also from an information architecture point of view it might be not the most efficient system to organize information. User has to know in which category the object-to-find is hiding. At least there should be a category specific search. To increase flexibility and improve findability I would also combine it with a tagging system.

share|improve this answer
add comment

The NestView method for representing a text hierarchy (specifically xml) came up as an answer on a programmers.stackexchange question. This is quite 'out there', but it does save a fair amount of horizontal space, compared to either a tree-view or indented text. It also has the benefit of having a larger 'touch area' than a tree-view, it could possibly also suit more general usage than just hierarchical text structures:

enter image description here

share|improve this answer
add comment

Your Answer

 
discard

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