Sidebar Sidebar
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

Status
Not open for further replies.
Feenician said:
Do they have X-Files on Netflix? That’s this thread. The one about Do Not Disturb While Driving is Monty Python crossed with Benny Hill.
Click to expand...

MacRumors is my General Hospital, Days of Our Lives and All My Children, ...all combined in to one.

I can make a better show from this forum alone than Silicone Valley TV show. There is enough material that will make me reach and keep the show going for a decade.
 
  • Like
Reactions: Martyimac and Feenician
trifid said:
I think it's also a new animation in iOS11 that seems more sloppy and slower. I went ahead and enabled reduce motion on, and now the entire interaction seems faster than iOS10. It's not ideal because there are some parts of iOS that work much differently like the app switcher, but it's better for me than the sloppy animation.

The whole animation/input-blocking saga from iOS7 to now makes me think Apple engineers either do this on purpose or are incompetent. There isn't any other explanation.
Click to expand...

The input blocking this time around is very inconsistent. Calculator app and the 1+2+3 = 23 is an example of input blocking causing an issue.
 
  • Like
Reactions: trifid
KGB7 said:
Tested the calculator. 1+2+3=6.
Click to expand...

If you type very quickly in a specific way it does indeed block input. Whatever intern they assigned to it decided to code their own special snowflake buttons for the arithmetic operators. When you tap them they stay lit until you hit a number, whereupon they slowly fade out. If you hit a number, then the operator again before it’s faded out it doesn’t accept the input. It is pretty damn stupid but on the other hand I’m not going to declare an entire phone useless for an edge case in the bundled calculator.

Mentioning in it the “hilariously over the top reaction” thread is very appropriate though. Thanks @Act3
 
  • Like
Reactions: MEJHarrison and trifid
Act3 said:
The input blocking this time around is very inconsistent. Calculator app and the 1+2+3 = 23 is an example of input blocking causing an issue.
Click to expand...

The one that infuriates me is... Apple fixed input-blocking during unlock animation, and when switching apps, which is probably the most contentious use case because it's so common and basic for any iPhone user, but there is still input-blocking on iOS folders!!! So on my iphone app dock I have a folder with apps, whenever I interact with that it's input-blocking extravaganza.

This disrupts the fluidity of navigating iOS, is so inconsistent there is no explanation as I said above. Is it plain incompetence from Apple?
[doublepost=1506121262][/doublepost]
Feenician said:
If you type very quickly in a specific way it does indeed block input. Whatever intern they assigned to it decided to code their own special snowflake buttons for the arithmetic operators. When you tap them they stay lit until you hit a number, whereupon they slowly fade out. If you hit a number, then the operator again before it’s faded out it doesn’t accept the input. It is pretty damn stupid but on the other hand I’m not going to declare an entire phone useless for an edge case in the bundled calculator.

Mentioning in it the “hilariously over the top reaction” thread is very appropriate though. Thanks @Act3
Click to expand...

Holy shiii, I actually just tested it out, what a disaster of UX. Great example of input-blocking incompetence from Apple.
 
  • Like
Reactions: Act3
Feenician said:
If you type very quickly in a specific way it does indeed block input. Whatever intern they assigned to it decided to code their own special snowflake buttons for the arithmetic operators. When you tap them they stay lit until you hit a number, whereupon they slowly fade out. If you hit a number, then the operator again before it’s faded out it doesn’t accept the input. It is pretty damn stupid but on the other hand I’m not going to declare an entire phone useless for an edge case in the bundled calculator.

Mentioning in it the “hilariously over the top reaction” thread is very appropriate though. Thanks @Act3
Click to expand...

Well adding numbers in a fast sequence is a very common task to do with a calculator. A very basic task that calculators from decades ago could do much smoother.
 
  • Like
Reactions: TommyA6 and Feenician
trifid said:
Holy shiii, I actually just tested it out, what a disaster of UX. Great example of input-blocking incompetence from Apple.
Click to expand...

It is and I won’t defend them on it. I think a bit too much fell victim to the 80/20 rule (anyone who had had to deliver a complex project is familiar with this rule) and it turned out more like 70/30 this year and that extra 10 is a bit too visible. I won’t make excuses for them. It’ll all get fixed but this was a bad year for the .0 release for stupid crap like that. Even though I’ve been running these since early betas without a thought of reverting, and there’s plenty to be happy about in iOS 11, I do hope someone is taking notes over there.
[doublepost=1506121795][/doublepost]
Act3 said:
Well adding numbers in a fast sequence is a very common task to do with a calculator. A very basic task that calculators from decades ago could do much smoother.
Click to expand...

Agreed. All I’m really saying on that is that it’s pretty easy to get around. See my actual thoughts on it above.
 
  • Like
Reactions: trifid
Feenician said:
If you type very quickly in a specific way it does indeed block input. Whatever intern they assigned to it decided to code their own special snowflake buttons for the arithmetic operators. When you tap them they stay lit until you hit a number, whereupon they slowly fade out. If you hit a number, then the operator again before it’s faded out it doesn’t accept the input. It is pretty damn stupid but on the other hand I’m not going to declare an entire phone useless for an edge case in the bundled calculator.

Mentioning in it the “hilariously over the top reaction” thread is very appropriate though. Thanks @Act3
Click to expand...

Slow down Robocop. Dont rush me while im trying to calculate my monthly payments on my Maserati. :p

Im good at alot of things, but i cant input random numbers fast enough in to a calc for it to have a heart attack.
[doublepost=1506122344][/doublepost]
fisherking said:
that's what they want you to believe...
Click to expand...

Get off my lawn, you are not my father.
 
Last edited:
  • Like
Reactions: Feenician
Radon87000 said:
It will be lightning fast on the X. I don't expect the home button devices to be fixed
Click to expand...
Right. You can't really delay a gesture. It will be instant.

So us people with a 7/7+ who are on iOS 10.3.3 will always have a faster home button even than the 8 unless they return it's behavior back. I'm staying put.

I don't need battery drain, stuck location arrows, stuttery 3D Touch, slower performance, CC center toggles that don't actually turn things off... I could go on. But right now 10.3.3 is the pinnacle of my iPhone 7's software and I don't think iOS 11 can get better for my device than 10.3.3. I hope I'm wrong and a 11.1 (or later) can match performance but based on history. Probably not.
 
  • Like
Reactions: Kalloud
forget the updated code, enhancements, new features. why upgrade to a new OS, if it means a slight lag when u click the home button? :eek: (which, btw, i am not seeing on my SE).

all i know is, on my iphone, ios 11 is as good as (or better than) any ios i've run so far. still, to each his (or her) own...
 
Radon87000 said:
The thing is no one including Apple cares about iPhone 8. Its all about iPhone X
Click to expand...
Speak for yourself. I am extremely happy with my 8Plus, as are 4 others in my family. 8Plus is noticeably faster than my 7Plus and the home button lag is noticeably less visible as well.
 
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back