Tag Info

New answers tagged

1

Break the problem into a number of functional areas Sending email (writing and responding and notification) Recieving email. Notifying email 3 managing email (reading, deleting, archiving etc) email archives. Here we are storing for later use. Searching/finding/sorting/grouping Your issue depends on 1. Quantity and age of email and the different number ...


2

I'm biased towards no pagination because it forces cognitive breaks in the user's workflow. But that is a bias and not an answer. I think the right choice here depends on a number of factors so on way to do this is to build a scorecard along the lines of: User considerations Does the user's workflow feel naturally paginated (eg a page metaphor is ...


1

Infinite scroll has the advantage of less controls (buttons) for the user to interact with, and thus less cognitive load on the user in general. Pagination has the advantage of additional navigation ("jump to") options if the user will be searching through the list. That is, the user can quickly jump to the oldest X% of emails through paginiation. In ...


1

Sounds like pagination/infinite scrolling are the default way of how to do it and do not confuse people and give them something familiar. Then add someting handy on the top of it, that speeds up the regular tasks/behavior of them. Here it will depend in which situation the email client is used. Eg. behavior can be different when dealing with personal and ...


0

The three major considerations that will have to be weighed up for your project are: Complexity of information - datagrids are suitable for information that has more or less a linear nature or hierarchy, or at least nothing to deep. So when you apply the rule in the style guide you probably shouldn't be applying only scrolling or pagination because it ...


2

Even for a thick application, it is not always about how much load client can bear. There are other aspects you must consider when you trying to introduce pagination. Nielsen Norman Group talks about that. Performance Loading all data at once will increase your initial load time, put burden on network. It would be unnecessary if user is not going to go ...


1

If the users know what they are looking for I would use a typeahead box. You can let both the technical name and the human readable name be searchable. Example of a typeahead input field: https://twitter.github.io/typeahead.js/



Top 50 recent answers are included