5 ms·

>the gesture is no longer “press” but “swipe” and the UI element is not a button but edge of the screen itself. Right, but while it's obvious to everyone that

>the gesture is no longer “press” but “swipe” and the UI element is not a button but edge of the screen itself. Right, but while it's obvious to everyone that a button is a control, it's not obvious that an edge is a control. On top of that, swiping up from the bottom edge triggers two completely different actions depending on exactly when/where you lift your finger off the screen. Why not move the physical home button to the back of the phone?

strogonoff 1y ago
I think a button that is located behind the screen fits the definition of “hidden interface control” more so than a swipeable screen edge. Forwhat it’s worth, back tap is a feature of iOS to which you can assign an action, though it only triggers on double or triple tap.
- fauigerzigerk 1y ago
  >I think a button that is located behind the screen fits the definition of “hidden interface control” more so than a swipeable screen edge. I couldn't disagree more. A big physical button on the surface of the device that is both visible and touchable is completely unmissable. More importantly, it's unmistakably a control. There is simply no other explanation for its existence than being a control. The edge of the screen on the other hand exists because the screen has to end somewhere. There is no hint whatsoever that it doubles as a control when touched in a certain way or that it doubles as multiple different controls when touched slightly differently. That said, I'm not a dogmatic "UI physicalist" (if that's a thing). I hate the physical mute switch for instance and I'm not a huge fan of the physical double click to authorise purchases. And I don't want scrollbars constantly in my face. I do believe that new ways of interacting with hardware can be introduced over time even if hidden. There's a legitimate trade-off beteween discoverability and productivity once you're familiar with the way a device works. The problem is that some people really struggle with gestures even when they know they exist. I watched people fail to answer calls on Android because it required them to swipe up an on-screen icon. The number of things you can do swiping or just touching somewhere near the bottom of the screen is staggering and constantly changing.
  - strogonoff 1y ago
    > There is no hint Like there is no hint for double click, right-click context menu, pinch to zoom, force/long tap, swipe anywhere in any direction, etc. I do not want to repeat my comment. To each their own.
fingerlocks 1y ago
Settings -> Accessibility -> Touch -> Back Tap -> Tap Back of iPhone for Home You're welcome
- fauigerzigerk 1y ago
  The point of the home button was that it's an obvious, unmissable control. A hidden gesture that's off by default is pretty much the exact opposite of that.
  - fingerlocks 1y ago
    You can bring back the home button in virtual form as well, also in accessibility settings.
- strogonoff 1y ago
  How well does it work? I configured some action on back tap, but on my old phone it only allows binding it to double tap and triggers strictly accidentally (I cannot trigger it when I actually want to). Are you saying new iPhones have better sensors that improve back tap?

strogonoff 1y ago

I think a button that is located behind the screen fits the definition of “hidden interface control” more so than a swipeable screen edge. Forwhat it’s worth, back tap is a feature of iOS to which you can assign an action, though it only triggers on double or triple tap.

fauigerzigerk 1y ago
>I think a button that is located behind the screen fits the definition of “hidden interface control” more so than a swipeable screen edge. I couldn't disagree more. A big physical button on the surface of the device that is both visible and touchable is completely unmissable. More importantly, it's unmistakably a control. There is simply no other explanation for its existence than being a control. The edge of the screen on the other hand exists because the screen has to end somewhere. There is no hint whatsoever that it doubles as a control when touched in a certain way or that it doubles as multiple different controls when touched slightly differently. That said, I'm not a dogmatic "UI physicalist" (if that's a thing). I hate the physical mute switch for instance and I'm not a huge fan of the physical double click to authorise purchases. And I don't want scrollbars constantly in my face. I do believe that new ways of interacting with hardware can be introduced over time even if hidden. There's a legitimate trade-off beteween discoverability and productivity once you're familiar with the way a device works. The problem is that some people really struggle with gestures even when they know they exist. I watched people fail to answer calls on Android because it required them to swipe up an on-screen icon. The number of things you can do swiping or just touching somewhere near the bottom of the screen is staggering and constantly changing.
- strogonoff 1y ago
  > There is no hint Like there is no hint for double click, right-click context menu, pinch to zoom, force/long tap, swipe anywhere in any direction, etc. I do not want to repeat my comment. To each their own.

fingerlocks 1y ago

Settings -> Accessibility -> Touch -> Back Tap -> Tap Back of iPhone for Home You're welcome

fauigerzigerk 1y ago
The point of the home button was that it's an obvious, unmissable control. A hidden gesture that's off by default is pretty much the exact opposite of that.
- fingerlocks 1y ago
  You can bring back the home button in virtual form as well, also in accessibility settings.
strogonoff 1y ago
How well does it work? I configured some action on back tap, but on my old phone it only allows binding it to double tap and triggers strictly accidentally (I cannot trigger it when I actually want to). Are you saying new iPhones have better sensors that improve back tap?