4 ms·
I 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
by thought_alarm 11y ago
I 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.