Lol, I’m on the 7 plus too and there’s clearly more of a lag compared to 10.3.3. Downgrade and try for yourself.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple has PURPOSELY introduced lag/delay with Home Button interactions
- Thread starter d5aqoëp
- Start date
-
- Tags
- ios 11
- Sort by reaction score
- Status
We'll all know if this planned obsolescence is true if the iPhone 8 with the same home button behaves the same way as an iPhone 7 on iOS 10 behaves.
If the iPhone 8 still has the lag I will believe it is by design which I will think is a huge step backwards with the overall feel of fluidity with iOS. iOS 10 is awesome in this regard.
If the iPhone 8 still has the lag I will believe it is by design which I will think is a huge step backwards with the overall feel of fluidity with iOS. iOS 10 is awesome in this regard.
Last edited:
3-4 people? so it's a global conspiracy?
seriously, if some people are experiencing lag, then... some people are experiencing lag. this is not proof of a purposeful effort by apple to 'destroy' the home button.
sure, the button is on it's way out, but that doesn't mean apple has intentionally 'damaged' it's behavior (fine, btw, on my SE).
How many times does this have to be explained. How do people like this survive to adulthood?
It is a BUG where the animation to close an app does not start until the time to see if it's a double click happens.
Simple proof:
Settings -> General -> Accessibility -> Home Button -> Click Speed
Set it to default and press the home button. Note there is indeed a short delay.
Set it to Slowest and note the delay is much longer.
Set it back to Default and note the delay is reduced again.
It is a simple bug
It is a BUG where the animation to close an app does not start until the time to see if it's a double click happens.
Simple proof:
Settings -> General -> Accessibility -> Home Button -> Click Speed
Set it to default and press the home button. Note there is indeed a short delay.
Set it to Slowest and note the delay is much longer.
Set it back to Default and note the delay is reduced again.
It is a simple bug
I think most the people who are experiencing this are people with the iPhone 7 and 7 plus. (Myself included) when I see the videos of the 6S and below (with the physical button) it looks like it's the same behavior as before. The OS already is waiting a half second to see if you are going to click again to enter multitasking. If anything the animation (once it starts on the 6S) seems to close faster than before. But us people with the iPhone 7 home button are used to instant response on our non physical home button on iOS 10. It doesn't wait for the second click. The animation starts instantly. So in iOS 11 it feels like every other iPhone with a physical home button again and we noticed it right away and it drives us nuts! Could be a bug. Could be by design. Could be planned obsolescence. We really don't know. But like I said. If the iPhone 8 behaves like a iPhone 7 that is on iOS 10.... Well.. seems obvious to me. We will see. We will see.
Last edited:
The 8 might well not act the same given its probably a seoerate code path for the swipe up. Logic dictates though that, as you say, it's the 7 with the capacitive button and not the models before it, that its not deliberate obsolescence.
I am downgrading my iPhone 6 or iPad whichever to iOS 10 so I can find out whether Apple fixes it by next year so we can have proof as to who is right once and for all.
Do you remember iOS 10.0? It was definitely not as fluid as 10.3
He is talking about the 8 with the capacitive button. Its the X which has the swipe up. If the 8 does not have this delay we have a confirmation.
Apple needs to start including OCD meds in their packaging for all future iPhones...wow
Right. But the instant response from the home button on the iPhone 7 has been there all along.
My mistake. Got it mixed up with X
Apologies imagineadam
[doublepost=1505411451][/doublepost]
There was actually a widely reported (and complained about) issue earlier in 10 where the animation was starting too fast. What happened is that when you did end up double clicking the animation to close/minimize would have to awkwardly transition to the multitasking view. There is precedent for problems in this area
bopajuice: March 22, 2016 - September 14th, 2017
People also start to see things that are not there as a way of justifying a new purchase. My dad is famous for this. For example, he starts working on my mom, complaining about the TV, the picture, lack of features, then he goes on to talk about something new he found and how it compares, then he claims he can no longer use the old TV that it's outdated, and low and behold he buys a new one. Kind of funny to watch.
Oh yeah for sure. The behavior/speed of reaction is exactly the same but they tuned up the animations some in 10.3 so it's not as wonky looking as before. But I will not upgrade to iOS 11 unless they return the home button behavior back to how it is in iOS 10. I really don't think I need a bionic chip to make this happen but we will see!
10.3.3 on my 6s, sometimes there's a small delay too, it's set to Default for the HB speed. Probably just the OS.
Very little lag on my 7 Plus. And if I turn on the Reduce Motion feature it is even faster.
Um, that doesn't happen on my iPhone 6.
[doublepost=1505413356][/doublepost]
Bull****. I just tested it out myself. I'm not blind. I can see an app immediately close back down just fine. One second delay my ass.
It does happen. The iPhone 6 is faster than the 7
https://streamable.com/6s01k
I currently have the 6 on iOS 11 and its behaving the same as the 7 Plus. I can post a video if you want
Just checked with my iPad. The delay is there even with reduce motion
First of all, if Apple did want to introduce an artificial slowdown on closing an app while it's still opening, I'm fine with that. I can't say I've never clicked the wrong app and immediately tried to get back out. But it's a rare enough occurrence that I'm not the least bit bothered by it in any way. It's not a common usage pattern, it's a mistake pattern. I'd rather they fix real issues, not some edge cases.
That said, I just tested this on a 6 Plus running the GM. And I honestly don't see the issue. One my phone the app closes. It doesn't even finish the opening animation. It just closes. So either the problem doesn't exist on the 6 Plus or I'm just not seeing the problem. Either way, I'm fine.
And before you ask, I won't be posting a video to "prove" anything. Because I honestly don't care who believes me and who doesn't.
- Status