Reinforcing endlessly scrolled pages

Question

I create an infinitely scrolled page that recursively loads and adds the contents of the next page to the current page. I think the browsing experience can be great and exciting, but the current method is not without usability flaws.

Incomplete progressive improvement. It is always helpful to maintain the back button and provide deep binding when using Ajax. Current infinite scroll implementations do not support this. Cannot bookmark bookmarks.

Some ideas for improving UX infinite scroll. Need an opinion.

• Change the hash of the URL with each download, for example. /! # / 2 → /! # / 3
• Pressing the back button allows you to scroll up the page. Pressing the forward button should scroll down.
• Access to deep link should behave as it was before Ajax. The transition to page 3, as well as the start from page 3 should show only the content of page 3, and not pages 2 and 1, since the user does not ask for them.
• There should still be a way for him to go to pages 2 and 1, as if it were a regular pagination. Since page 3 loaded scrollTop at 0, the scroll event is not useful. To do this, we may need a clickable link.
• We need to check if the requested page number is larger than the current one, because we should not load the contents of page 2 at the end of the page.

What do you guys think?

Answer 1

Interest Ask. I would suggest changing the hash of the URLs in the form #!/from/123/to/456 and increasing the to identifiers when the page loads.

If you use a hash or API history API to change the URL, in the sense of UX, the URL always indicates the location of the current content . For example, a user will wait for a bookmark, hit a reboot, or copy the URL to another computer and press "Go", it will return the same page.

The only way for your endless scroll page to complete the URL logic is with the hash of the URL I suggested above. Otherwise, just leave it; Twitter does not update the URL hash on its homepage.