Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

reddit.com

Post reply on HN
Print view View original

31–40 of 501 posts

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

#31

Post by trumpownsyou420 »

epistasis wrote: post #21

Almost all of the animations on iOS are about 2x-3x as long as they should be. First off, they look terrible, the slooooooow change from one thing to another. Secondly, they severely impede usability because you have to wait wait wait for 1000ms here, 1000ms there, and another 1000ms there after every action. It's enough to make me want to give up privacy and switch to Android. Soooo pissed at slow animations. 500ms,…

lol, you think you have privacy on either apple or android? you just made my night LOL.

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

#33

Post by matt4077 »

veidr wrote: post #6

"Jony wants you to take time and appreciate the simplicity of the slowly dimming animations. Or we’re just using it wrong." Apple has lots of issues like this, in iOS and macOS, where they choose visual appeal over functionality, or where animation impedes usability. This is a pretty sad bug, though. My (very expensive, "high-end") Japanese induction stove has a similar issue. Its capacitive touch controls take just…

I don't feel like Apple is overdoing animations. They are mostly only used where they make sense, such as showing you where something disappears to, allowing you to find it it later.

There are also options to reduce animations in both macOS and iOS, although I'm not sure if the calculator responds to that.

But you're absolutely right about these non-responsive 2D stove controls. I have o multiple occasions given up on trying to use stoves at friends' places because I was actually unable to turn them on. The worst sin is obviously that there's no affordability indicating a touch has been registered. But on top of that, they somehow tried to sixth-normal-form these buttons. So you have one button rotating through functions (up, down, off, fire fire fire!), and one other button to choose the burner. Or something like that.

I really wouldn't know anything to make them worse. Maybe Clippy.

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

#34

Post by plainOldText »

I absolutely abhor the new Calculator app on the iOS 11. The old interface was way more elegant, the buttons were squares (and had a larger touch area), and it worked even when you typed fast.

Sometimes I wonder why individuals working for these multibillion dollar companies, who affect the lives of millions of people, decide to change things for the worse. Imagine having spent all those hours overhauling the calculator app, on I don't know, fixing things that actually are broken.

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

#35

Post by colanderman »

epistasis wrote: post #21

Almost all of the animations on iOS are about 2x-3x as long as they should be. First off, they look terrible, the slooooooow change from one thing to another. Secondly, they severely impede usability because you have to wait wait wait for 1000ms here, 1000ms there, and another 1000ms there after every action. It's enough to make me want to give up privacy and switch to Android. Soooo pissed at slow animations. 500ms,…

> It's enough to make me want to give up privacy and switch to Android.

It's sadly no better on the Android side of the fence either. How many times I've had to wait for the keyboard app to decide to load…

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

#36

Post by deckarep »

tedunangst wrote: post #29
deckarep wrote: post #23

Earlier quoted context omitted.

Hmmm it could be but who knows? Almost there entire eco-system is closed off so ¯\_(ツ)_/¯ I guess we’re at the mercy of an update so we can get back to calculating things with at least a few order of magnitudes of accuracy...

It's not hard to know what it is. Watch the screen. You can see the animation.

The animation doesn’t mean anything. You should be able to have many animations happening in parallel and their completions should not block keyboard events from being handled...

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

#37

Post by bowmessage »

sogen wrote: post #19
deckarep wrote: post #10

Earlier quoted context omitted.

Ugh, can also confirm this happens on my phone. This feels like more of UI event/timing issue than a logic issue. Also, if this turns out to be a performance based bug that will be pretty frustrating considering Apple is always bragging about how they build the hardware, the software, have grand-central dispatch, have Metal and have multi-core custom built CPUs...yada, yada. It’s not just that number sequence...it’s…

btw, has anyone has tried deleting a note in Reminders?

yes it's so broken and if you delete a selected event the app crashes.

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

#38

Post by IncRnd »

The software quality of Apple products that I use has fallen significantly in the past few years.

Updates slow down my phone, every single update, as well as introducing errors like this or where I double tap home to change applications and instead get a blur on the screen. Desktop OS updates have incrementally slowed down the computers, notably since Mavericks (and even earlier), so ever-slower desktops are actually expected by now.

I've used iOS products for years, refusing for example to use Android, but the issues I am encountering on the phone have become ridiculous. It may be time for an old school flip phone with a week long battery.

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

#39

Post by inopinatus »

jasonlotito wrote: post #14

This type of thing isn't new. Even on the latest hardware with up to date software. Countless times I've searched for an app, seen it popup, stop searching, and go to tap and something else comes up and I've now tapped on that.

That problem is frustrating but not unique to Apple. Many asynchronous search interfaces break usability in this fashion. I have never understood how any front-end developer can tolerate this behaviour.
Post reply on HN