Full XP from a LifeQuest focus session arrives after the server records enough elapsed time, not when you press Start. That delay makes the reward reflect time you actually gave the quest.
The clock starts before the reward does
On 6 May 1954, Roger Bannister stood at Iffley Road Track in Oxford with Chris Brasher and Chris Chataway set to pace him. A four-minute mile had never been officially recorded. The race still had to happen, and Bannister still had to cross the line with a qualifying time.
He finished in 3 minutes 59.4 seconds.
The moment matters because nobody could award that record when Bannister put on his spikes or stepped onto the track. His preparation was real, but the result depended on what happened across the full distance. Bannister recounts the attempt in The Four-Minute Mile: the standard became meaningful only when the clock stopped.
A focus quest has the same basic shape. Opening the timer is a commitment. It is not yet evidence of focused work.
Setup is easy, elapsed time is the work
It takes seconds to create a study quest, choose a task, and tap Start. The difficult part begins after that screen changes: staying with the reading, code, notes, or practice when there is no immediate victory screen waiting to flatter you.
LifeQuest uses server-timed focus sessions for that reason. The visible countdown can help you orient yourself, but the server records the session’s elapsed time. Full XP arrives when that record shows enough time has passed.
That distinction protects the meaning of a verified reward. A device-side counter can look finished after a phone clock changes, an app pauses, or someone returns later. A server-timed session ties the outcome to the time the product recorded.
The delay also creates a useful bit of friction. You cannot turn the intention to focus into full XP with a quick tap. You have to let the session run and do the work you planned to do.
A late reward can make progress feel more honest
Immediate feedback has its place. Starting a session should feel clear. Seeing time accumulate can make a large assignment less intimidating. But a reward that appears before the underlying action has had time to happen trains the wrong association.
Bannister’s record did not come from declaring that he intended to run fast. It came from a measured result after a hard interval with an uncertain outcome. LifeQuest applies a much smaller, everyday version of that idea. Full XP belongs at the end of the focus period, once the evidence supports it.
That does not mean every useful effort needs a timer. Some quests are hard to prove objectively. LifeQuest keeps honest self-report available for half XP, so a real effort can still move a quest forward without pretending there is stronger proof than there is.
For a coding quest, a qualifying public GitHub push can support full XP. For a suitable task with visible results, an in-app photo can be reviewed for plausibility. The point is to choose the verification method that fits the work, rather than forcing every quest through one checkbox.
For more on why the displayed countdown and the recorded time serve different jobs, see Server Time vs Phone Time.
Use the wait to make a smaller promise
A server-timed focus session works best when the quest is concrete enough to begin without negotiation. “Study statistics” leaves room for avoidance. “Work through problems 1 to 6 and mark the one that breaks your method” gives you somewhere to start.
Before tapping Start, decide what will be on your desk, what distraction you will put away, and what a useful stopping point looks like. Then leave the phone alone if you can. The session does not need your screen to be exciting. It needs your attention to have somewhere to go.
If you come back after leaving the app, LifeQuest can show that time passed rather than pretending the work paused. That honesty may feel less comforting than a frozen timer, but it gives you a clearer choice: continue with what remains, use a different verification method when it genuinely fits, or take the half-XP self-report for work you completed without objective proof.
Bannister’s stopwatch could only report the time he had run. A focus session should follow the same rule. Start the clock, do the next piece of work, and let the reward wait for the evidence.
Comments
No comments yet.