Web Developer whines about a UI element
Dear Fixed menu bars,
I think you may secretly have a problem with me and I wanted to be the bigger man and address it directly. I don’t think you believe I deserve space, screen reading space. You see, I purchased this device to read articles, and boy do I love reading, sometimes I watch video on it too, it practically delivers 1/3 of the content I consume. You see, this device is actually quite small to be consuming content from, albeit all bleeding edge and shit, the experience it delivers is in some ways a step down from the mediums it is assumed to supersede. Simply put, it’s got a tiny screen, and it sometimes unnecesarilly glows.
You have decided to further this inconvenience by staying in place and taking up precious space, causing me to view snapshots of the world through an even tinier window. And please do not start with “but I’m here in the event you need to move along, and to remind you where you are”.
I am a full grown man, if I am invested enough to navigate to a website I would know where I am reading an article from, and I don’t need to be reminded of the title 2 or 3 paragraphs down, at this point the title may not even matter anymore and surely I know what the article is still about - well cause I’m reading it aren’t I. Perhaps if one had forgotten what an article is about mid-skim then it must be terrible and maybe one shouldn’t be reading it, or the reader just has a short attention span and deserves the minor inconvenience of scrolling up and back to where they were.
You may think, well “what if you need to navigate away?” I could always scroll up, and I do agree that’s probably a lousy way to do it but it feels the most natural, well then at least try to predict when I want to navigate away, like when I start scrolling up, or perhaps when I reach the end of an article, but I suppose the “Related Reading” section has beaten you to it didn’t she.
How about when I lose interest? You’re never told of when that happens, I guess not yet, nor soon. But shouldn’t hinder your foresight. When I open an article and start scrolling downwards, that should at least mean that I am interested in reading and not navigating away, in which case you should take a temporary absence — i.e. GTFO. Take for example writing apps, when I start typing all the chrome goes away, because it can safely assume I want to write and not “open a file” or “add a heading”. In fact even the browser does that doesn’t it? Hide the address bar when the user starts scrolling down, when I am likely reading, and show up when it gets the closest indication that the user has stopped reading i.e. scrolling up ever so slightly.
No, just stop