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

161–170 of 501 posts

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

#161

Post by npgatech »

jljljl wrote: post #146
kalleboo wrote: post #125

Earlier quoted context omitted.

I still find a number pad to be the fastest. Why am I spinning something around and trying to position it right when I just just press three buttons 9-3-0?

For alarms and clock times, my guess is data validation. The app could correct or block invalid time entries (e.g., accidentally hitting 2500), or it could restrict the entry set. It also means the number will be in the correct format. your example, 930, could mean many things (930 seconds? 9:30am or 9:30 pm?)

If all inputs are in hh:mm format, then there is no ambiguity of 930 as 9:30 am/pm. There could be a toggle for AM/PM.

Who puts seconds as an input for setting their morning alarm? MAD!

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

#162

Post by flukus »

scrollaway wrote: post #139
dingo_bat wrote: post #85

Earlier quoted context omitted.

I was very annoyed with this. Then I chanced to use my wife's laptop. And Win10 was absolutely flying on it. No keystroke misses, no launch lag. I have since concluded that Win10 is impossible to run properly on a spinning drive. You must have an SSD. I once r4ead that the reason Vista was such an utter dog on old machines was because Microsoft dev machines were too highly spec'd. I guess the same has happened with W…

Can confirm. I run W10 on my gaming machine, which still has a spinning drive. I cannot believe how frustrated I get every single time I use it. An operation as simple as opening the Windows menu and searching for an app can take up to 20 seconds. What a waste of time.

I think there's some network access in there too. When I was tethering to my phone on public transport (where the connection drops out periodically) I've had the windows menu freeze for a minute (or whatever the timeout is).

I moved back to linux for a computer where basic things like this would work reliably. A good move for the most part, but for some reason the calculator in gnome doesn't do anything when you hit the '=' key, I have to reach for the mouse. Seems like no one can make a simple calculator app anymore.

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

#163

Post by dogecoinbase »

npgatech wrote: post #161
jljljl wrote: post #146

Earlier quoted context omitted.

For alarms and clock times, my guess is data validation. The app could correct or block invalid time entries (e.g., accidentally hitting 2500), or it could restrict the entry set. It also means the number will be in the correct format. your example, 930, could mean many things (930 seconds? 9:30am or 9:30 pm?)

If all inputs are in hh:mm format, then there is no ambiguity of 930 as 9:30 am/pm. There could be a toggle for AM/PM. Who puts seconds as an input for setting their morning alarm? MAD!

What's the unambiguous setting of 73:45 in hh:mm format?

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

#164

Post by dragonwriter »

teej wrote: post #55
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 hate to be this guy but Steve Jobs would have fucking eviscerated the team that produced this. The first time he used the calculator and got 24 instead of 6, he would’ve walked straight to whoever wrote the software and gotten it fixed. There’s no one at Apple who can do that anymore.

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

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

#165

Post by learc83 »

shakna wrote: post #143
learc83 wrote: post #117

Earlier quoted context omitted.

They are definitely cheaper most of the time. They are often just a trace on a PCB. Product designers hate mechanical switches because they are almost always the first thing to wear out. Including a switch robust enough to last as long as the rest of the product is generally too expensive for consumer electronics. Capacitive buttons can be made much better with some kind of instant feedback to replace the tactile fee…

Our supplier delivers capacitive switches at about $80 per thousand, resistive at $75 per thousand, and tactile at $95 per thousand. However resistive needs fine-tuning, and really shouldn't be used in dusty or hot environments. Which adds design time and shielding costs. In our internal research, they end up costing about equal. But we are small, so it might change at a larger scale, though I'd expect those differen…

You can include capacitive inputs on a PCB in many cases for essentially zero cost.

You also don't need to engineer attachment points into the product chassis, and assembly is easier.

In addition, they can improve the lifespan of the product because they don't wear out nearly as fast, and they don't provide ingress for dust and water.

Capacitive inputs have many downsides, but at scale they are certainly cheaper on average.

In your particular case they may not be cheaper due to other design considerations.

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

#166

Post by hedora »

11thEarlOfMar wrote: post #3

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…

It takes 14 sec to open maps and load a screen of tiles, 4 sec to open messenger on a my 6 plus. I’d love to see timings for this on the newer models.

Also, I swear the rear-facing camera has lower color saturation and higher sensoe noise after the upgrade. I’d love to see A-B camera tests for iOS 10 and 11 on old hardware.

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

#167

Post by hedora »

prawn wrote: post #141
sogen wrote: post #2

As the thread says, I can confirm this bug, the answer: 24 :( iOS 11 must be the buggiest piece of s I've ever tried. Stuck animations, apps that take ages to load, widgets not working, more stuck animations, text overlapping everywhere. Related: Flat design was supposed to make things leaner... EDIT: Worst of all, every single operation is wrong: 7+8+9 = 96 4+5+6 = 60

I'm with you. Updated my 6+ and everything is tragically slow. 4-5 seconds just to get the Settings or Messages apps to open. Typing anything is unbearable - every time, the first word capitalises and then botches everything from then on. Basic functions within apps or opening the camera take so long as to render them near-useless. I have switched off any animations and performance tweaks that I thought might help, b…

YEp. Thought it was me.

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

#168

Post by zorpner »

stickfigure wrote: post #84
Nition wrote: post #59

Earlier quoted context omitted.

It definitely looks more sort of futuristic, I have to concede that. Too bad we have to actually use these devices instead of just admiring them in the shop. Thank you for advocating mechanical buttons.

In the 70s my family bought a microwave oven. It had one knob with a dial, which you would turn clockwise to the number of minutes. The microwave would immediately start (if closed, of course) and count down. The gradations had a logarithmic scale. If you wanted to stop early, you turned the knob counterclockwise to zero. That interface was genius. These days I sob and cry every time I have to figure out how to use a…

If you're ever looking for a toaster, check out Dualit (the classic, not whatever cheap plastic one they peddle to price-segment). I use mine every day and interface-wise, it's pretty much the most satisfying moment of every day.

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

#169

Post by balls187 »

kalleboo wrote: post #133
11thEarlOfMar wrote: post #3

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…

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!).

Interesting. Bored before bed so ran a quick test using my iphone7 and Ios 11.x, Google's stopwatch.

The time from wake to photo was ~2seconds (using the lockscreen short cut).

The time from wake to home screen photo app to photo was ~5 seconds.

*

I had to start the timer myself then go back to using the phone so I believe I could cut ~500ms.

Since I have Live Photo enabled, the 2-second shots actually have a few frames that are sub 2 seconds.

Going to the homescreen was accidental. In each attempt, I attempted to use the lock-screen camera shortcut.

As a whole, the experience using the iphone is too unpredictable to be reliable for quick reaction shots (< 3 seconds). A number of times I either: bypassed the lock screen, didnt get passed the lock screen, unlocked my phone to a different app, and on one occasion, the camera app paused for a few seconds before focusing.

Post reply on HN