In retrospect, there was really only *one* reliable, UX-enhancing use for force touch, and that was to use a relatively strong press as an accelerator for long-press. All the other experiences (peek and pop) added confusion and UX fragility. Besides, there could not be any UX that could *only* be accessed via force touch, because other devices ran the same iOS version that didn’t have the sensor. Additionally, force touch-exclusive experiences would introduce accessibility challenges.
Anyway, it was (not) fun while it lasted. I know hardware planning is hard, and planning cutting-edge products many years in advance is risky. But force-adding (pun intended) a UX affordance *because you have hardware* is the wrong way to design a product.
In fairness, I know of a few cases where production hardware *was* disabled or used in reduced capacity because the UX did not meet the bar to ship.
#apple #iOS #iPhone
Dave Rahardja /
npub13j…75d7q
2023-12-26 21:11:30
in reply to nevent1q…5yqn
Author Public Key
npub13jszgr40d0pnyum0t845scy8uggn676enygvaf4ajzm2y9rqzd8sy75d7qPublished at
2023-12-26 21:11:30Event JSON
{
"id": "9822dd03d07dc7041f4d449ff23d963a2d4a76da9be91d3c9c88da4264c0f198",
"pubkey": "8ca0240eaf6bc332736f59eb486087e2113d7b599910cea6bd90b6a21460134f",
"created_at": 1703625090,
"kind": 1,
"tags": [
[
"e",
"1eb30d528c962720d6844b021a0b32874896fbb92173218adb7514a66511ac87",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"apple"
],
[
"t",
"ios"
],
[
"t",
"iphone"
],
[
"proxy",
"https://sfba.social/users/drahardja/statuses/111648773938867981",
"activitypub"
]
],
"content": "In retrospect, there was really only *one* reliable, UX-enhancing use for force touch, and that was to use a relatively strong press as an accelerator for long-press. All the other experiences (peek and pop) added confusion and UX fragility. Besides, there could not be any UX that could *only* be accessed via force touch, because other devices ran the same iOS version that didn’t have the sensor. Additionally, force touch-exclusive experiences would introduce accessibility challenges.\n\nAnyway, it was (not) fun while it lasted. I know hardware planning is hard, and planning cutting-edge products many years in advance is risky. But force-adding (pun intended) a UX affordance *because you have hardware* is the wrong way to design a product.\n\nIn fairness, I know of a few cases where production hardware *was* disabled or used in reduced capacity because the UX did not meet the bar to ship.\n\n#apple #iOS #iPhone",
"sig": "17ee062c643aa5999e5b947825a01bfce483a01e8e58a0dffa33a3f82fee49bea2f82049b206ef1b731a8266caeace3ceb2192b7dcc316f5d391ae36e385fbd4"
}