A screenshot at the beginning of https://stackoverflow.com/questions/37809848/can-we-use-some...
However IMHO it's a big usability regression from the old time picker widget, which was a number pad to enter the four digits a time is made of. I know the time I want to set and instead of typing it straight away I have to look for numbers on a dial. It takes longer.
Design teams are losing their way. Too much eye candy is making them blind to efficiency, pun intended.
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?)
Who puts seconds as an input for setting their morning alarm? MAD!
The Android clock app silently corrects 73 minutes to 1 hour 13 minutes.
So for 1:13:45 (hh:mm:ss) you can input "7345" on the keypad and It. Just. Works.
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.
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.
It’s a damn shame. I loved the Apple of old.
Are they cheaper? I don't understand the point of them in the cases where they're literally just replacing a real button. The worst is when they don't even indicate clearly where the buttons actually are.
Not generally, by neither are they more expensive generally.
However, there's a large section of consumers that see that sort of thing and somehow assume it means the product is of higher quality, or that's what comes up in the marketing meetings I've had to sit through whilst advocating for mechanical switches.
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 feedback of physical buttons.
The problem is that adding that kind of feedback costs money. Even if it's just a few pennies per device, most manufacturers won't do it for consumer devices. That kind of penny pinching is the reason I avoid consumer grade products if at all feasible.
Capacitive buttons have some distinct advantages too, primarily being waterproof and nearly infinite durability. A lot of UI issues like OPs stove are likely poor software, there is no real reason why a capacitive button would need a 700 ms pause between actions. Now, the lack of tactile feedback is a more fundamental problem sometimes, but capacitive buttons can be great when implemented well.
The problem described occurs before the oven even has time to heat up at all much less heat the input panel to 120F.
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 differences to shrink.
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.
That interface was genius. These days I sob and cry every time I have to figure out how to use an unfamiliar microwave.
As for regular oven tops, we spent some time finding an induction model with physical buttons. It's wonderful and I enjoy using it every day. It's very tactile. Throw a kettle on and slam it to "P" in 30 milliseconds, aah I love it.
Both are on the fly adjustable, both power and time. I find it really good design.
They don't work any better or worse with wet hands, so I have to figure they kind of sacrificed overall usability in exchange for capacitive touch working with wet fingers.
My lab placed fancy touch-screens in the place of the light switches. Now turning the lights on or off takes at least 15 seconds but we get to pretend to be luxurious :(
You don't make sales based on how much people like using it, you make sales based on how attractive it appears while on display.
My favorite example comes from the aptly named "Asshole Design" subreddit: https://www.reddit.com/r/assholedesign/comments/78b0di/apple...
What should I believe? /s
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.
But with the added layer of animations post interaction it can feel really cumbersome and disconnected. Imagine if each key on the keyboard had an associated delay and animation and you can see how it might impede a user's progress in other scenarios as well.
I think it is a case of the rule of cool winning during design and development, and then because the devices and sites we use become daily use items we end up growing tired of the mounting small inconveniences.
Imagine if every time you opened your wallet you had to wait a few seconds for it to slide open from a button press, rather than it just opening as you manipulate it.
You lose a slight bit of control over the situation and it's timliness and that adds up over the course of long time use until eventually you throw out the wallet and buy a more rudimentary one that "just opens for crying out loud".
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 an extra beat to register, so you have to turn on the stove, pause 700ms, turn on the burner, pause another 500ms or so, then turn the burner up to max to boil your kettle.
I'm totally used to it by now, and never get it wrong any more, but it still bugs me every single fucking morning.