LifeQuest awards full XP for a focus quest from the time recorded by its server at the start and finish of the session. A phone can display a useful countdown, but the server record is what establishes whether the required time elapsed.
A focus timer feels simple until the reward depends on it. If an app lets the device decide when a session began, ended, paused, or resumed, the evidence comes from the same screen asking for credit. LifeQuest keeps the clock that awards full XP outside that screen.
At 9:37 p.m., Mara sits at a scratched kitchen table in Manchester with her history notes open beside a cold mug of tea. Her 25-minute focus quest is for the essay due the next morning. She starts the session, then a message lights up her phone. She taps it, gets pulled into a group chat, and looks back up after the room has gone quiet.
The countdown on her phone says she is nearly done. Her essay still has a paragraph missing.
If that timer awarded itself full XP, Mara could receive credit for a session the app has no reliable way to place in time. The bad ending is small but real: she starts believing a rank, streak, or badge reflects work she did not complete, and the system loses the meaning that made the reward worth earning.
The record starts before the work begins
When Mara starts a LifeQuest focus session, the server issues the start time. When she finishes, the server checks the finish time against that original record and calculates elapsed time there.
That design gives the session one shared source of timing. The phone still shows a countdown because people need to see where they are. But the countdown is a view of the session, not the judge of it.
This matters most when real life interrupts. A phone can lock, an app can move to the background, or a person can walk away from the desk. LifeQuest tells the user when they were away and does not pretend the session paused. The elapsed time continues according to the server record.
That can feel stricter than a timer that quietly waits for someone to come back. It is also clearer. You know what earned full XP, what did not, and why.
For a 25-minute quest, 24:59 remains short of the requirement. That last second is not a trick or a punishment. It preserves a simple agreement: full XP marks the focus duration the quest asked for. The 24:59 Focus Session, and What It Costs Your Quest XP explores that boundary in more detail.
Full XP needs evidence that fits the task
LifeQuest uses different completion methods because different quests produce different kinds of evidence. A coding quest can use a qualifying GitHub push made after the quest was created. A physical or visual result may fit an in-app camera photo submitted for AI plausibility review. Focus work has a different shape: the useful evidence is a timed session with a server-issued start and finish.
The system does not claim any method is fraud-proof. It gives each method a role that matches what it can genuinely show.
A focus session can establish how much server-measured time elapsed between start and finish. It cannot prove every thought stayed on the task. A photo review can assess whether submitted proof looks plausible. It cannot turn form coaching into completion evidence. Keeping those boundaries visible helps XP mean something without asking the product to promise more than it can know.
When objective proof does not fit, LifeQuest still allows honest self-report for half XP. That route matters. Someone may have done meaningful work that leaves no photo, no GitHub event, and no suitable timer record. Half XP recognizes the effort while reserving full XP for a completion method with stronger evidence.
The timer should make the rule visible
Good rules are easiest to follow when the product shows them before the result arrives. A focus screen should tell you that the server measures elapsed time, that leaving the app does not pause the session, and that an abandoned session eventually clears. There is no hidden device-side counter deciding whether a reward appears.
That clarity lowers a different kind of friction: the argument with yourself after the session. Did the timer pause? Did it count the time spent answering a call? Did the app lose track when the screen locked? A single server record gives the answer the same way every time.
Mara returns to the table, sees the away-time note, and starts again with the group chat muted. This time she finishes the paragraph before ending the session. The next morning, her notes include a completed quest with full XP because the recorded session met the requirement.
Her streak has value because it reflects a rule she could see while she was earning it.
Progress feels better when the credit is earned
Ranks, badges, and skill trees work because they turn repeated effort into something visible. Their value fades when every completion uses the same generic checkbox. Evidence-weighted progress makes the distinction clear: a self-report is still progress, while verified full XP marks a quest completed through a method suited to that quest.
For focus work, the practical habit is simple. Start the session when you are ready to begin. Treat the displayed countdown as a guide. Return to the task if you step away. Finish only when the work block has actually run its course.
The reward is not the clock itself. It is the confidence that, when Mara looks at her Mind rank later, the full-XP session behind it has a record she can understand.
Comments
No comments yet.