Stop Pagination Now
slate.com
Stop Pagination Now
1–10 of 92 posts
Re: Stop Pagination Now
#2Much bigger sin: Boing Boing style "endlessly load more content with Javascript" nonsense.
If you're browsing on an (arguably flawed in its implementation) iOS device where page state gets unexpectedly dumped all the time (e.g, tab switching, browser crashes, "multitasking" switches out to an IM client), this style of "pagination" is utterly pants. I end up having to manually edit the URL to advance through content like Boing Boing and Tumblr just to be sure that when Safari or Chrome inevitably next dump my page state I won't have to start from the very top again.
Re: Stop Pagination Now
#3But of course, even this article itself is paginated.
Perhaps ironically, but still.
Re: Stop Pagination Now
#4But of course, even this article itself is paginated. Perhaps ironically, but still.
If you read even a little bit of the article, you'll see it's Slate's policy to do so. But even then, if you click the next page, he just completes the joke he made in the article.
Re: Stop Pagination Now
#5Article on single page.
http://www.slate.com/articles/technology/technology/2012/10/...
Re: Stop Pagination Now
#6Much bigger sin: Boing Boing style "endlessly load more content with Javascript" nonsense. If you're browsing on an (arguably flawed in its implementation) iOS device where page state gets unexpectedly dumped all the time (e.g, tab switching, browser crashes, "multitasking" switches out to an IM client), this style of "pagination" is utterly pants. I end up having to manually edit the URL to advance through content l…
Yeah, paginating articles and paginating archives are two totally different things. Paginating articles (as the article linked describes) is not a good user experience. But not paginating archives, otherwise known as endless scrolling, in my opinion, is not good.
Re: Stop Pagination Now
#7Much bigger sin: Boing Boing style "endlessly load more content with Javascript" nonsense. If you're browsing on an (arguably flawed in its implementation) iOS device where page state gets unexpectedly dumped all the time (e.g, tab switching, browser crashes, "multitasking" switches out to an IM client), this style of "pagination" is utterly pants. I end up having to manually edit the URL to advance through content l…
Yeah, I can't stand infinite scroll pages. It becomes impossible to pass a link to someone to a specific section of entries. It generally breaks the back button -- when I click a link and then go back to an infinite scroll page, it has dropped all the dynamic content and has to reload it, and then I have to scroll back to where I was (which may have involved several minutes of scrolling and loading content).
Perhaps it's irrational, but it also frustrates me that such pages have no bottom. I think people got used to a model of a page where it has a top and a bottom, and now it's a bit weird to interact with. One of my favorite examples is Facebook's implementation, which leaves several useful navigation links in the page footer. These links taunt you as you tried to scroll to reach them, only to have more news content appear in your view and push the footer off screen again. (I think they've since duplicated those footer links in other locations so you can reach them, but it doesn't change the fact that this broken UI model presents options and then sucks them away before you can click on them.)
Re: Stop Pagination Now
#8Much bigger sin: Boing Boing style "endlessly load more content with Javascript" nonsense. If you're browsing on an (arguably flawed in its implementation) iOS device where page state gets unexpectedly dumped all the time (e.g, tab switching, browser crashes, "multitasking" switches out to an IM client), this style of "pagination" is utterly pants. I end up having to manually edit the URL to advance through content l…
Yeah, paginating articles and paginating archives are two totally different things. Paginating articles (as the article linked describes) is not a good user experience. But not paginating archives, otherwise known as endless scrolling, in my opinion, is not good.
Endless scrolling can work if you use it in conjunction with replaceState to make sure that the URL reflects that the user is looking at. Outside of that, though, definitely annoying.
Re: Stop Pagination Now
#9But of course, even this article itself is paginated. Perhaps ironically, but still.
If you read even a little bit of the article, you'll see it's Slate's policy to do so. But even then, if you click the next page, he just completes the joke he made in the article.
Poor guy couldn't even get through the first sentence before he felt the urge to try to impress us all with his keen observation.
Re: Stop Pagination Now
#10>"Pagination persists because splitting a single-page article into two pages can, in theory, yield twice as many opportunities to display ads—though in practice it doesn’t because lots of readers never bother to click past the first page."
As much as I hate it and would love to think that pagination is just a publication pipedream, it's not.
Some online publications have spent (and will spend if they're interested in making $) significant time and $ A/B testing various levels of pagination such that their sites are optimized so that there are just fewer pages than their readership is unwilling to tolerate.
The end result is that their sites are optimized to make the most amount of money. If it didn't improve their revenues, they wouldn't be doing it.
Of course, there are copycats that don't do the testing, don't optimize for their niche of readers, and are probably losing both money and readers because of it.
We can argue about publications adopting different business models, but that's a different story. Advertisers pay a premium for engaged, targeted niche audiences that match their products/services. That's the reality of the online advertising market.