Live data from Hacker News

Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

reddit.com

301–310 of 501 posts

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#301

As 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…

My biggest gripe is the flashlight delay - swipe up for control center, tap flashlight, and the actual light takes easily a third of a second to turn on. I suspect that's also waiting for the stupid animation to complete. Honestly I feel like the people in charge of iOS have stopped using the devices personally. I have no other explanation for so much annoying crap slipping through (ok, other than some idiot exec bei…

The flashlight behaviour is odd, I just tried it and I got the same delay the first time I turned it on, but no delay after turning it on multiple times. It's almost as if the code was swapped out to a slow disk and you have to wait for it to be swapped back in before the first use. There's still no good reason why it should take such a noticeable time, though.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#302
It's not only Apple that is regressing. calc.exe crashes at startup my Win 10 machine 50% of the time. It needs a remote procedure call to work now.

Activation of application Microsoft.WindowsCalculator_8wekyb3d8bbwe!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#303

I 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 have the latest iOS installed

If you mean one of the developer betas then that's the cause of ... > [apps take a long time to load]

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#304

I 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 have the latest iOS installed If you mean one of the developer betas then that's the cause of ... > [apps take a long time to load]

No, i have tried all versions and currently have the public version. I have given up on developer betas already, I don't trust them anymore. But I expected public OS to work as expected.

So no, the developer beta is not the cause. It happens to me and a lot of my "normal" friends who just upgraded their iOS because it kept bothering them with push notification to upgrade.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#305
post #182

Earlier quoted context omitted.

> 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. That was actually recently debunked by Futuremark https://www.futuremark.com/pressreleases/is-it-true-that-iph... . Important excerpts found at the bottom of the page: > Our benchmarking data shows that, ra…

What is debunked? That the CPU has not changed during the upgrade? No shit sherlock. Synthetic benchmarks tell nothing of the end-user experience. Does Apple sprinkle wait()? No. Does the system become more and more complex and Apple taking less time to optimize because it runs “fine” on the [latest - 1] hardware? Yes.

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.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#306
post #53

People 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…

> cross platform

Only mobile, the web version is shitty because it hosts a web server on your phone which is unreliable. And even with that you can only access the web version from one computer and it does not work well on tablets.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#307

Earlier quoted context omitted.

My iPhone 7 - the latest iPhone at the time iOS 11 came out, and with the fastest single threaded mobile CPU for some time - can no longer play locally downloaded audio and be used at the same time without stuttering constantly. Everything is broken on iOS 11. Extremely frustrating. I will buy a new phone, but not an iPhone.

I have an iPhone 7 and I do not experience this at all.

On the other anecdotal hand, I have an iPhone 7 and do experience this - normally through Overcast but sometimes Music will stutter and jank.

HOWEVER I am running the developer preview betas which are notorious for being UX janky and logging insane amounts of crap on every action the OS takes. Which probably explains it for me at least.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#308

I 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…

>5. Yesterday I was trying to take a picture and opened the camera. And YES, I mean the native camera app that ships with iOS. I saw the camera UI launch, but there was no "camera". It was just a black screen. I've become accustomed to this type of lag in app loading so i waited for my camera to "boot up". It never did. The camera app was open and there were all the UI components, but it wasn't capturing anything. I have never seen anything like this before.

On iOS 10, I noticed, if I swipe the lock screen left and right really fast where it brings in the camera, it eventually gets stuck. Like half the screen is now black and nothing happens until I hit the reset button. This is reproducible. It seemed to me like a really weird little bug to have on maybe the most popular mobile OS on earth but brushed it off as me being anal about something not even Apple considers a problem. This calculator story is a bit of a waking call that Apple UX quality genuinely did get worse in recent years. It's little things that add up. It's the little annoyances with Android that keep me coming back to iOS but now it seems like they're introducing all kinds of new issues with iOS. Ugly.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#309
post #185

Earlier quoted context omitted.

> I hate to be this guy but Steve Jobs would have fucking eviscerated the team that produced this. I'm pretty sure the very similar numeric spinner issue on iOS has been around since Jobs was alive and running the show, so the idea that he would have reacted swiftly and decisively to an issue like this is not merely unverifiable speculation, but contrary to what (inconclusive, to be sure) evidence is available.

The numeric spinner issue is much less severe. Calculators are often used in higher speed for a lot of calculations. That bug makes the calculator unusable for many people. The spinner is not used that often and waiting for an extra second there doesn't add up as much time.

That's assuming you know about it and all you have to lose is time.

Since it's an alarm, as another comment has exemplified, you may actually miss an important event in your life because you didn't know to wait for an animation to complete before saving your alarm.

I would say that this is severe given the potential outcome.

Similarly, the calculator bug is more of an annoyance for people who know about it, which is already bad, but the problem really manifests to those who do not know about it and may end up, say, wiring the wrong amount in a money transfer because their phone calculator didn't finish the animation in time to register actual key presses.

This is UI making the outcome of user operations actually wrong, not just laggy.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#310
post #203

Earlier quoted context omitted.

Since iOS 10 the system apps have been on the App Store, and as far as I know, they can now be updated that way, too.

They‘re listed on the App Store but they‘re fake listings. Removing a core app from the home screen does not remove it from the device. Installing it from the App Store restores that link. That means updates still need to be a part of a system update.

In iOS 10, reinstalling the News or Calculator apps was instant. In iOS 11, the App Store list sizes for these apps, and reinstalling them takes a few seconds (on my phone and connection).

I haven’t measured data usage, but I suspect this means that removing Calculator’s icon actually removes its code from the system. If that is true, it is potentially upgradeable independent of the iOS system, at least from a technical perspective.

I suspect Apple’s QA and release processes cannot take advantage of this, though.

Post reply on HN