Yes, it seems like the younger generation is conditioned to a different form of UI "discoverability" than those of us who learned computing in the desktop era. I look for visual indicators, even on touch user interfaces, so I am always missing functionality that is hidden behind a non-visual interaction. "Pull down to refresh" is something I would have probably never found in many applications if it had not been pointed out to me. iOS is especially notorious for hiding features behind odd/innovative UI behaviors such as press-extra-hard or shake.
I almost feel as if "just show me visual indicators of all functionality because I am old-fashioned" needs to be a new accessibility concept or setting.
Sure, when I see younger people trying some new GUI they basically touch and swipe everything to discover hidden options and functionalities, because someone decided that a flat rectangle looked "cooler" than a button, or that a greyed out textbox looked more "modern" than a standard white one... but isn't this just bad design? what happened with make things as simple as possible, but not simpler and don't make me think?
It's under the Accessibility settings if you want to just browse around for it.
a) the shaking feature turns on even if i don't type anything just by the virtue of the phone being active (shaking can mean 'undo', not just 'undo typing')
b) i have it mounted on a quadlock on my handle bar, no holding whatsoever.
c) i take the risk of asking for trouble while cycling on a cycling path with no other cyclists near me (within, say, 300m). I am not cycling between 2 double decker buses while texting...
take the risk of asking for trouble while cycling on a cycling path with no other cyclists near me (within, say, 300m).
You don't know. If you start looking at your screen and you are moving, you are a danger to others. I don't care what happens to you, but I care that you don't hurt others. And you may.
I.e. if there is no trust i can glance at a screen when i am on a cycling path with nobody around without injuring someone else, how can I be trusted while sharing the road with cars/buses/trams?
It definitely does feel like something the browser should handle though. Having to work on stuff like that instead of actual functionality is painful, especially for startups that are trying to iterate fast.
It's the definition of false simplicity.
Everyone followed suit because Apple Keynote events just made everything look so magical, and Mac/iPhone snobs were taken seriously by the dumbed-down press, and now Windows laptops and keyboards are like their previously-less-functional MacBook counterparts.
On mobile I'm fine with hidden ones. Since attempting to scroll down never has an unintended action (I'm sure someone on the Internet can name an exception, but I can't name a single one so it's not the common case) I always just try to scroll and notice when it doesn't go further.
Maybe for desktop, it might be solved by having a free spinning scroll wheel. Then you can flick like on mobile and nearly never need to actually drag the scroll bar. In the rare case that you do, you can still grab the one that appears on demand (like in many mobile apps), and by appearing on demand you have a visual indicator of how much more there is. (The home/end buttons also go a long way, but one doesn't always want to scroll to the end or use the keyboard.) But until we universally have such mice...
The most frequent one I've seen on Android is swiping down while (almost) at the top, and the entire view refreshes. This is mostly in the browser, which simply reloads the page after a few seconds (resetting any text fields you may have modified) and in this case the gesture can be cancelled by reversing it. Unfortunately, if the browser or app has been open for a long time (say, I've left a news app open for three days), the view can be quite different once it finishes reloading, and can be impossible to get back to where I was previously.
Lazy-loading content can also cause issues when offline if the placeholders don't update (Materialistic, the app I'm using now, has both these issues).
Occasionally I'll find an app that likes to do annoying bouncy things with the view when overscrolling the bottom of a list, but that's fortunately rare.
You can make a scrollbar that "ghosts" over/under the content.
Windows 8 was a culture shock, but at least was clear in what it wanted to be. Personally I found it (and to a lesser extent the "mostly like a phone" UI of Win 10 and current MacOS) to be a mistake - I want a distinct and appropriate metaphor for a desktop rather than using it like a 27" tablet. People have dozens of apps and windows open, not one or two at a time.
Win 10, for me, is a mess. The whole flat thing went much, much too far, there's dozens of remnants of the Win 7 way of doing it in dialogues, settings, workflow etc. Win 7 is probably the nicest, and most coherent look Windows managed, but for workflow Win 2000 often had the edge! e.g. every version of Windows since 2000 has reduced the power of search, but made it increasingly obvious that it's there.
It was in the betas which I enjoyed using. But when it was removed it made the entire OS feel unusable to me. Whoever decided Windows Server 2012 should follow suit deserves just as much scorn.
edit: the issue is still there :(
edit: I have a magic trackpad 2 also. It took when I turned that off and reloaded the page. Well that's annoying that I lose the scollbars with the trackpad.
I've been using iOS since 4.
Settings > Ease of Access > Automatically hide scroll bars in Windows > Off
I always thought 'below the fold' was so overused or at least only for people who never use a computer, but I guess that's definitely wrong.
I disagree, because you're not calculating anything. You just see the existence of a scrollbar and know immediately that the content exceeds the viewport and you can scroll. That's it. It's at least an order of magnitude faster than the alternative of "checking" because it happens instinctively without the slightest motor movement.
"Checking to see if something scrolls" means some form of finger or hand movement.
I know what you're saying though, because I do see people do it all the time. There is an awkward, to me, pattern of "I just started reading, so let's shake the content up and down to get oriented." It's just as foreign to me as people who highlight text as they're reading. Not my thing, but whatever. (On the highlighting behavior, I always figured it's both a visual cue and at least partially a matter of highlighted text becoming light-on-blue, which is easier to read than most web pages' black-on-white.)
> I always thought 'below the fold' was so overused or at least only for people who never use a computer, but I guess that's definitely wrong.
That advice was commonly head in web design and it wasn't really about people not knowing whether they can scroll or not. But rather, that visitors might just decide not to scroll before they leave your content because the first page is so uninteresting to them. It's because scrolling requires interaction that you're motivated to make the "above the fold" content grab their attention.
A behavior of "let's see if this scrolls by actually scrolling" is, in my opinion, an anti-pattern of bad UX.
I had been reading since before I started school; it was something I picked up early and that my parents encouraged in me greatly. So by the time I was in school and we were doing these reading exercises (which were mostly utterly boring to me at the time, because my favorite thing to read at home were my various science encyclopedia sets), I had no need for such a placeholder. Reading was natural to me, and I knew where I was in a paragraph, etc.
Of course, this upset the teachers, until they finally figured out that yes, I could read, and not only that, I could read well above my grade level (that said, my comprehension wasn't as great, unless it was geared toward topics of science).
I always figured that people who highlight text as they read on a screen do so for similar reasons; not that it's a stupid thing or anything - sometimes with long lines, small fonts, bad color/contrast choices, etc in text on a screen, you do need some kind of a marker to help you along...
(This is a real-world issue: In a write-up, you may want to present detailed data, but don't want to have every user, interested in the details or not, to scroll over several pages of extensive data. So the logical choice is to present a small, illustrative sample and have more in the overflow. The same technique may be used – and has been historically extensively used by the Engelbart community – for outlined text content.)
This is the typical narrow minded view that these app designers (not you) have. There are other uses for the scroll bar. For instance, I used to be able to tell how long it would take to read an article by looking at the scroll bar. Now they are gone and to compensate every other article now as an indication of reading time. Which is of course a worse solution, because people's reading speeds differ and it also clutters screen estate, even is a more annoying way.
The well known xkcd[0] about breaking workflows does not only apply to features, but also to UI. Few designers seem to acknowledge that.
This happens to me so often it's ridiculous. Maybe because I'm just used to seeing a scrollbar if there is a Y-overflow, and people that grew up with this system know to -- I guess just like try scrolling every interface and see if it scrolls or something? I dunno.
For anyone else in my boat:
System Preferences -> General -> Show Scroll-bars -> Always