LifeQuest shows a countdown during a focus session, but the number on your screen does not decide whether you earn full XP. The server records when the session starts and calculates elapsed time when you finish, so locking your phone or leaving the screen does not pause the underlying clock.
In 1999, NASA engineers waited for the Mars Climate Orbiter to emerge from behind Mars and restore contact. The signal never returned.
The spacecraft had reached Mars after a journey of more than nine months. Yet calculations made on Earth had placed it on a dangerous path through the planet’s atmosphere. One engineering team had produced impulse data in pound-seconds, while another system expected newton-seconds.
The numbers moved through the software. The underlying units did not agree.
The measurement behind the display
NASA’s Mars Climate Orbiter Mishap Investigation Board documented the unit mismatch after the loss. The investigation found that navigation software supplied by Lockheed Martin produced data in English units while NASA’s navigation system expected metric units.
A value appearing on a screen can look precise. Precision alone does not make it authoritative. The calculation only means what its source, units, and rules say it means.
A focus timer has a smaller consequence, thankfully, but it raises the same design question: which clock determines the result?
LifeQuest answers that question before the session begins. Starting a focus quest creates a server-timed session and records its start time. The visible countdown helps you understand how much time remains. When you finish, the server calculates the elapsed time using its own record.
That distinction matters because a timer running entirely on your phone can become unreliable when the app moves into the background, the screen locks, or the operating system limits activity. A polished animation cannot prove how much time actually passed.
The server record can.
What happens when you leave the focus screen
Suppose you begin a 25-minute study quest, work through several pages, then lock your phone so the screen stops pulling your attention away. The displayed counter is no longer in front of you. The session continues according to the server-issued start time.
When you return, LifeQuest derives the countdown from that timestamp. If you were away, the app says so plainly. Nothing pretends the session paused.
Finish after the required elapsed time and the server can award full XP. Finish too early and the session does not qualify. The decision comes from recorded elapsed time rather than a device-side counter that might freeze, drift, or restart.
This design also places a clear limit on the claim. LifeQuest can verify that the timed session ran for the required duration. It cannot see your thoughts or guarantee that every second was productive. Evidence-weighted progress means choosing proof that fits the quest, then describing what that proof establishes without stretching it.
For a deeper look at the finish condition, read How Does a 25-Minute Focus Session Prove It Earned Full XP?. If you regularly lock your screen during a session, Server-Timed Focus Sessions: Why Lena’s Dead Battery Did Not Erase Her Progress explores the same design from another angle.
Why the countdown still belongs on the screen
A cosmetic countdown still has a real job. It tells you where you are in the session, gives the work a visible finish line, and reduces the temptation to keep checking the time elsewhere.
“Cosmetic” describes its authority, not its usefulness. The interface communicates progress. The server decides whether enough time elapsed for full XP.
Keeping those responsibilities separate also makes interruptions less confusing. Your phone may redraw the timer after sleep, reload the screen, or show how long you were away. None of those visual changes rewrite the server’s original start time.
The Mars Climate Orbiter investigation showed what can happen when systems appear to exchange the same measurement while following different rules. LifeQuest avoids that ambiguity by assigning one clock to the XP decision and treating the displayed countdown as a view of that record.
Start with a quest that time can honestly support
Use focus verification when elapsed time is meaningful evidence for the work: studying, writing, practicing, reading, or another task where sustained attention is part of the goal.
Choose another method when time proves little. A GitHub push may better fit a coding deliverable. A current camera photo may better fit a visible result. Self-report remains available for half XP when objective proof is impractical.
Then put the phone down. Let the countdown disappear if that helps you concentrate. The session’s source of truth is still running where a locked screen cannot rewrite it.
Comments
No comments yet.