A Lock Quality score looks precise. That makes it easy to give the number more meaning than it has.
A score of 92% does not prove that you reached flow. It does not know whether the work was difficult, whether the result was good, or whether your mind wandered while the phone stayed dark. The score answers one narrower question: once the session faded away, how often did you wake it to look again?
That narrowness is deliberate. FlowLock can measure what happens inside FlowLock. It should not pretend to read your mind.
- Lock Quality begins at 100 for each session.
- Waking a dimmed or Deep Mode session screen lowers the score.
- Locking your phone and letting the audio continue does not lower it.
- The score does not measure concentration, intelligence, effort, or work quality.
- Your pattern across similar sessions matters more than one perfect number.
What the score counts
During a running session, FlowLock gradually removes its own interface. The normal focus states dim after a few seconds and settle into Deep Mode after about twenty seconds. The timer is still running and the audio continues, but there is almost nothing left to watch.
If you tap that faded screen to bring the controls back, FlowLock records that check. In the current version, each recorded check lowers Lock Quality by four points. Zero checks leaves the score at 100. One check produces 96. Five checks produce 80. The score never drops below zero.
It is not a count of every control you touch. Starting the session is not a penalty. Deliberately dimming the visible interface is not a penalty. Lock Quality is aimed at the repeated check after the app has already stepped aside.
A focus app should not win by keeping you inside the app. FlowLock's interface fades because the work is somewhere else. Lock Quality gives that disappearance a simple feedback loop.
Why locking your phone does not hurt the score
FlowLock is built to keep playing when you lock your phone. That is normal use, not a broken session.
To FlowLock, locking the screen and moving to another app can look alike at the moment the app goes into the background. Treating every background event as distraction would punish the exact behavior FlowLock is designed to support. For that reason, Lock Quality currently uses screen checks for the score and does not subtract points simply because the app went into the background.
The result is intentionally conservative. FlowLock would rather miss an interruption than claim it knows why you left.
What Lock Quality does not measure
The percentage is a behavior signal, not a diagnosis or a productivity grade. It cannot tell you:
- Whether you were deeply focused. You can leave the phone alone and still stare out the window.
- Whether the work was valuable. A clean hour on the wrong task is still an hour on the wrong task.
- Whether the result was good. The app cannot inspect the code, paragraph, study notes, or decision you produced.
- How hard the session felt. Ten calm minutes and ten difficult minutes can produce the same score.
- Why you checked the screen. A deliberate pause and a reflexive check may look identical to software.
- What never started. A score from a finished session says nothing about the block you postponed all morning.
Lock Quality can help you examine a session that happened. It cannot replace choosing the right task, protecting the time, or making the first step clear. A quick digital workspace reset handles the setup that the score cannot see.
A 100 is not automatically your best session
Suppose you finish two blocks. The first lasts 25 minutes with a score of 100. The second lasts 90 minutes with a score of 92 and produces the hard section of work you had avoided all week. The smaller number does not make the second session worse.
The formula does not adjust for session length. One recorded check costs the same four points in a short block and a long one. Compare similar work when you can: writing against writing, study against study, and blocks that last 25 minutes against other blocks of the same length.
Use the number as a prompt, not a verdict. If it drops, ask what pulled you back to the screen. If it rises, ask what made the session easier to leave alone.
Use the average across ten sessions
FlowLock's Sessions view keeps completed sessions on your device and shows average Lock Quality across the most recent ten. That rolling view is where the metric earns its place.
One session can be noisy for ordinary reasons. You picked the wrong duration, someone interrupted you, or you needed to pause. Across a week of similar sessions, patterns start to show. You may stay settled for 35 minutes but not for 60. Writing may stay quiet in the morning and fragment after lunch. You may also see a difference when notifications are off before you begin.
A short weekly focus review turns those observations into one change for the next week. The goal is not to collect perfect sessions. It is to make the conditions for useful work easier to repeat.
How to use Lock Quality without gaming it
- Define the work before pressing start. A vague task sends you back to the screen because you never decided what to do.
- Choose a duration you can currently hold. Build from completed blocks instead of selecting a heroic number and abandoning it.
- Let the interface disappear. Keep the phone face down, lock it, or place it just out of reach while the audio continues.
- Do not restart to erase a messy score. The messy session contains the information.
- Review groups of similar sessions. Look for one repeatable trigger, then change that condition once.
If the problem is constant switching between messages, tabs, and tools, fix that environment directly. Lock Quality can show the checking pattern, but the practical work is reducing the opportunities to switch.
Run one realistic session, not your longest possible session. Let FlowLock fade, leave it alone, and review the score only after the block ends. Then write down the one thing that made you reach for the screen.
Keep the score in proportion
Productivity metrics often turn behavior into judgment. Minutes become commitment. Streaks become character. A missed day starts to feel like evidence about the person instead of the schedule.
Lock Quality works best as a small signal: one visible behavior during one completed session.
That narrow signal can help you adjust the next block without turning focus into another dashboard to manage. Start the session, let the app disappear, do the work, and look at the pattern later.