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.

Context: I have tabular data in a table that populates dynamically so there could be any number of rows in the table. I do not wish to bombard the user with a long scrolling page so I'd like to set breakpoints in the table and use a display count dropdown so the user can select how many rows show in the table per page.

Here's an example of what I'm talking about:

enter image description here

Question:

How do you determine the breakpoints?

Do you increment by 10,25,50,100,500,1000? or 10,100,1000?

Is there a general rule of thumb or best practice?

Note: Auto-load on scroll will not work in this case as the quantity of data the user sets can be exported under a WYSIWYG model.

share|improve this question
    
There is no max for this as it's determined by the user's settings. They set the date and increment for the data. It could be anything from a few hundred rows to 100,000s. If the user selects Hourly breakdown over the course of 3 months, that's over 20k entries. –  Pdxd Mar 5 at 16:59
    
possible duplicate of Best practice for displaying no of records on datagrid –  Code Maverick Mar 5 at 17:31
    
Just took a look at the link and it doesn't quite answer what I'm looking for. My question is about what specific increments to use as best practice, not about how to display. –  Pdxd Mar 5 at 18:15
    
@CodeMaverick not a duplicate - that question seeks to choose between three different styles, one of which is this customisable pagination method ... but doesn't address the question of what size buckets to use. –  Erics Mar 6 at 5:47

1 Answer 1

up vote 3 down vote accepted

Here's a study by the NNGroup that talks about User's Pagination Preference:

Many sites let users choose how many items they’ll see on each page. This is often overkill, as when pop-up menus let users View 10, 20, 30, 40 items per screen.

...

It’s usually better to offer a single default number—such as 10 or 20—and supplement it with View All for people who want more...this design requires only a simple button and is thus much faster to operate.

...

if View All would generate an unwieldy page, give users the choice between two numbers, say 10 and 50, where the second number is substantially bigger than the default.

share|improve this answer

Your Answer

 
discard

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

Not the answer you're looking for? Browse other questions tagged or ask your own question.