LifeQuest treats the countdown as a display, while the server measures the focus session. Full XP depends on elapsed server time, so changing a phone clock or watching a local timer hit zero cannot decide the result.
A timer can look finished before the work is measured
Consider Elian, an illustrative composite, at 8:42 p.m. in a crowded university library in Lisbon. His headphones are beside a half-full bottle of water, and a focus quest is open on his phone. He has an assignment draft due the next morning, with two paragraphs still held together by notes in the margins.
He starts the session, puts the phone face down, and works.
Halfway through, the library Wi-Fi drops. Elian opens his phone to check the time, then remembers he has a message to answer. A few minutes pass before he returns to the document. The visible countdown is still there when the connection comes back, but it has to catch up. Then it reaches zero sooner than he expected.
That creates a real problem. If the number on the screen were the authority, Elian could be credited for a session the product cannot reliably measure, or lose credit after doing the work because his device displayed the wrong remaining time. His assignment is still unfinished, and the full-XP result is uncertain until the session is checked against the time LifeQuest recorded when it began.
The screen can only show its best current estimate. The server-issued start time is the record that matters.
The server start time gives the countdown something solid to count from
When a LifeQuest focus session begins, the server records when it started. The app derives the visible countdown from that server-issued start time instead of trusting a counter that runs only on the phone.
That distinction matters because phones are interrupted constantly. Someone locks the screen. A battery-saving mode slows background activity. The app is closed accidentally. A device clock is changed. A connection drops in the middle of a study block.
A device-side counter can be useful as a visual aid, but it is a weak source of evidence. It only knows what happened while that particular app was able to run and report time. LifeQuest uses the server’s clock to determine elapsed time when the session finishes.
The display still has a job. It helps you see where you are in the session and decide whether to keep going. It can also show an honest away notice after you leave the app: time continued to pass, and nothing was paused in the background.
That is more useful than a comforting fiction. A paused-looking countdown could invite someone to believe they preserved a focus session while answering messages, commuting, or watching videos. A server-timed session gives the same rule to every device: the clock kept moving.
Full XP needs evidence that fits the quest
LifeQuest offers different completion methods because different quests leave different kinds of evidence. A coding quest can use a qualifying GitHub push. A physical task may be suitable for a photo review. A task with no practical objective proof can still be completed honestly through self-report for half XP.
Focus work needs its own kind of evidence: time measured from a source outside the device that displays it.
That does not prove every second was perfectly concentrated. No timer can see whether Elian reread a sentence three times, stared out the window, or made real progress on the hard part. It does establish that a focus session began at a known time and lasted long enough under the server’s measurement to qualify for full XP.
The boundary is deliberate. Form coaching, for example, can give feedback on a short exercise or craft clip, but that feedback does not award XP. Each tool should make the claim it can honestly support. The same principle explains why a focus countdown is treated as a display rather than a verdict.
For another edge case, see What Happens When Your Focus Countdown Ends Before the Server Clock?.
The honest result is more motivating than a convenient one
When Elian finishes his draft, he returns to the session instead of relying on the number that flashed on his phone earlier. The server evaluates the elapsed time. If the session qualifies, he receives full XP. If it does not, the result remains clear rather than being hidden behind a timer that happened to look complete.
The next evening, he starts again with a different expectation. He can use the countdown to stay oriented, put the phone down, and come back when the work is done. He does not have to babysit a device-side timer to protect the record.
That is the practical value of separating display from measurement. The countdown helps you focus. The server time keeps the XP claim grounded.
Comments
No comments yet.