Earlier quoted context omitted.
Your solutions are a little off the mark. Treating the animation as the problem is merely treating the symptoms. What needs to happen here is pressing the button needs to immediately register the press elsewhere in the code. The UI animations and the button tap should be decoupled entirely. Then the user can tap away as fast as their heart desires and only the animations are going to continue on. That’s an easy probl…
My professor likes to tell this story about keyboard buffers that I never quite understood. Basically, in this old time terminal setup he would start typing the password before the prompt showed up or something and when it did, it would just sail through. Sort of like how I can apt upgrade while apt update is still running but fancier and a couple of decades before...
Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
381–390 of 501 posts
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#382I probably own more Apple devices than most people here (even considering this is HN we're talking about) because I do a lot of iOS programming and I have to use them as test devices. I also own the latest devices. But this problem is not some stupid complaint coming from uninformed people. This calculator thing was a perfect symbolism for all this bullshit that's been going on since iOS 11 release because the bug is…
I think you might want to debug this like a problem rather than assume it’s all due to Apple errors. With all that’s going on I’d probably just jump all the way to a full restore.
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#383As soon as I upgraded my 6s to 11, I saw performance seriously degrade. It takes -seconds- to bring up the iMessage editor. My immediate thought was that Apple had liberally sprinkled wait() into the iOS 11 code base so that I'd feel like my ole A9 CPU just wasn't cutting it any more and I'd realize, as they do, it's time to upgrade. Or... maybe they are running every key stroke through the new Azure-enabled Cray com…
The worst thing for me is the Camera. If I want to take a photo of something that's just happening I don't even bother anymore since I can expect it to take 10 seconds to wake the phone, get into the camera, and have the shutter button respond and have it actually take a photo (sometimes it looks like it took a photo but it actually didn't save!).
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#384People are talking about "lag" and performance, as if this was a "the system can't handle it!" issue. This is a misleading description. The actual issue is that some developer at Apple screwed up their animation configuration when implementing the calculator redesign, and nobody tested adding more than two numbers together quickly. Multiple failures, none involving system performance. What's happening is: the operato…
Your solutions are a little off the mark. Treating the animation as the problem is merely treating the symptoms. What needs to happen here is pressing the button needs to immediately register the press elsewhere in the code. The UI animations and the button tap should be decoupled entirely. Then the user can tap away as fast as their heart desires and only the animations are going to continue on. That’s an easy probl…
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#385Earlier quoted context omitted.
Your solutions are a little off the mark. Treating the animation as the problem is merely treating the symptoms. What needs to happen here is pressing the button needs to immediately register the press elsewhere in the code. The UI animations and the button tap should be decoupled entirely. Then the user can tap away as fast as their heart desires and only the animations are going to continue on. That’s an easy probl…
Isn't 'never' an oversimplification? Sometimes there is a feedback loop between UI effects and user input, or the user input changes the way the UI registers hits, which means subsequent input depends on complete processing of prior inputs. On a static view like a calculator grid, you should default to non blocking animation, but sometimes blocking is the desired behavior.
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#386Earlier quoted context omitted.
> cryptic UI, teen-oriented These things go hand-in-hand by the way. And that's not a complaint, it's just funny how "only teens bother to figure this out" can be an honest-to-goodness feature under specific circumstances. Especially if you (basically) need to be "introduced" to a program and all of its quirks through your friends.
I hated it at first, but I've come to really appreciate being able to swipe around through almost all the screens, vs. having to stretch across my phone to hit menus on the far corners in other apps
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#387Another UX issue I've seen with the iPhone calculator: My wife is a nurse and uses the iPhone calculator to calculate doses. She performed a calculation like 2.25 / 1.5 = It did give the correct answer of 1.5 . However, there was no animation or blanking out of the display to easily distinguish between the operand of 1.5 and the result of 1.5. She thought it was a bug and wasn't giving her an answer. I always thought…
I just tested this and it does animate (a brief flash). This is on iOS 11, so maybe you have a different version?
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#388People are talking about "lag" and performance, as if this was a "the system can't handle it!" issue. This is a misleading description. The actual issue is that some developer at Apple screwed up their animation configuration when implementing the calculator redesign, and nobody tested adding more than two numbers together quickly. Multiple failures, none involving system performance. What's happening is: the operato…
This shows how important UX really is. UI can be all glam and shiny, but the software with the most accessible of UX wins, more often than not. I always come back to the example of WhatsApp and how it took on SMS, IM, and emails and won. People claiming WhatsApp went in mobile first are getting it only partially right. WhatsApp defined itself as a replacement for SMS: No login passwords, no chat history, cross platfo…
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#389Earlier quoted context omitted.
Technically the 6s is now [latest - 2] hardware. X/8/8+ have the A11 Bionic; 7/7+ have the A10 Fusion; 6s has the A9.
Exactly what I said. It runs "fine" on 7, while it runs slow(er) on 6S.
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#390Earlier quoted context omitted.
Isn't 'never' an oversimplification? Sometimes there is a feedback loop between UI effects and user input, or the user input changes the way the UI registers hits, which means subsequent input depends on complete processing of prior inputs. On a static view like a calculator grid, you should default to non blocking animation, but sometimes blocking is the desired behavior.
What's a concrete example of this?