Tag Info

New answers tagged

0

I agree on most suggestions for a progress wizard (there is a related post here). I do not completly agree, that the amount of content is critical if it should be splitted in serveral pages. Think of pinterest for example. They have an endless page to scroll. For sure there are some withdrawals with the automatic appending of new content (perceived ...


0

If there's indeed enough content to fill one long page with it, then splitting it into several shorter pages might be beneficial. Users won't feel overwhelmed by the amount of content (or by the amount of data that is asked of them, in case this is a big form) and they'll have a better sense of progress. In that case just make sure to provide some kind of a ...


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 ...



Top 50 recent answers are included