3 ms·
It works reasonably well on the Apple Watch, where screen real estate for touching "objects" is minimal. Force-touching on the notifications view, for example,
by otterley 11y ago
It works reasonably well on the Apple Watch, where screen real estate for touching "objects" is minimal. Force-touching on the notifications view, for example, is the only way to clear all notifications.
That said, I've never used it on the iPhone -- if anything, Force Touch only gave us some shortcuts to actions that long-time users have already acquired "muscle memory" to perform differently (and without significantly more steps).
- dreamfactory2 11y agoI hate it on the watch. I'm not that uncoordinated and always misfiring it and confused by what happens. For anyone actually disabled I'd imagine it must be a sick joke accessibility anti-pattern.
- dkonofalski 11y agoI don't understand this. I have such an easy time with Force Touch but yet you're definitely not the first person I've heard say this. I can hit the Force Touch menus everywhere with 99% accuracy. Most people that I've seen do this seem to press really hard to try and activate it but it's much more subtle than that. It's even hard to describe but the activation isn't because of a harder touch, it's because of a "deeper" touch. At least that's how I was introduced to it and now I absolutely love it.
- thought_alarm 11y agoI see two problems: 1. Speed. The delay between a force touch and the haptic feedback is often measured in seconds rather than milliseconds, particularly when the watch has been inactive for a period of time. That kind of delay is frankly outrageous. The haptic feedback needs to be instantaneous to be effective, even if it takes the actual software longer to wake up and respond. 2. Tap vs. Scroll. Unlike the iPhone, the Watch does an especially poor job of distinguishing between tap and scroll gestures. If your finger isn't perfectly still the software will treat it as a scroll gesture, and no amount of force will override it. Pairing those two behaviors can produce some frustrating user experiences. On the original iPhone, Apple did an amazing job of producing a very fluid and responsive UI on very humble and underpowered hardware. They've been less successful at doing the same with the Watch hardware.
- dkonofalski 11y agoThat's probably why I'm having so much success then. I scroll almost exclusively with the crown. I never have issues with taps being interpreted as scroll actions. My wife also got an Apple watch and kept having issues sending heartbeats and sketches until I gave her the same example ("deeper" not "harder" - giggity). Now, the only issues she ever has are when her nails get in the way.
- thought_alarm 11y agoForce Touch is perhaps the one thing I truly dislike about the Watch. Force Touch is just a menu button. Only it's a menu button that's extremely fussy and difficult to use. I actually struggle to save my workouts on the Watch because after a workout when I'm sweaty and breathing heavily, it's damn near impossible to bring up the menu and save the workout. The Watch would be a better device if it had a hardware menu button instead of Force Touch. Same goes for the iPhone. Force Touch is only useful for bringing up the app shortcut menu, and for positioning the cursor in a text field. Those are important but utterly mundane features. You don't need a sophisticated force-sensitive screen to bring up a menu for move a cursor, and those features would be easier to use if they were not implemented using Force Touch.