According to these conspiracy theories they should have just gone directly to an underground lair under a volcano because all they do all day, every day is try to be as evil as possible.
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
According to these conspiracy theories they should have just gone directly to an underground lair under a volcano because all they do all day, every day is try to be as evil as possible.
good thing we have you here to explain things to us...
Like sarcasm apparently.
Yes this just proves that Apple doesn’t care about devices with home buttons and that swipes on the X will be instantaneous.
[doublepost=1506091931][/doublepost]
What’s absurd about it?
Did it hurt when you moved those goal posts? Where will you move them next?
We need somebody with an iPhone 8 to make a video side by side with a 7 running 10.3.3 closing apps to be completely sure the lag remains.
There are videos in the thread showing exactly that.
The video posted shows the 8 and 7 plus both running iOS 11.
They both appear to be about the same but to demonstrate the bigger difference we need to see the 7 running 10.3.3 next to the 8 on 11.
That will really help open people's eyes to what we've been complaining about with the delay of response time with the capacitive button under iOS 11.
Ah, I misread your post.
Why would the "lag" (sic) have disappeared from the 7 without software updates?
this is, at least, a fun thread.
there's a wide gap between fact and opinion. saying there's a lag may be a fact, but explaining apple's reasoning, and secret plans, is just ridiculous. believe whatever you want; i personally am interested in what people experience, and facts that are, in fact, real.
there's a wide gap between fact and opinion. saying there's a lag may be a fact, but explaining apple's reasoning, and secret plans, is just ridiculous. believe whatever you want; i personally am interested in what people experience, and facts that are, in fact, real.
You do realize the 7 had a similar issue last year, right? It was corrected.
https://forums.macrumors.com/threads/slight-lag-on-iphone-7.1997556/#post-23492286
https://forums.macrumors.com/threads/slight-lag-on-iphone-7.1997556/#post-23492286
Let’s install iOS 11 on a smart refrigerator, just to be sure that there is a lag.
And then we can test iOS 11 on a TexasInstrument graphics calculator.
Yeah, brilliant idea. That will show Apple the new evil Corp how evil they are.
And then we can test iOS 11 on a TexasInstrument graphics calculator.
Yeah, brilliant idea. That will show Apple the new evil Corp how evil they are.
Agreed. If aliens landed on the planet and all they had was this thread to learn the English language they would have a MAJOR misconception about what the word “proof” means.
Nahhh, they would just kill us all so we don’t continue to reproduce.
Yes that is the animation glitch in the beginning of iOS 10. The animation did start instantly but had a little hiccup. The button was and has been responding instantly when you push it all the way though iOS 10 until iOS 11.
There isn't a hesitation in the animation in iOS 11. It's simply that nothing is happing for a half second or so and then the animation begins after pressing the button. It's a change in timing with the capacitive buttons on the 7, 7plus and now looks like the 8 in iOS 11. It makes the phone feel slower.
[doublepost=1506097141][/doublepost]
Somebody already posted this but it shows best what we are describing. Notice how the 10.3.3 phone begins the animation to close the app instantly whereas the iOS 11 device is always slightly behind closing.
I'm not sure if I'm seeing things but...on my antique iPad mini 2 with iOS 11, I notice the delay is not there when launching apps from dock as compared to from the apps page. Bizarre, I hope this gets fixed in 11.1
Last year people were complaining that the animation started too fast. The problem was that the closing started immediately and then if you did double click the animation had to awkwardly jump from the close animation into multitasking. From that thread, but it was widely discussed
Seems to me people are never happy.
You can clearly see the home button wasn't pushed at the same time. Thats poor test.
Please note in my OP I said “8 and X”. It has yet to be disproven whether the X has the lag or not and I assure you it won’t. The 8 was always flaky from the beginning because it’s essentially a upgraded 7.
The only thing Apple cares about are profits and they would love everyone to buy the X
*facepalm*
Yeah sure a few of the times he even missed the home button before he hit the iOS 10 one but most of the time he hit them at the same time and lo and behold 10.3.3 closed faster in all of those times.
Slow the video down and you'll see. He wasn't trying to make 10.3.3 faster. It just is.
Here's what it boils down to I think, and I'm pretty sure I said like 10 pages or so ago to cries of fanboy.
Early in the iOS 10 cycle the close animation started as soon as the button on the 7 was pressed, resulting in slightly awkward animation translightly if the double click actually occurred.
In the iOS 11 cycle so far the animation instead appears to wait for the entire double click period to expire before beginning.
Sometime well into the iOS 10 cycle (10.2 or 10.3) Apple found the Goldilocks "just right" time.
There is no "proof" of forced obsolescence. No "proof" of trying to make the X faster. The one and only thing anyone can prove is that there is a stupid regression, a bug, in a part of the system that Apple were in no particular hurry to fix the first time.
It's a dumb, trivial error and it really shouldn't happen, but it does. It is absolutely not worth the tears shed, vitriol spewed and crackpot theories sprayed around. Chill out. It'll get fixed.
Early in the iOS 10 cycle the close animation started as soon as the button on the 7 was pressed, resulting in slightly awkward animation translightly if the double click actually occurred.
In the iOS 11 cycle so far the animation instead appears to wait for the entire double click period to expire before beginning.
Sometime well into the iOS 10 cycle (10.2 or 10.3) Apple found the Goldilocks "just right" time.
There is no "proof" of forced obsolescence. No "proof" of trying to make the X faster. The one and only thing anyone can prove is that there is a stupid regression, a bug, in a part of the system that Apple were in no particular hurry to fix the first time.
It's a dumb, trivial error and it really shouldn't happen, but it does. It is absolutely not worth the tears shed, vitriol spewed and crackpot theories sprayed around. Chill out. It'll get fixed.
Seems like the "AND" part has been disproven. Goalposts are still being moved and deflections are still in play--business as usual.
As long as iPhone X does not have this lag (and it won’t) my point is still being proven.
- Status