We're displaying a paginated collection of tiles (fixed width and height) within a variable width container. We have an upper limit of showing only 15 tiles per page due to the server resources required to get data for each tile.
On certain screen widths, there might be space at the end of the arrangement of tiles, which gives the impression the user has reached the end of the collection.
One option we considered would be to determine the # of items per page based on browser size, (ie responsive pagination), but I forsee two problems:
If you're on a non-first page and change the browser width, items toward the beginning or end of that page might disappear to another page.
There might still be space at the end of a page's collection if the calculated # of items per page isn't divisible by the number of rows.
Any ideas for achieving a better experience in this situation?