docs/wiki/4.15-Timers-and-Focus-Mode.md
Focus Mode in Super Productivity addresses a central challenge of task-based work: maintaining sustained attention and structured work sessions in the face of distractions and context switching. The app is designed to help you stay organized and focused through timeboxing, time tracking, break reminders, anti-procrastination features, and a Pomodoro-style timer—all working together to support healthy, productive habits. Timers and focus are treated as a first-class feature: they have dedicated configuration, distinct modes with clear behavior, and deep integration with task tracking and metrics. Understanding what problem Focus Mode solves, how it relates to time-boxing and deep work, what the app assumes about focus when using timers, and how timers influence your behavior helps you use it effectively.
For how time is logged when you track a task, see [[4.14-How-Time-Is-Logged]]. Focus Mode settings (sync with task tracking, tick sound, preparation screen, breaks, etc.) are in [[3.02-Settings-and-Preferences]].
Productivity loss from distractions and context switching is something the app explicitly tries to reduce. Focus Mode gives you:
The app’s metrics also reflect this. They can classify your day into states that include an ideal deep-flow state (high productivity and high sustainability) and a drift state (low productivity and low sustainability—often indicating attention or focus problems). That encourages you to reflect not only on how much you worked but on how you worked: sustained focus vs fragmented attention.
Focus Mode implements three distinct time-boxing strategies, each aligned with different productivity approaches:
Pomodoro is classic time-boxing with fixed work and break lengths:
The app can automatically start the next work session after a break, so you can run multiple cycles in a row. Pomodoro is well suited to disciplined, interval-based work: clear boundaries, regular rest, and a predictable rhythm.
Flowtime supports open-ended deep work without a fixed session length:
Flowtime is for when you want sustained focus without a hard stop: you start the session, work until you’re done or need a break, then end it manually. The timer still tracks how long you’ve been working so you can see elapsed time.
Countdown is custom-duration time-boxing:
Countdown is for when you want time-boxing with flexibility: e.g. “I’ll focus for 45 minutes on this” or “I’ll do 20 minutes and then switch.”
The app’s design reflects the idea that sustainable deep work has a natural limit. The metrics use an optimal focus target of 4 hours per day (240 minutes). That aligns with research suggesting that beyond a certain amount of focused work, gains diminish and fatigue grows. So Focus Mode and the metrics are built not to maximize “more hours” but to support focused, sustainable work: enough structure to protect attention, and enough flexibility (especially in Flowtime) to preserve flow when it happens.
Several assumptions drive how timers behave and how focus is evaluated.
A work session is treated as complete when:
Elapsed time is always calculated from when the session started to now, so the duration is accurate even if update intervals vary. For Flowtime, there is no set duration, so the session never completes automatically; you must end it yourself. That preserves the “no interruption” design of Flowtime.
So “session done” means something different per mode: in Pomodoro it triggers a break (and possibly the next session); in Countdown it just ends; in Flowtime it only ends when you say so.
The app’s productivity and sustainability metrics assume that more focus time is not always better. They use an inverted-V curve for focus balance: up to the optimal amount (e.g. 4 hours), more focus improves the score; beyond that, excessive focus is penalized (e.g. with an exponential decay). That reflects the reality that cognitive fatigue is non-linear: pushing far beyond the sustainable range does not improve outcomes and can hurt sustainability. So the system encourages you to value sustainable focus, not maximum hours.
Timers affect how you work through several mechanisms.
When enabled in settings, the app can play a tick sound during work sessions (typically once per second, at a reduced volume so it’s not intrusive). That keeps you subtly aware that time is passing and that you’re in a focus block, without requiring you to look at the screen.
When a work session or break completes, the app can:
That multi-channel feedback makes it clear when to switch from work to break or from break back to work, or when a Countdown session has ended.
When “sync session with task tracking” is enabled, Focus Mode and time tracking work together in both directions:
That creates a bidirectional link: starting or pausing the task affects the focus session, and starting or ending a focus session (or break) can affect what’s being tracked. The result is that “focus time” and “logged task time” stay in sync when you want them to.
The app’s productivity score combines several factors. Focus time is one of them (often weighted around 30%): progress toward your focus target improves the score. But impact (your own assessment of how valuable the work was) is weighted more heavily (e.g. around 65%). So the system encourages you to reflect on the value of work, not only on time spent. Focus time is rewarded, but the main driver of the score is whether the work mattered. That supports a balance between “did I focus?” and “did I do something that mattered?”
Focus Mode is not a minor add-on; it’s designed as a core part of the workflow.
Focus Mode has its own timer state (running, started-at time, elapsed, duration, work vs break), UI screens (task selection, duration selection, preparation, main timer, session done, break), and session metadata (mode, cycle, last completed duration, paused task). The timer is the single source of truth for “how long has this session been running?” so the UI and any logic that depends on session length stay consistent.
Each mode (Pomodoro, Flowtime, Countdown) has defined behavior: different session lengths, different break rules, different completion behavior. The app doesn’t treat them as “one timer with different numbers”; it treats them as distinct strategies. So Pomodoro always has breaks and cycles; Flowtime never auto-completes; Countdown always lets you set the duration. That makes each mode predictable and purposeful.
Focus Mode has multiple dedicated settings (e.g. sync with task tracking, start in background, skip preparation screen, play tick sound, pause task tracking during break, manual break start). Those options show that focus is meant to be configurable to your workflow. The feature is also woven into the app: session lifecycle (start, tick, complete), break handling, task-tracking sync, and metrics all depend on focus state. So focus is central to the workflow, not a side panel you can ignore.
The design treats focus as a skill to be developed and maintained. That’s why the app offers:
The 4-hour optimal focus target and the penalty for excessive focus reinforce that the goal is sustainable productivity, not maximum hours at any cost.