Kabaka

The main installation method young people run into nowadays is the Steam or phone app store experience: search for the thing in the store, click “install,” wait briefly, click “open.” Installing a program from a website or physical media is not as common an activity as it used to be — other than installing Steam itself or similar, for example, which is a quickly forgotten inconvenience.

I once lived in a rental that had the dispenser mounted on the wall right beside the tank. Twisting and contorting to reach it was a painful and annoying experience. No clue what the owners were thinking. I eventually bought a freestanding holder to put somewhere more ergonomic.

Could be. I have no idea how it’s implemented in this specific device/app. It might immediately resume tracking the duration when it boots (or you opened the app before correcting the time) and cancels the stopwatch when it finds the start time is seemingly in the future. If I still had my iPod Touch, I’d try to find out — decent nerd sniping opportunity.

They’re using what’s called “feature flags” or “feature toggles.” It lets the software team work faster and safer: ship inactive code updates to clients, then gradually, remotely turn them on to make sure the changes work and be able to quickly go back without requiring another app update if something goes wrong.

They’re quite powerful and effective if used correctly. Very standard practice these days.

https://en.wikipedia.org/wiki/Feature_toggle

It just has to record the start time, then show the duration between the current clock time and the saved start time. As long as the clock can still sync or be manually set after being charged, there’s no reason it shouldn’t work.