> Why are you frequently switching away from the timer after setting it but before starting it?Example: I boil water in a kettle for tea. I set the timer to the correct steeping time. I open the top of the kettle to let the water cool off for a bit for it to be appropriate for the type of tea I'm making. Before the water gets to the right temperature, I get an SMS or someone calls me. I then get back to the app, but the timer value is wrong.
But really the main failure mode is the lock screen, not switching to another app. I set the timer value to what I want and leave the phone on a tabletop until the time comes to start the timer. But the timer app behaves like an attention-seeking child which punishes me if I don't give it constant attention. So you can replace getting an SMS/getting called in the above with just putting the phone down until it's needed. It's nice to separate those two steps, when you want to be more precise.
Scenario 2: I want to make soft-boiled eggs, so I set the timer value to 3 minutes and put the phone down until water starts boiling. I lower the temperature for the water to simmer. And start the timer.
> This was willfully done this way, probably due to another customer's Feedback submission.
I find it hard to believe that someone would want their timer to reset to a value they used the last time they pressed the Start button, instead of staying at whatever value they've just selected. The previous value is likely to be completely unrelated to what they're doing the next time. Previously you were cooking eggs, now you're making tea, later you're frying steaks, ...
I think tpmx's suggestion that it may be a bug introduced in a SwiftUI rewrite more likely, especially given
Jtsummers's observation that all that's needed is switching to another view.
