Tag Info

New answers tagged

0

Rather than doing a vertical expansion of items, perhaps try a more layer-based approach could help simplify. Rather than showing a long list of items, you could showcase a "stack" of sorts which allow the user to track where they were while seeing the options relating to their selection. View an example: ...


0

Does it matter to the person searching, if a node is of type A or B? I mean – do you have to make the tree structure visible within the search? If not, I would recommend using the ux pattern "faceted search" or "faceted navigation". In my opinion this can be a helpful ux pattern especially for 'power users' that know what they're looking for – but also for ...


2

What are the user needs? It is next to impossible to answer the question without more information. Primarily, why would users need such feature to begin with? What I have in mind is that if there are 1000 versions, involving 500 objects (490 of which may have been deleted) you'll be showing so much information that the visualisation will be impossible to ...


0

Git and other code versioning systems might be a solid start. Maybe some highlighting of the main/current branch and displaying more or less information about each version. code version system screenshot Large navigational systems might be helpful. Try underground plans for big cities and Japan Rail Pass map, they have a nasty amount of Shinkansen ...


0

It sounds like you need to rework your menu system/grouping. For a mobile application this seems like too many menu options. Assuming you keep the same grouping you could consider collapsing all groups except the one you are in. That includes any sibling level menus. Example assume Three 5 - 3 is selected. Your menu would look like this: Top One Top Two ...



Top 50 recent answers are included