Hundredths, lap splits and full screen. It keeps time in a background tab and through a sleeping laptop, which is where most of them go wrong.
0 seconds elapsed
Counting down instead? Set a timer.
The obvious way to build one is to add a few milliseconds to a number on every tick. It works perfectly on a visible tab and fails everywhere else: browsers throttle intervals in the background to save battery, and stop them altogether when a laptop sleeps. A stopwatch left running through lunch comes back minutes short and never tells you.
This one records the instant you pressed start and subtracts it from now. Nothing is counted, so nothing can be missed — the tab being asleep just means nobody was looking.
Laps are the point: each split lands next to the last one, so a set that is drifting is visible while you can still do something about it.
Hundredths, a big readable clock, and full screen for a phone propped at the end of a lane.
The honest cure for a bad estimate. Time the task once and the guess stops being a guess.
When you need elapsed time rather than a deadline, and want to mark the moments along the way.
Run it through a rehearsal, lap each section, and see which part is eating the talk.
Elapsed time everyone can see, without an app or a phone passed around.
The number on the clock is gone the moment you close the tab, and with it the only evidence of how long that thing really took. Which is a shame, because that is the number that fixes estimates.
EvyOS runs the same clock attached to a task or a skill, so the time lands on the record instead of evaporating. After a month you can answer “how long does this actually take me” with data rather than a feeling.
EvyOS keeps the minutes against the task, the skill and the habit they belonged to.
Start for free →