Focus time can earn XP in several life RPGs, but the important comparison is how the app decides that a session deserves full credit. LifeQuest uses elapsed server time for focus-session XP, then offers photo evidence or a qualifying GitHub push when those are a better match for the quest.
Compare the proof behind the timer
A focus timer can make a work block feel more rewarding. You start a quest, work for the planned duration, and watch XP move from an abstract promise to visible progress in a skill tree, streak, and rank ladder.
The tradeoff is simple: a device-side timer only knows what the device reports. LifeQuest starts a focus session through the server and calculates completion from the server-issued start time. The countdown you see is there to help you pace yourself, while the XP decision comes from elapsed server time.
That matters when you leave the app. LifeQuest does not present an away period as a paused session. If you step away, the focus screen tells you how long you were gone, and the session continues against the same server clock. There is also only one running focus session at a time. An abandoned session clears after 12 hours, so it cannot sit open indefinitely.
This setup suits work where time itself is meaningful evidence:
- Reading a chapter for a Mind quest.
- Writing a first draft for a Craft quest.
- Practicing a language lesson.
- Working through a focused study block before an exam.
Set the quest before you begin. Start the session only when you are ready to work. Then finish it when the server-timed requirement has been met. A session that falls short does not earn full XP simply because the timer was opened.
For a closer look at how that plays out during a reading task, see LifeQuest Focus Sessions: How Theo Earned Full XP by Returning to Chapter Four.
Match the proof method to the actual work
Focus time is useful evidence for focused effort. It is a poor fit for every goal.
If your quest is “complete a 30-minute study block,” elapsed time makes sense. If your quest is “finish a painting,” a photo can better show the result. If your quest is “push the feature branch,” a qualifying GitHub push provides a more direct signal than leaving a timer running beside your editor.
LifeQuest gives you the methods that genuinely apply to a quest instead of treating every completion as the same checkbox:
- A self-report is always available and earns half XP when objective proof is impractical.
- An in-app camera photo can earn full XP after AI plausibility review accepts the evidence.
- A server-timed focus session can earn full XP from elapsed server time.
- A qualifying GitHub push can earn full XP for a Craft quest after the quest was created.
Each method has conditions. Photo proof must be captured in the app, rather than selected from a gallery, and a rejected photo does not consume a photo-review allowance. AI review checks plausibility; it does not claim to establish certainty. GitHub verification requires a linked GitHub username and a public qualifying push made after the coding quest exists. GitHub events can take up to five minutes to appear in the backend cache, so a push made seconds ago may need a little time before it can verify.
That timing rule is worth planning around. Create the coding quest first, then make the push. A push that predates the quest cannot earn full XP for it. What Happens When You Push Before Creating a Craft Quest? walks through that limitation in detail.
Keep coaching feedback separate from completion
A 60-second form recording can also receive asynchronous AI coaching feedback, including a summary, cues, and concerns. That feature serves a different purpose from verification.
Use form coaching when you want feedback on an exercise or craft movement. Use a focus session when you need to document focused time. Use a photo when the finished result is visible. The coaching response never becomes XP proof, so helpful feedback cannot be mistaken for evidence that the quest happened.
This separation is a practical guardrail. You can ask for feedback on a squat, a drawing stroke, or another recorded movement while keeping the quest pending until you choose a valid completion method. It also keeps the AI’s role clear: feedback can help you reflect on form, while proof methods determine how much XP a quest earns.
Choose your verification plan before starting
Before you create a quest, write down the outcome and the proof you can realistically provide. “Study chemistry for 25 minutes” points to a focus session. “Build the first working version of a login form” may point to a GitHub push. “Complete the sketchbook page” may point to a photo.
If no full-XP method fits, choose self-report honestly and take half XP. Progress still moves forward, and the difference between half and full XP remains visible instead of being hidden behind one generic completion flow.
Start with one quest today. Create it before the work begins, pick the evidence that fits the task, and reserve the timer for work where elapsed focused time is the proof you actually want to count.
Comments
No comments yet.