User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

It's known that infinite scrolling may be harmful for the usability and that sometimes it's better to set an end and provide a button to show more content.

My question is, in a web application context, what would be the impact of infinite horizontal scrolling on a timeline like this:

In this example, horizontal scrolling is done by dragging and dropping the timeline, so it is not continuous. Users have to click each time they want to scroll. Isn't that similar to click in a button to show more?

share|improve this question

Your example does not feature infinite scrolling in the same way it is discussed in the article you have linked to. Apart from the obvious difference (drag to navigate), the user can scroll up or down to zoom in or out the timeline: that gives the user a sense of where the current moment lies in the bigger story. A user can zoom out to see the entire timeline. In contrast, in the examples mentioned in the article, the user doesn't know their position in comparison with the entire content (I'm now at page 5 of …?).

In your prototype the issue at hand is to visually indicate StartTime and EndTime at the left and right edges of the timeline, so that the user will have a visual indication of the timescale they're currently browsing.

share|improve this answer

Your Answer


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.