Question

It seems that the trend in web design is to provide paged output, where long tables are displayed a page at a time. My customers don’t like that, and have requested that the web sites I design for them show all entries in long tables. The arguments for paging seem to be mostly based on the performance hit of displaying long tables, and this is less of a concern in a high-bandwidth corporate intranet. Arguments against paging include the ability to print the entire table, do string searches against the entire table, select arbitrary ranges from the entire table for copying, etc. I’ve pointed out that these features can easily be added to paged web designs (e.g. a print button that prints the entire table, or a button that creates a CSV file of the the table), but the paged output still seems inconvenient to them. Our typical table is about 100 to 600 items. Obviously tables that would be significantly larger would probably have to be paged.

Questions:

1. What is your experience with personal or customer preferences for paged vs. full output in long tables?
2. Web design tools seem to be pushing the paging paradigm. Are they out of touch, or are my customers unusual?
3. If you’re thinking ‘It depends on the length of the table’, what threshold would you use?

Answer 1

1. I love long one-page listings. One of the few reasons I can see for paged listing is the ones you point out about performance.

2. I think your customers are very usual and in-touch.

3. The threshold would be about page loading times. When the server can’t produce the full lists fast enough or when the lists gets so long that the browser slows down. (The latter can happen for quite short lists if you have non-a-tag hover stuff in your CSS and the browser is IE.)

Give the users a powerful search function and they’ll narrow down their page lists themselves.