421–430 of 571 posts
Earlier quoted context omitted.
Can you turn this off? I am asking because using an iPhone unlocked while cycling is activating this great feature regularly.
I'm gonna be the jerk who says you really shouldn't be using your phone while cycling.
Earlier quoted context omitted.
Can you turn this off? I am asking because using an iPhone unlocked while cycling is activating this great feature regularly.
Go to Settings, scroll to the very top (beyond what shows as the top when you first open it). There's a search field (this is in a lot of other "list" styled interfaces like contacts as well). Type "undo" into the field. It'll bring up the location in settings to disable "shake to undo". It's under the Accessibility settings if you want to just browse around for it.
I need to use a MacBook Pro for work. Discovering that there is an option to make scrollbars always visible when there is scrolling to be done was, by a significant margin, the best QOL improvement I have discovered. 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 scrollin…
edit: the issue is still there :(
All those hidden scrollbars result in undiscoverable UI elements. They would only need to be a few pixels in width and it wouls be easy to tell that things are scrollable.
I went a long time--months?--thinking Apple had simply removed support for "repeat song" because of this exact same issue. When someone told me to "scroll down" it was like someone said "just open that wall, the peanut butter is inside" and I'm staring at a blank wall wondering who is insane.
On my iPhone SE, it is also well-spaced and perfectly cropped, omitting the 'copy' row and perfectly finishing below the second line of icons. (I actually have a PhD in human-computer interaction and I'm a professor for UX design. It took me a two days to figure out where all those functions, which somehow appeared to be accessible 'only through apps' (or people ;)), went. Oh well...)
Weird — on my SE the "copy" row is only half-visible at the bottom so it's clear that I can scroll.
I've also wondered where the functionality went.
Without this article I would never know that it's actually there but hidden.
Somehow I feel really bad about that.
-----
1) I don't remember if I've tried to adjust the font size. My pet peeve regarding that is the font in the Notes app which has a and o similar enough to allow false reading of anything that is not plain common words.
Earlier quoted context omitted.
Hmm, idk, perhaps a midway between removal and hiding would be to collapse it to ~1px so you gain real estate but still see the position in the document?
I use that from time to time. Some applications and some desktop environments on Linux do that. It's horrible, might as well not have a visible scroll bar at all. I'm fine if they're a little more narrow than the traditional Windows 95 ones, and the color can certainly be improved (maybe translucent Windows task bar / color-adapting Android notification bar), but expanding or hidden scroll bars are both super annoyin…
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.
"But I see them impact my aging parents all the time." I've realized lately that I'm actually entering this zone. For the last 20 years I've been talking about how stuff like this is a nightmare for the "aging" community. 20 years is a long time, and now I'm falling into it. The big one for me in this new version of iOS was that: 1) I couldn't figure out how to move my cursor around. It used to be perfect. I held my…
To summarize this thread (HN is still the best place to get IOS tips and tricks): Three ways to move the cursor, from most reliable to least: 1. Hold down space bar and you'll enter a mode where moving your finger moves the cursor. 2. Drag it from its current location to a new location. This gets finicky, especially if you move your finger out of the text area; the cursor will move to the end of the text, but the hig…
Earlier quoted context omitted.
It was in the WWDC keynote speech. The rest of the world else can "discover" it the next time a bug crawls on their screen.
Herein lies the problem: it doesn't matter how much 'better' or 'smoother' or 'consistent' the change is - or is not, in this case. It's a gross oversight to never inform end users of the change in any way . How many iPhone users attentively watch WWDC or read each update's (often incomplete) release notes? 1%? 3%? 5% tops? Why roll out a feature when 95% of your users will need to discover it through trial and error…
The false simplicity and "freshness" factor designers and developers are doing to change or add interfaces that cause confusion just for the sake of trying to get attention or change how something looks is a minor change for a major disfunction.
If the change doesn't improve something's usability, DON'T DO IT. I just noticed today iOS changed how some buttons look and menus operate, completely unnecessarily, throwing off recognizability and flow. Totally disruptive to the wrong people for the wrong reasons. Just stop, make interfaces that are easy to understand, figure out, operate, and remember. It's much easier to leave something as is than to change it unnecessarily.