> The advantage of moving sideways is that that's how every reading experience a user has ever experienced works, outside their computer.
Most of your customers are comfortable with the default scrolling experience. Those that are not are older; they are not your future. The fact that you have to include navigation instructions for your page shows that you're breaking expectations.
> For instance, what you are calling lag is the animation. Most people find computer navigation hostile because things move around and they don't know where they are going.
I was actually referring to the lag I experienced when testing the site on an iPad. The scrolling is jittery, it is pretty smooth on desktop Chrome though.
> In the case of scrolling, I find scrolling long documents a hostile user interface. It requires a great deal of user interaction and minute control over position. Pagination simply requires "next", "next", "next". I don't think every web site should work this way. But for long form content, it works a treat.
We've had a solution for long documents in HTML forever: the fragment identifier. I've recently seen a few clever sites use a fixed position div to provide a table of contents that updates as you scroll down the page. I wish I could find one; the affect is gorgeous, and still conforms to the normal web UX (and degrades gracefully).
Most of your customers are comfortable with the default scrolling experience. Those that are not are older; they are not your future. The fact that you have to include navigation instructions for your page shows that you're breaking expectations.
> For instance, what you are calling lag is the animation. Most people find computer navigation hostile because things move around and they don't know where they are going.
I was actually referring to the lag I experienced when testing the site on an iPad. The scrolling is jittery, it is pretty smooth on desktop Chrome though.
> In the case of scrolling, I find scrolling long documents a hostile user interface. It requires a great deal of user interaction and minute control over position. Pagination simply requires "next", "next", "next". I don't think every web site should work this way. But for long form content, it works a treat.
We've had a solution for long documents in HTML forever: the fragment identifier. I've recently seen a few clever sites use a fixed position div to provide a table of contents that updates as you scroll down the page. I wish I could find one; the affect is gorgeous, and still conforms to the normal web UX (and degrades gracefully).