I think it's a valid complaint. We used to be able to do that prior to iOS 18. Have you never wanted to repeatedly add or multiply the same number? Many people do and got into the habit of doing that. Heck, most real calculators operate that way.Getting a little tired of these posts about an app being “flawed” or “broken” because it doesn’t behave the way YOU want it to.
www.apple.com/feedback
Valid complaint - sure.I think it's a valid complaint. We used to be able to do that prior to iOS 18. Have you never wanted to repeatedly add or multiply the same number? Many people do and got into the habit of doing that. Heck, most real calculators operate that way.
Another thing they removed is the swipe to delete a digit gesture...another habit that's hard to break.
Their calculator doesn't work like every calculator I've used in the last 40 years worked, and you're giving me grief for saying it's a flaw? Care to enlighten us as to how this is actually an improvement?Getting a little tired of these posts about an app being “flawed” or “broken” because it doesn’t behave the way YOU want it to.
www.apple.com/feedback
Thank you for joining in with a sensible reply! It's a shame that there's always a few people that take even the most mild criticism of their favourite company personally. 🤦♂️I understand completely! Every hardware calculator performs that way, even the Windows and Linux calculators doing it. The iOS calculator also behaved normally, as most people are used to this behavior. To change such an essential part of entering data routine is - at least - a very bad mistake. Hopefully it is only an error, that will be corrected, but as i "enjoy" Apple software quality lately, this will be marketed as a "feature" - think different... 🤣
It’s behaved that way since the first iOS calculator was released.Getting a little tired of these posts about an app being “flawed” or “broken” because it doesn’t behave the way YOU want it to.
www.apple.com/feedback
Call it out as a design change you don't like. Nothing is broken.It’s behaved that way since the first iOS calculator was released.
This is a feature regression and it’s perfectly sensible for people to call it out.
Getting a little tired of these posts about an app not being flawed or broken just because a feature was removed that always existed before.Getting a little tired of these posts about an app being “flawed” or “broken” because it doesn’t behave the way YOU want it to.
www.apple.com/feedback
I wanted to do this today. I wanted to do 100 x 1.1 =======, basically, how would $100 appreciate at 10% interest compounding. Then I was like WTF, this used to work.What is the use case for this repeated addition or multiplication? I can't think of anything.
So every feature is inviolate? Talk about bloat... 😏Getting a little tired of these posts about an app not being flawed or broken just because a feature was removed that always existed before.
Yes. I'm annoyed that swipe to delete is gone. I keep trying to do that and it's just adding time and frustration. Why couldn't they keep both?I think it's a valid complaint. We used to be able to do that prior to iOS 18. Have you never wanted to repeatedly add or multiply the same number? Many people do and got into the habit of doing that. Heck, most real calculators operate that way.
Another thing they removed is the swipe to delete a digit gesture...another habit that's hard to break.
That's not how you calculate compounding interest.That’s 1.1^100. You’re not really going to press the equals key 100 times are you?
View attachment 2450377
It’s not. It’s 100 * 1.1^10That’s 1.1^100. You’re not really going to press the equals key 100 times are you?
View attachment 2450377
There are many. One example is compounding interest. Another one is scaling recipes in the kitchen. You want to divide every weight, every measurement by 3, for example:What is the use case for this repeated addition or multiplication? I can't think of anything.
Not a bug. "Negative change" per the article. Apple made a change, users didn't like it, so they changed it back.iOS 18.3 beta 2 corrects (@critics and thereby confirms) this BUG!