A 25-minute LifeQuest focus sprint lives in the server record: the server issues the start time, then measures elapsed time when the session finishes. The countdown on a phone can help someone pace themselves, but full XP depends on server time rather than a timer that only ran on one device.
The countdown reached zero, but Lena could not be sure
At 8:34 p.m., Lena was at a kitchen table in Glasgow with a statistics workbook open beside a mug gone cold. Her quiz was due before class the next morning, and she had already spent most of the evening switching between notes, messages, and the same three unanswered problems.
She created a 25-minute study quest and started a focus session. LifeQuest recorded the start with the server’s time. On her screen, the countdown began to move.
Then her phone battery slipped into the red.
Lena plugged it in, but the cable sat loose in the socket. The screen went dark halfway through a worked example. When it came back, she had no clean way to trust what the device timer had displayed while the phone slept. If the session could rely on a local countdown alone, a pause, a clock change, or an interrupted app could turn the record into a guess.
Her streak was not the real pressure. The real risk was spending another half hour convincing herself she had studied when she had mostly fought with a screen, then facing the quiz with the same blank space around hypothesis testing.
She kept working from the workbook. The phone stayed facedown.
The start time belongs to the session record
A focus session begins with a request to the server. The server returns a session and a `started_at` time, which becomes the reference point for elapsed work.
That distinction matters because phones are built to change state. An app can move into the background. A device can lock. A person can cross time zones, change the clock, or lose a connection for a stretch. A visible countdown still has value as a pacing tool, but it cannot carry the weight of a full XP award by itself.
LifeQuest treats the screen countdown as cosmetic. It derives its display from the server issued start time, so it can show where the session stands. The server remains the source of the elapsed time that matters at completion.
This is a small design choice with a practical effect: the record answers a narrower, more useful question. How much time had passed on the session the server started? It does not claim to observe every second of a person’s attention or prove perfect concentration. A timer cannot honestly make that promise.
For a broader look at the same edge case, see What Happens When Your Focus Countdown Ends Before the Server Clock?.
Finishing checks the clock that started the sprint
When Lena returned to the app, the countdown had reached its end. She finished the session, and the server compared that finish request with the time it had issued at the start.
Enough elapsed server time had passed, so the quest earned full XP.
The important part is the chain of custody. One system creates the session. That same system records its start. That system calculates the elapsed time when the person finishes. The phone displays the session, but it does not get to rewrite the clock behind it.
LifeQuest also keeps the behavior legible when someone leaves the app. A focus session does not pretend to pause because the screen is gone. When the person returns, the app can state that they were away for a period and that nothing paused. That can feel stricter than a forgiving timer, yet it removes a more frustrating outcome: a person believing they preserved a session when the underlying record says otherwise.
A session that is abandoned does not remain active forever. It clears after 12 hours. That limit gives the system a way to close an unfinished record without turning it into a completion.
Full XP marks a stronger record, not a perfect study session
The next morning, Lena opened her workbook before class and found the page where she had finally written out the test steps. The quest had full XP because the focus session met the server timed requirement. Her understanding still came from doing the problems.
That separation is useful. XP can reflect the strength of the evidence attached to a quest without pretending that a verified session measured every outcome. A photo review, a GitHub push, a focus session, and an honest self report each answer different questions. LifeQuest lets people choose the method that genuinely fits the work.
For a study sprint, server timed focus gives a clear record of elapsed time. For work where timing does not capture the result, another method may fit better. The point is to make the evidence match the quest rather than force every kind of progress through one completion checkbox.
Before starting your next 25 minutes, make the quest specific enough that the finish means something: one problem set, one reading section, one outline, one practice block. Then let the session record the time while you keep your attention on the work in front of you.
Comments
No comments yet.