My favorite iPhone feature was removed, long live its subpar replacement
technicallychallenged.substack.com
technicallychallenged.substack.com
It was definitely one of my favorite features, and Force Touch isn't a drop-in replacement.
With 3D Touch anywhere on the keyboard, you could apply pressure to start moving the caret (text cursor) around, but what was even more useful was being able to apply a little bit more pressure to start selecting text with incredible precision.
With Force Touch, you can long press on the space bar till you get haptic feedback, then you can move the caret around freely. However, if you want to select text, you need to use a second finger on the keyboard after you start moving the caret around, but honestly it's an absolute mess to use; try it out, I can guarantee you won't be able to select what you were planning on.
However, as much as I miss it every time I fail to accurately select text on iOS, I don't mourn its loss. Force Touch is adequate. It's just not a replacement, and seems a shame it was probably removed to reduce costs and hardware complexity, all at the cost of regression.
The 3 times this year I’ve needed to use my flashlight are not worth the 20+ times it’s been accidentally running in my pocket because I held the wrong corner while pocketing my phone.
Plus it’s in control centre anyway If you need it fast.
I actually used to hit it accidentally more often when it was a 3D touch button rather than a delay-based button.
I just want a way to completely remove it for the majority of us who are not wandering around in pitch black.
I don’t think I’ve ever had the flashlight accidentally left on (not in a long time, anyway).
Force Touch is something supported by 2015+ MacBook trackpads (you can push harder to effectively middle-click something) and 3D Touch was the iPhone screen tech that did the same thing, which has been replaced with Haptic Touch (equivalent to Android's "long press").
It seems the selection can only grow and on both sides, which is the main problem.
If they showed the cursor with a different color than the selected text, and if they shrink and grow the selection as you move, I think it could be pretty nice: select the starting point of the selection, and select only what’s in between the original cursor and the moving one.
Alas it’s more like painting a selection at the moment, with an invisible brush.
With a traditional cursor, it places an anchor wherever you’ve moused down and then drags the selection around that anchor.
Whereas with Haptic Touch selection, there’s no anchor, so you find yourself selecting text you didn’t mean to. I’m sure that once you’ve gotten used to it, it’s a nice feature; but it’s not intuitive if you’re not accustomed to it (which seems to be the majority of folks).
iOS UI in a nutshell.
You can do most of the things that most users need to do just knowing how to tap icons and swipe up to go home. I don't think it's such a big issue that there are some power user features that you either discover by messing around or word of mouth.
I could have sworn it used to work like how you'd expect, where it's anchored from the place you started highlighting. I got my first iPhone, the 12 mini, when it came out. So end of 2020, and I thought that was how text selection worked when I first got it, then it seemed at some point, perhaps after an update it started working where it would only grow the selection and you couldn't unselect if you accidentally went too far. I thought they introduced a bug but it hasn't changed since then. I have no source for this, only my own memory, but maybe someone else can tell me I'm correct/incorrect about that?
The current implementation is way too hard to use. Especially if, for example, you're selecting something starting on the far right side of a line to the far left side of the same line. You have to thread the needle of the above and below lines like a game of Operation, because if you go too high or too low, you'll accidentally end up selecting that entire line.
Yes, it's slightly worse now but for a greater cause and the greater cause, IMHO, is the unified interaction model on mobile devices. If not all devices and apps are using it there's no reason to having it.
In the Android world there are tons of exotic stuff, novel ideas and even "standards" that go nowhere unless Apple implements it.
There is a magic in general availability. I think, if all Apple devices had it, it could have been possible to rely on its existence and build the UI with that assumption in mind. With just some devices having it, you need to have few versions of the UI to handle each case.
I think you misunderstood. This is not an argument for equality at all, the problem with patchy support is that few bother to implement features against because it costs time and money and as a result fades into usbcuirity.
Having uniform platform is a very effective for innovations success. It makes sense for Apple and the developers to have the hardware based 3D touch with a software based alternative so that it can work on all devices the same way.
The way you get there is by putting it into everything for several years.
Cutting it after three is the opposite of working for that greater cause.
Maybe the force the user can apply when iPad is on a table(no lever effect) and when is handheld(strong lever effect, user needs counterforce on the other end of the screen to achieve firm press) is far too different to reliably activate the gesture?
– Apple
Never been able to get the same size phone twice even if I wanted to.
That is not how I remember it. I remember text being selected left and right at random for no apparent reason when trying to move the cursor.
They probably removed it because nobody was using it and they couldn't figure out how to teach people, while spending extra $ to add it into phones.
Cynically, it feels like they think everyone should already "just know" how the various gestures work, which is obnoxious and user hostile.
I also dont often use Linux, but I could try some new distro with a completely different windows manager I have never seen before and I can figure it out and be happily computing in no time.
apple stuff always requiring searching on the internet to find out how how to do even most basic functions.
Also, not relevant, but I gotta mention as it grinds my gears so bad.. The only reason I have to use macOS is that it's required to build to iOS, which is just uniquely egregious. That sort of business should actually be illegal. Hopefully it will be in EU soon.
The shortcuts associated with menu items are shown in the menu item. I realize that there other discovery problems with keyboard shortcuts (on all platforms) but there is non-zero discoverability for "the most basic things" on Mac OS.
Gesture discoverability is much closer to zero, IMHO.
(yeah this is the computing equivalent of a locked file cabinet in a disused toilet stall in a dark basement with a sign on the door that says "Beware The Leopard")
OTOH it makes complete sense to have a look at the Trackpad pane to see how it works. It’s not like it’s hidden behind a defaults command line, and it even has movies. It’s much worse on phones.
What do you expect? Unskippable videos when you first set up a mac followed by a mandatory test that you have to pass before you can use the computer?
Everyone else does it worse, except maybe the VSCode command palette.
I’d like a Mark II version which also says “there is no such thing as Sunday 8th of August this year” so that I can fix my errors before they cause problems.
No matter how clever and subtle you think you're being, you're still just redirecting the user's attention from the task at hand toward the UI itself. No matter how ignorable, dismissable, or optional it is, it's an abysmal UI failure and it shouldn't even happen once. Make the feature right in the first place and you won't have to resort to nagging.
Isn't that the Tips App? I'm pretty sure it gets recommended every time you set up a new phone. Mine has a tip on using Haptic Touch with the keyboard to move the insertion point.
There is/was - it's called Tips, and most people ignore or uninstall it.
Some say it's why minesweeper et al were added to Windows, so people could learn how to use the mouse.
Apple Introduces Revolutionary New Laptop With No Keyboard https://www.youtube.com/watch?v=9BnLbv6QYcA
"just few hundred clicks away"
The end. (I didn't even know about it until I finally switched to an iPhone Xs after years and years of lowest tear iPhones).
Currently it’s “long press”. I think they did this so they could remove the physical layer required for 3D Touch that took up space.
The UX was better for the force sensor though, it was instant feedback based on user action and didn’t require a delay to detect.
There's probably a way to make a lot of HN points just running a summarization model and posting the result as comment
Force Touch was the same tech as 3D Touch, first introduced on the watch. It was rebranded for the iPhone when the pressure sensitivity stuff was added.
It's current replacement is Haptic Touch.
"Both 3D Touch and Haptic Touch fall under the umbrella of Force Touch functionality. This is Apple's general name for its technology that lets input devices distinguish between different levels of pressure when you touch them."
https://www.makeuseof.com/apple-force-touch-3d-touch-haptic-...
https://en.wikipedia.org/wiki/Force_Touch
So, 3D Touch was one implementation of Force Touch.
No kidding I just managed to make it bug out and crash safari
Better than I knew before, but not incredible. Would at least require letter by letter precision for that.
That behavior was very, very frustrating.
Now how as a "user of apple products for 8 years" was I supposed to guess this ? Thank you ! You made my day !
The input experience (or AI supported typing) is getting worse and worse for me on the iPhone. Especially, if your are using different languages in parallel. For me it is my mother tongue German and my most second language English and sometimes using Spanish. In an (for me) unpredictable way, there are words replaced to "correct" typos. But, independent of the used keyboard language, which is completely ignored for this auto-correct, it replaces it with German word, when I write English and sometimes with English words when I type German. Then this forced touch was helpful to select the letters/word to re-write it correctly to make the sentence meaningful. But now, this whole selection process is completely broken (for me). Since the removal of force touch, when I try to go to a specific spot, it selects parts of the sentence in a completely (for me) unpredictable way. Then I have no chance to un-select anymore, so I have to replace the whole. The experience is getting worse and worse.
I think peak iOS was in the past.
However, the points you make are absolutely right, and in addition it has recently developed the annoying trait of sometimes choosing to replace previous words that I have specifically typed and selected.
But I think it's great that the keyboard language does not define the autocorrect language.
The German keyboard has smaller-sized keys and it would drive me insane I think if I had to switch to the German keyboard in order to type German text.
For the special characters (é, à, etc), I long-press and choose whatever I need.
Since I hate typing on the phone, I quite like using the suggestions, especially for words with multiple special characters.
- The two word replacement pattern is immensely frustrating and leads to typos, e.g., where “AI” seems to think it knows better what I was trying to write and changes the previous correct word based on what it thinks I am trying to currently type/swipe. A good example just happened below; I tried typing “mid word” below, once I started swipe typing “word” iOS thought it would be a great idea to change “mid” to make it “miss words”. Thanks for the unhelp Apple.
- The random capitalizations for no apparent reason, sometimes even mid word, and no, not from accidentally hitting shift, even during swipe typing.
- The infuriating overbearing and downright evil efforts at speech and thought control. For example you can’t swipe type certain things Apple has clearly designated as wrongthink; assuming of course that the only possible reason someone would want to use the sequence of words Apple has designated as wrongthink is for purposes that violate their perspective of narrow utopian authoritarian society.
- That for some reason sooner rather specific acronyms seem to be prioritized over the most common words in the English language through inaccuracy. One example; try swipe typing “is” with some inaccuracy and you get “OSS” instead, ab rather obscure acronym to replace “is”, or OSS it?
- The concatenation of “a” (I think there are others I can’t recall) rather than automatically adding a space when there is a hyper (I think that’s what it’s going on), so e.g., “it’s a” turns into “it’sa” … “he’s a” “what’sa”
- I too have gotten the sense some of it may even have to do with or is exacerbated by using multiple keyboard languages. I love when the autocorrect “AI” substitutes words from a different language altogether, that’sa (that was organic, but left for sarcastic effect) really great feature! (Yes, that’s more sarcasm)
I've never had capitalization for no apparent reason (maybe I didn't pay enough attention), but I have a similar pet peeve, where the AI learns "a bit too much".
I write a lot of French, and a fairly common phrase I type is "c'est chiant" (that sucks). At first, it would try to autocorrect this to something else, probably because it's "not nice" to write that.
But after insisting on writing that for a while, it must have figured "ok, let him write that". Except that it learned the whole phrase, capitalized, because it's usually the first thing I type, so it automatically capitalizes the first letter (I always rely on automatic capitalization when writing informally).
But now when I want to write that in the middle of a sentence, it will auto-capitalize the C.
On other devices/keyboards (SwiftKey for example) I type a word and if it thinks I might mean something else, it shows up in a row of 3 suggestions above the keyboard. If it's correct, I tap the suggestion and it replaces whatever I'd actually typed.
Makes for easy fixes and only adds an extra "tap" if I see a mistake that needs to be corrected. Either way, beats backing up and retyping or jumping through hoops to remove "ducking" from the dictionary.
SwiftKey on Android (Microsoft) does the same thing to me on occasion. It is indeed very annoying.
I ended up reducing the force setting to the minimum, and still felt it wasn't practical.
I was so out of the loop that I had no idea the feature existed. When I eventually looked it up, all I could think was "how the hell was I supposed to figure that out?".... maybe they explained it during one of those apple conferences everyone watches?
I suppose if my first iPhone was one that had this functionality, maybe I would have figured it out.
But your confusion is an example of the main problem. It’s hard to discover and easily confused with long press (if you try to Force Touch and don’t apply enough pressure eventually you’re going to leave your finger there long enough to activate long press)
Happened to me.
Then I couldn't delete apps at all, but turning off 3d touch fixed it. Perhaps a coincidence, or some other bug. Terrible UX though.
Swipe from bottom to switch programs? Swipe from top left and top right to get different (IMPORTANT!) panels? Why are three lines a "Menu"? But sometimes it's dots, or a gear icon, and they're never in the same place. On iPhone, there's no real unified "Back" button - chase it down from application to application with different context and result every time. On Android, unified buttons (including reliable and predictable "back") exist but their location and icons are not intuitive either.
I also encountered opposite problem than described - when I tell people to hold-press, they exert force. It's a natural, intuitive thing for most of them - they're trying to press hard. But the mere notion you need to hold-press anything? Completely unintuitive. Like everything else on a modern phone :-/
The single, physical home button was fucking genius and iOS6 and earlier were the only operating systems I've ever seen that my very-old-and-with-significant-mental-decline grandmother might have been able to use regularly without a ton of help.
Then iOS7 came out, and later they got rid of the home button. So much for that.
> On Android, unified buttons (including reliable and predictable "back")
If the back button's reliable, that's a recent development. It spent at least a decade being the "YOLO" button that might do any damn thing. Absolutely terrible, and complete usability poison for non-nerd users. Or maybe this was sarcasm and I'm missing it.
Although, they've overloaded it's use - single press for home, double press for app switcher, fingerprint sensor, etc. (Or maybe that's what you were referring to with iOS 6/7?)
Agree with you in general, though: the single, physical home button that always did what you expected was great.
Android's back button usually takes you back to wherever you were before, although apps can break this (instagram, for example: if you open a message from a notification, you have to press back 3-4 times to get out of the damn app.)
That seems a valid and desired behaviour.
If I want to exit app, I press home button.
But if I want to go back one step... I press back button. It takes me back one step. It's like the Go-mode of undo :-). Previous page or form in a browser, back several layers of menu in app or game. I may be writing an email then press back to go back to main mail screen. Etc
Basically for me, Android back button does exactly what I want it to do, in OS, games, programs and Web, zero sarcasm. And home button to "take me to where I was before I entered the app".
The back and share pipeline of Android are like it's super powers as far as I'm concerned (and I say this as somebody forced to use iPhone for work last 4 years, so get to experience both daily)
When I press the home button, this often doesn't close down the foreground app entirely, so after a while of doing this I will end up with lots of apps running in the background, which I don't like because often they keep consuming power even when backgrounded and may also continue gathering data about me that way.
I am aware that apps can also install and run background services separately from the app, but in my experience, the apps that I use tend to also shut down these services, as long as I exit the app entirely, using the back button.
There are times I want to set the 250k+ per year developers, and the board room committees arguing if 30 or 40 ms is the appropriate touch time down with one of these users and see if they can succeed in teaching them the interface.
While I don’t believe a sufficiently complex UX could be totally intuitive (it can at most depend on existing knowledge of similar devices), it does extend the app as a physical rectangle idea very well, the animation strengthens the memory, and the movement becomes second-nature in no time.
(Also, credit where it’s due, I believe this feature was first introduced by Palm?)
I think just about everything else requires context, which is just a fancy way of saying that someone taught them how it worked at some point or they played with it long enough to guess their way to enough breadcrumbs that they built up that context themselves.
But then they added long press, so now one icon does two or more things depending on how long your finger is touching it.
Then they decided some things don't do anything at all if you tap them, only if you long press them.
Then they decided it should matter how hard you long press.
Then they decided you should memorize which quadrant of the screen you need to swipe to do something.
"intuitive" is a spectrum, and we are steadily moving to the less intuitive side. I think just giving users a bash prompt and a cheat sheet might be more intuitive at this point.
Thankfully I'm able to change settings to bring back the dedicated bottom navigation "buttons" (they are virtual, on screen)
Not perfect but I'm glad that it's an option
There are so many more buttons in cars now than when I first started driving. I've mostly adapted to them, except when I have to drive a friends car and everything is in the wrong fucking place. WE DO NOT NEED TO MOVE CRUISE CONTROL THANK YOU. And don't get me started about breaking the gear shift lever. There are hidden features in the old design that apparently the new designers didn't know about, but anyone who drives for a living or just cosplays at being an advanced driver knows about slapping an automatic transmission from reverse into drive...
Anyway, point is that I don't envy children trying to figure out all of the stalks and buttons on a modern car, and then immediately trying to figure out how to merge into highway traffic. It's no wonder everyone is waiting until they're older to drive. Smartphones feel categorically similar in their evolution.
Eventually however, the track pad was the one thing I really enjoyed about using an apple product.
I always assumed the bigger issue is that because this is strain based, extrapolating the feature to an iPad sized screen was possibly too challenging without resorting to something like an array of strain gauges to measure across the display. IIRC, no iPad ever got this feature. Given how it worked on an iPhone sized display, I can imagine challenge increases with screen size of measuring this accurately.
One also has to imagine that when Apple reviewed their usage metrics, was this feature even worth the cost to ship?
3D touch malfunctions badly with a slightly swelling battery pressing against the lcd backplate inside the phone. Or a bend in the phone chassis. The 6s case was bent for every person who carried it in their back pocket. I saw malfunctioning 3d touch several times every week back when I was in phone repair. Especially with carrier insurance refurbs, where the replacement parts were of especially poor quality. Carrier refurbs often had the cheapest batteries, screen assemblies and sometimes non original chassis.
It has a cracked screen (dead OLED is slowly spreading out from the top-right corner), shattered back glass, battery at 81% health, and the earpiece speaker doesn’t work properly so to make a call I have to use a headset or speaker mode.
But 3D Touch still works perfectly!
Mine is an iPhone 7 I bought refurbished back in February 2017. This phone is likely to have seen less use than a friend of mine's phone bought at the end of 2021. It spends 95% of its life connected to a power source (even when I actively use it), so I expect the battery to last quite some time.
According to my phone, over the last 10 days I had an average screen time of 3h34m per day. I use it to communicate and to consume media while commuting. I charge it whenever it needs some juice, it does get to down to 10%-20% sometimes.
But honestly I don't see how my usage can hurt it so much. And if my usage is indeed what damages the battery so much, then that seems to be Apples issue, considering how I'm really not a poweruser or whatever.
What battery health does your phone have? I can't imagine that having a phone connected to a power source 95% of its lifetime can be especially good for the battery.
What can be Apple's fault is the battery going to 10% after using it for 3h, but I don't think that's the point here.
> Letting it go down to 20% before charging it back up means the battery has to cycle
Apple actually says themselves, that "You complete one charge cycle when you’ve used (discharged) an amount that equals 100% of your battery’s capacity — but not necessarily all from one charge." [1]
The iPhone 12 mini has a 2,227mAh battery. Its battery health is at 86%, so effectively I have 1915mAh. But now you're also telling me that I can't use it past 20%, which leaves me with 1530mAh, or 68% of the original capacity.
I can totally agree that with long-term usage it's up to the user to optimize their battery usage for health. But my device was at 92% battery health after not even a full year and I simply won't accept that this is on me. Especially if we consider how expensive and complicated Apple makes it to replace a battery. Apple also tells me that I can charge my battery whenever I want.
To give more insight, GPS is fully disabled 99% of the time, it runs in dark mode, auto-brightness is disabled and I usually set it to a pretty low brightness, 5G is disabled and generally I remember disabling lots of things like "double tap to wake screen", "lift phone to wake screen" etc.
Whatever time it spends unplugged, is time spent draining the battery. Down to 90% or down to 0%, it's just a difference of amount.
If you keep it plugged most of the time, and only drain it to, say, 90% (and this is an arbitrary number), you only used 10% of one cycle. If you let it unplugged until it's down to 0%, you use 100% of one cycle.
If every day you let it go down to 0% and then charge it back up, in 10 days you've used 10 cycles.
If every day it only loses 10% (total) and charge it back up, in 10 days, you've used 1 cycle.
I'm not saying "it's your fault" or that "you shouldn't do it", I'm talking about objective use of the battery.
Yeah, I know it's a mobile phone, so one of the reasons for buying that is to use while out and about.
But the point is that not everyone uses it that way, which can explain why some people see the battery health going down faster than others, on the same device.
And that's not Apple's fault. Sure, you could argue that the battery life is ridiculously short, that the battery's health shouldn't degrade as fast, and so on. And I'd agree with that. But still, it's a different issue.
> not everyone uses it that way, which can explain why some people see the battery health going down faster than others
True, yes. However, and feel free to disagree, but from my experience the minority of people keep their phones plugged in as much as they can, at least in my social circle and work environment.
I knew that I would have to live with shorter battery life when buying a small phone with a small battery and I also know that batteries just loose health and that this is normal. The drop on my device just makes me think that maybe my device has some kind of issue, or received a battery which would be placed on the left side of a bell curve.
Wanted to check the exact stats - So, I bought it in the end of April 2021. That's 16 months ago. If a 14% loss of battery health during that time is normal, then maybe I had wrong expectations. It just seems excessive when comparing with other people/devices.
I'd agree with your point that people keeping the phone plugged in all the time are a minority. But even so, I wonder if screen time is enough of a metric to gauge "similar use patterns".
For example, my phone absolutely drains the battery when using Google Maps, whereas browsing HN on a basic text-only app doesn't seem to make a dent.
I know it's anecdotal, but I mostly keep my battery-powered electronics plugged-in when possible, and their batteries tend to degrade much less over the years compared to a friend's, who tends to unplug them and charge them when needed. And the electronics in question are fairly similar: iPhones and same-gen Macbooks.
Same for my work laptop (hp) which, after 4 years, still has around 80% of its original battery life, when my colleagues', who use them much more often on battery, only last around 50% of their new condition, if they weren't changed because of swelling.
The one kind of battery among mine that seem to have shorter lives are camera batteries. Which, of course, tend to get drained more since I don't have an outlet handy when out in the woods.
But I mostly do iOS software engineering, so the device spends most of it’s time plugged in.
In a few months, it won’t even need to try to stay under 80% anymore. It just will.
There were some battery drain issues in different versions of iOS 14 and I believe there was some unnecessary wear in there, as well as a couple 'recalibrations' of battery health in iOS. Maybe the phone was falsely reporting 100% at release and was corrected to a lower percentage.
I'd be curious to see if anyone with a fall 2020 still has over 90% battery health.
I think the issue is more that it was not very discoverable. A bet the vast majority of non-tech users didn't even know it existed and perhaps accidentally activated 3D touch much to their confusion.
Removing it simplifies the hardware, avoids accidental activations and is less maintenance work.
I still miss 3D Touch :(. I am happy that Macs still have Force Touch, even though Force Touch and haptic feedback are criminally underused. There are so many useful applications, e.g. OmniGraffle gives subtle haptic feedback when dragging an object and it aligns with another object. It's such a nice feature that other apps could learn from.
It’s tough to sell a feature that has no interface. A little too minority report arm flailing for me :)
Baloney - it was the 6 Plus, not the 6S, and it was far more rare than twitter would have had you believe.
It's a typical Cook's Apple experience to listen to 10 tracks from different albums, all called "Outro", after album chosen by me finishes playing with a track called "Outro" and is set to repeat.
Pick one song I shazamed and poof, I get to listen to "random" "identical" songs for hours. A gem.
I have different kinds of music. When at the gym, classical music is the last genre from my library I'd like to listen. When listening to ambient during work I don't want to suddenly get hard rock or rap. Preferably no vocals at all.
The iTunes.app was capable of playing the music I wanted. Things went sideways when it was renamed to Music.app.
However, for playlists, I think it is nifty, but afaik you can't have it both ways.
It really should be a per playlist toggle at the bottom "continue on radio when all songs in this playlist have finished playing."
For me, that's poor UX and fucked up good product (iTunes.app).
There’s a “infinity” toggle on the song list, which if you turn off stops that behaviour
The whole app seems to have been designed by a madman. I miss the bloated, yet functional, iTunes.
This works fine for western languages where the key to input a space is large and centered, but some keyboards like the Japanese flick input keyboard look more like phone numpads where the middle of the keyboard is taken by the “number keys” (each key represents a consonant). The space key is located on the right hand edge of the screen, and while the “long-press to move cursor” shortcut still works, it’s only useful for moving the cursor leftwards since your finger is already at the righthand edge of the screen when the shortcut triggers.
It’s quite an unfortunate casualty caught in the crossfire between i18n, feature discoverability, and hardware cost-cutting.
I just always use that long press on the space bar to move the cursor.
3D Touch is interesting from a technical point of view but it makes manufacture more complex and using the phone more complicated than it needs to be. I was always activating it by accident.
When it was first announced I was excited that haptic feedback would allow us to feel the edges of the virtual keyboard keys and improve typing accuracy. That's not what we got and I've found very little utility in the current implementation sadly.
It also makes it harder to get the screen replaced. Since I don't live near an Apple Store that's important to me. I want to be able to pop into a local locksmith and get them to change a broken screen while I wait. The alternative is either a long drive or sending the phone away for days on end.
If Apple really wanted to impress me they would replace the dictation key on the keyboard which I regularly trigger by accident with something useful like an Undo button. I have never used dictation so this is just a daily irritation to me.
So the cursor navigation feature activates on long press of the space bar, in iPhone models that don't have 3D touch?
I will say this, in 50,000+ 3D Touch iPhone screen repairs (conservative estimate) I don’t recall any complaints about non-working 3D Touch. I think probably 0.1% of iPhone users even knew it existed.
NO. Not only is this ridiculously cumbersome, but it's not marked on the keyboard. So 99+ % of Apple users undertake DOUBLE the keystrokes to arrow the cursor past the letters they want to delete and then use Apple's mislabeled Backspace key to get rid of them. I've been in the Apple store and heard a customer come in and ask if there's some way to configure the keyboard to have a legitimate Delete key.
Meanwhile everyone else manages to provide a real Delete key, even on SMALL laptops.
I long felt like once all iPhones (that supported the most recent iOS) had the feature than they could really take it and run with it in iOS. But this never happened.
But the usability improvements of it were great. In music ALL the time I would hold down on a song to pull up the menu, keep my finger down and scroll down to add to next, and lift up to select it. One swipe and I did what I wanted. I could do that quicker than it takes it to register that I am holding down in the first place now. It worked the same was as anything on the Menu on a Mac (holding down and releasing doing the command) and it just felt super intuitive.
I won't deny that it had a discoverability issue, but that feels like the wrong reason to remove the technology.
I am glad this technology still exists on the watch, which has an OS that was always designed with this in mind. So I think it works well there.
I long hope this comes back. But I have to imagine there is a reason this never came to the iPad so maybe that was a major contributor to it being cut.
These devices support 3D Touch: iPhone 6s, iPhone 6s Plus, iPhone 7, iPhone 7 Plus, iPhone 8, iPhone 8 Plus, iPhone X, iPhone XS, and iPhone XS Max.
Only now thanks to the OP I understand how to achieve this without 3D touch. Poor discoverability on this feature never ends.
First time trying it for me but it seems.. odd, maybe need to get used to it.
The prior mention of defining the start and end points of the selection is a bit more tricky and may not even be an actual feature, which involves moving the cursor around in a kind of handoff between start and stop point. That’s trickier to describe because it fellas like it may just be a quirky behavior that can be manipulated.
Apple has a problem with discoverability in quite a lot of features. There's many small little things in iOS that users don't know about and likely will never find out about, perhaps because they want to keep the UI clean.
There’s a whole Apple app - Tips - included with every iOS device, dedicated specifically to these small features.
It’s updated by Apple with new tips and tricks regularly, and you can choose to be notified each time a new ‘episode’ is released.
I imagine most iPhone users don’t know it is there!
On the one hand, thanks for the tip! On the other hand, Apple has an enormous discoverability problem, it's getting worse, and they're responding by making the UX dumber instead of addressing it head on.
Why is it being replaced? Because there's a new branding. Why is the old application being disabled? Because it would be insecure to keep it without security updates. Why does it need security updates? Because it accesses the internet. Why does a local music player need to access the internet? Because they merged the local music player and streaming music player.
So there's a ridiculous user experience and unnecessary deprecation, all because local functionality interacts with nonlocal functionality.
Kind of like an escape key on a keyboard.
Another one is that the illusion of pressing a tactile button is gone. 3D Touch would give tactile feedback only if the screen was pressed with force; this was realistic enough to simulate actual buttons on iphone7/8. The long press has no way of measuring force, so it accepts light touch too and still responds with haptic feedback; this doesn’t happen in the real world and the illusion is gone.
Just checked on my own behavior in this regard, and I seem to have grown a habit of just scrolling slightly enough to not make it appear to be a long press before actually resting my finger on the screen.
This might be a more common habit and would explain the consensus of long presses not being seen as too problematic.
Anecdotical, I remember not having to do this initial micro scroll as a more comfortable scrolling experience.
"All the way" is just moving the finger a couple of cm. The main difference is that 3d touch instantly activated the touchpad, now there is a small delay of 0.25s. Not a bad compromise if it means removing some hardware.
From the original post:
“Fast forward to today, the trackpad mode and selection feature technically still exist albeit in a lesser form. If you long press (aka hold down) on the spacebar of your touch screen keyboard (which works on iPad too) you can get into trackpad mode.”
Also confirmed by another commenter in this thread.
Samsung implementation was a bit gimmicky, gimmicks were the hallmark of Samsung during that time, but it is extremely useful for one thing: hover targets on web pages. It actually makes sites that are completely unusable on other phones usable again, and not only that, it is very intuitive.
And the best part is that it costs next to nothing to make and it doesn't take any space or make anything more fragile, if I am not mistaken it is just a few tweaks on the way the capacitive touchscreen sensor is driven. So why not keep it? UI wise Samsung was a bit clunky but it doesn't mean it doesn't have potential.
3D touch on the other hand is probably a bit more expensive as it requires extra components (pressure sensor). Also, pressure sensitive devices have a long history of being failures, but contactless tech is used all the time, the closest would be digitizers, they all support hovering and it is put to good use. I don't have anything against 3D touch, I think it is nice to have and cheap, the ability to use your phone as a scale is also a nice gimmick but between 3D touch and hovering, I would have bet on hovering. In the end, we have neither...
Apple probably collects usage statistics and knows no one (by approximation) uses it so they scrap it. That's sad, but understandable as well.
edit : fixed typos
Getting rid of 3DTouch feels to me more like a hardware cost reduction (+ harmonizing the system with the iPad) than anything.
– iPhone 6S
– iPhone 6S Plus
– iPhone 7
– iPhone 7 Plus
– iPhone 8
– iPhone 8 Plus
– iPhone X
– iPhone XS
– iPhone XS Max
The feature was discontinued with the release of iPhone 11. [2]
[1]: https://www.businessinsider.com/does-iphone-have-3d-touch
[2]: https://www.businessinsider.com/apple-discontinues-3d-touch-...
[1] Since iOS 13, 2019 [2] https://www.macworld.com/article/233056/ios-13-and-ipados-13...
And for real, I'm suspecting Android is better at this than iPhone
>>> My guess is that people had no idea it was there. Likely it had very low usage statistics and so Apple cut it in order to...
Right there.
I am often frustrated that I cannot edit a URL in the address bar - but not frustrated enough to use a different phone or explore.
What would be useful is some kind of "how to use your phones hidden features" guide on the phone (no not on a website somewhere an actual supported by Apple real tutorial). Then both I can find out and Apple can find the real ratio here - people who know how to use 3D whatever and who just don't bother.
I suspect that the long-press alternative in software was found to be sufficient alternative to not warrant the force-press. I wonder if this is where we are going on Mac too where, e.g., force press to trigger definitions of words is a godsend especially when leaving foreign languages,
On an iPhone? You've always been able to do that...
To be clear, I mean if the irl is longer than the width of the visible address bar, I cannot move the cursor outside the visible box and bring the rest of the url into view. So for example I might want to edit a query param.
One thing that no one mentions for 3D touch is gaming. Being able to aim and just "click" with the same finger is really amazing. Makes FPS games on the phone feel way better.
I know it was a power user feature, and I wish they kept it on the pro iPhones or reintroduced it there. One-handed text selection was an absolutely awesome feature, and it’s definitely not something everybody needs. But I too miss it dearly.
Personally I believe Apple was wrong here and basically lost the argument. The right-click standardized around a context menu. People generally understand this.
So imagine my surprise when Apple introduced Force Touch on the iPhone. This added weight and cost to the iPhone for a feature with no discoverability or consistency. The closest we got was "preview". The author says:
> My guess is that people had no idea it was there.
But that's only half the problem. It might be there or it might not depending on the app and who knows what behaviour you'd get if it was there.
Force/3D Touch I always considered a mistake along with:
- Removing the orientation lock button from the iPad
- Face ID (seriously, just give me a phone with Touch ID; put it on the back if you have to)
- Zooming out in Safari takes you to the list of "tabs" and there's no way not to do this
[1]: https://www.cultofmac.com/269222/steve-jobs-hated-idea-multi...
Why would Apple keep hardware that most people didn't know about and didn't use?
I do miss the headphone jack, but clearly Apple is not bringing that back.
My favourite iPhone feature that was removed though was being able to fully turn off WiFi from the Control Center (last seen in iOS 10).
I still much prefer any keyboard over Samsungs tho. The Samsung default keyboard is the worst I’ve used.
GBoard / Swiftkey does its darnest to ensure that it will never select a swear word and always pick 'duck' but give me an option for 'fuck'.
Flow you didn't need to be accurate, you could be 'close enough' and it figured out the word you wanted based on what you were writing. GBoard/Swiftkey get it wrong more often than I like.
I do use the keyboard cursor thing but to be honest text entry on a touchscreen has never really been good for me. I don’t think I’ve ever typed a sentence correctly in 15 years of iPhones. Even with autocorrect I’m often having to go back. Selection, cut, paste are all terrible. Tap somewhere and hope it offers to select a word but sometimes it doesn’t. Try to copy some text on a web page oops it’s a link. Tap elsewhere and try to paste but sometimes it doesn’t. Try to extend a selection and get weird multiline behaviour I can’t explain. Maybe I have the world’s biggest thumbs but it’s constant aggro that you just end up internalising.
On the one hand, I guess it's nice, I don't have to field calls from my family asking how to do something on the phone, or how to turn off a feature. (Well except for that time my mom accidentally turned on emergency sos mode and couldn't figure out how to turn it off for an hour.)
On the other hand, sometimes I would do something unexpected that seems cool, but now I don't know what that feature is called or how to purposely do it again. Was it triple back tap or long tap-short tap- long tap the volume button or maybe it was septuple swipe across the home screen... I'll never know.
It makes me angry every single time I try to take an action on a notification on my iPad.
The iPad never had 3D Touch.
It boggles my mind how they put up with it when they can change it.
I'm not a UX specialist, but even I could connect the dots on how 3D touch was just the iOS version of the long-deprecated Android menu button: useful, but with non-existent discoverability. Additionally, apps would support it inconsistently, so most users wouldn't know the functionality exists at all, and of those that do know about it, sometimes the feature does nothing at all.
I am soooo happy this physical feature is gone. Personally, I hated it.
I'm still a fan of the SE (give me touchID or death). I still want a touchID phone with more advanced camera capabilities.
This feature caused no end of confusion, even as an experienced iOS user. Completely fucked up any software trying to do long press detection. But even after adapting for that, the pressure differential for touching just didn't work.
But if you were willing to do that, whole new interface possibilities open up because you have an entirely new dimension to work with! I made a music instrument app where position on screen controls note/frequency and pressure controls amplitude and it works very smoothly[0]. But all the established paradigms that devs and users know revolve around 2D, so to take advantage of the force touch you have to both invent a new paradigm and teach it to users, all while supporting devices without 3D touch or losing that share of the market. There weren’t enough takers or it didn’t happen fast enough so Apple decided it wasn’t worth keeping, which is understandable but also kinda tragic in my admitedly biased opinion.
[0] Xalophone digital musical instrument incorporating 3D Touch: https://apps.apple.com/ca/app/xalophone/id1420669553
I did not know that. Thank you!
One thing that annoyed me quite much when I received my6S Plus was that fixing typos felt clunky (couldn't move the cursor not that easy as before).
If I just would have known that 2 years earlier, I would still have a lot more colorized hair... I love that feature!
However, I didn't know about the space bar alternative until after I upgraded. Honestly I don't even miss 3D touch after a little adjustment period. I forgot I don't have it. So the new alternative works great for me
There are all sorts of things out there a lot of people don’t figure out, or old features that new users never discover, but they require maintenance of code — this required a component, and saw poor adoption amongst many, many devs. Apple surely deserves some blame for it never taking off, primarily for a lack of discoverability. They added this new interaction after 7 years of a well-established and simple model, and didn’t give any visual indications for where you should be trying to use it. Plus, it was never on iPads, and only made it to iPhone models for four generations (6S, 7, 8/X, and XS — and it wasn’t on the XR).
It was a great idea, and I still wish they doubled down on it, but it makes perfect sense for them to have let it go for other advantages that ultimately will be used by more people and sell more phones.
As a developer, it'd be nice if I didn't have to support a minority. I appreciate that iOS streamlines the experience that I have to develop for.
^
ctrl-< < > ctrl->
V
shiftlock cut cpy pst
srch shr …
That’s all I need to edit/select text instead of these glamour gestures. Assuming ctrl-likes use \b word boundaries.I’d also like to turn off input focus zooming in safari.
Related, I’d also like to jumps 5s in videos rather than 15s. Not very useful to rewatch 15s when you missed a word or a visual.
Tap the text field (twice if not already selected) and you'll have tooltip with "Scan Text". Selecting that turns on the camera, replacing the keyboard, and text under the camera is temporarily inserted, with an "insert text" button. Nice!
Like, everything else since then seems to just have been some stupid gimmick driven by the bean counters and not any evidence based approach. I assume modern academic human interface designers have been going quietly insane for the past few decades.
I think myself as a power user for 3D Touch especially for using the keyboard to navigate within text. Not to mention previews (while I know most of these features still work to some extent by long press, it's more cumbersome).
I also get it that many "normal" users didn't even know about the feature and added complexity to hardware, so it was right for Apple to remove it, but I really miss it.
Most users don't know how to use half the iPhone's navigation features. And the problem here isn't the users, but that they are completely undiscoverable. At some point, I think the home-button had like 11 different functions based on how you pressed it and in what context.
Everything to make things look "sleek".
That is my issue with so many of Apple's features. Apple fans are so happy to shout "it just works. You just have to double tap, or three finger swipe or hold your mouse in the corner or press harder on the screen"
If the UI doesn't tell me about those hidden methods, then the feature doesn't exist.
I do wonder if it'll come back at some point.
> press and hold tab icon in safari for closing tabs and creating new private tab
> press and release on the navigation dots at the bottom of Home Screen to get an overview of all screens and you get to show or hide the screens
Also the feature to position your courser is still there, just press harder on the space key, Apple confined it to that key/area
Haptic Touch and 3D Touch are different things[0] and the feature was removed after the iPhone XS line. 3D touch could actually measure the amount of force you put into the screen, it wasn't simply a "long press" like Haptic Touch is.
> Also the feature to position your courser is still there, just press harder on the space key, Apple confined it to that key/area
Yeah, but it's neutered in 3 ways at least.
1. With 3D Touch you didn't have to confine it to the space bar.
2. With 3D Touch you could press harder after going into cursor mode, and it would start selecting text.
3. With 3D Touch you didn't have to wait for a long press to register to activate it.
You can see an example of it in this video[1]
If you have a phone that supports 3D Touch, give it a try. You’ll find that simply long pressing on the button doesn’t work, you have to apply a certain degree of pressure before it responds.
The replacement method works, but it is indeed subpar. It annoys me that my 3 generation newer phone is a downgrade in this regard, but I can live with it.
This trackpad mode sounds interesting though, I'll try it :)
And nothing's changed since then. Sorry. It's too confusing.
If there's a proper, disclosed affordance to do the same things... then I guess they are harmless. But if there is ANY compromise made to implement them, good riddance.
I wish they would bring it back via Force Touch on iPhones.
Why can't Apple make the feature activate on a regular "long press" for the other models?
so actually it works on long press right now.
Well what do you know...
Your iPhone 13 has Haptic Touch, not 3D Touch. Haptic Touch and 3D Touch are different things[0] and the feature was removed after the iPhone XS line. 3D Touch could actually measure the amount of force you put into the screen, it wasn't simply a "long press" like Haptic Touch is.
The feature has also been made worse in at least 2 ways.
1. With 3D Touch you didn't have to confine it to the space bar.
2. With 3D Touch you could press harder after going into cursor mode, and it would start selecting text.
3. With 3D Touch you didn't have to wait for a long press to register to activate it.
You can see an example of it in this video[1]
Kudos to Apple.
Sometimes the 1% of power users are right and not listening to them leads to bland and less useful products.
I haven't used Android enough to know if it's the same issue, but the main problem is discoverability. iOS, and many apps, have a ton of features, but there isn't enough screen space to do hint to how to use them. There also isn't enough space to add more buttons. So we end up with these weird swiping motions, long press, 3D Touch or hard to hit icons.
Maybe it's just me being old, but I'd recommend stripping a ton of features from phones and their apps. If you need to do anything more complicated, push people to use a device that's designed for higher levels of interaction.
Just give me a phone with a bunch of pictures and mandatory like buttons. That’s 90% of computing’s use case and all we need.
Which bucket does that 1% fall into though? It’s not as simple as saying only a few people use it, trash it.