I realize I may be alone here, but I can think of very few "scroll up bars" I've come across that I didn't find incredibly annoying — a lot more annoying, in fact, than traditional fixed headers. They just get me every time: I'm skimming through the content, see something I like, scroll back up no more than a few pixels and down the bar comes, overlapping the exact thing I wanted to read (because, if I'm scrolling up just a few pixels, it's quite likely I'm trying to read whatever's near the top of the screen). I know it sounds a bit overboard, but it's actually been a source of minor anxiety for me, as a user, in the past — I now always scroll up at least twice the amount I need, just in case.
For the record, I do realize most of the times this is just the result of poor implementation (i.e. the developer did not weigh in scroll velocity and threshold) but it's still a good example of how making assumptions about user behaviour can lead to good ideas, but not thinking them trough will often make for some pretty frustrating experiences for at least some of your users.
Good point. On the new Facebook app they've put the scroll-up bar on the bottom, which is less intrusive.
A few days ago I put together a really rudementary demo of a 'get out of my way' nav: http://codepen.io/BorisKourt/full/HlcqA Thought it was, at the very least, a fun version of the much reused fixed bar menu.
Sorry to be so negative, and I understand it's a matter of opinion, but I really don't like this pattern. I find myself scrolling back down a little just to get rid of the bar when I scroll back up to review some content.
On a side note, please don't break mobile native scrolling on mobile/responsive sites with some scrolling emulation library just so you can implement features like this (or something parallax-like).
Sorry to be so negative, and I understand it's a matter of opinion, but I really don't like this pattern. I find myself scrolling back down a little just to get rid of the bar when I scroll back up to review some content
I'm not what sure the intent of the blog is supposed to be. With the title 'usability post,' I'm pretty disappointed though. The explanation is is a good exploration of design rationale, but hardly is there any information given about the usability of each pattern themselves. Where's the data?
Edit: missed a word.
I've been way less nuanced about this.
Frik'n anti pattern. I hate it when they screw with my perception by making a top bar that changes position. Ridiculously annoying when reading.
YES. I'M LOOKING AT YOU, CHROME.
.edit: [rant some more] actually, this is just as annoying as those bleeps that pop up a "share" menu as soon as you select some text.
Scrolling, hovering, and selecting. Three things that are not supposed to do anything, and (some) people use while reading to indicate how far they've gotten. [/rant some more]
I actually really dislike this design, as I never scroll up before wanting to go back a page (edit: or change pages). I honestly can't understand the correlation between scrolling up and going to the previous page (edit: changing pages). When I reach the bottom of the page and am done with the content, I look for the back button (edit: navigation). My first experiences with this feature left me extremely frustrated, not knowing where my back button had gone.
I think this is neat, but is it more usable?
I would even argue that from a usability perspective (as in: how people actually behave on the web), having a non-fixed header without fancy tricks makes just as much sense. It's not that big of a deal to scroll to the top, people know where to find navigation.