# How FlowFlight works

> A focus timer with a destination.

FlowFlight is a timer built for flow state. Pick a 25, 45, 90, or 120 minute focus timer on a real flight path, take off, and stay airborne until you land.

Start flying: https://flowflight.app/departures

## Use cases

- **Focus timer for coding.** A 90 min timer for a feature, a refactor, or a debugging stretch that should not lose the thread to another tab.
- **Focus timer for writing.** Draft, edit, or ship a post in one airborne block. The landing is the deadline — not an open doc you mean to finish later.
- **Focus timer for studying.** A 25 minute timer for a single chapter, or a 90 min timer when the material needs a full deep-work cycle.
- **Focus timer for design.** Stay in the file until the gate. Cabin noise and a moving map keep the session on course while you iterate.
- **Deep work for research.** Read papers, review a PR, or think through a hard problem for 45, 60, or 120 minutes without a stack of short alarms.

## Session lengths

- **25 minute timer.** A short hop — the same length as a classic pomodoro — when you have one clean block.
- **45 minute timer.** A longer stretch without a break. Enough runway to get into the work, not so long that the landing feels abstract.
- **60 minute timer.** An hour in the air. One focused session with a visible destination instead of a countdown in a browser tab.
- **90 min timer.** A full deep-work cycle. Alertness rises and dips in roughly 90-minute waves — this is the block most people already mean by “a real session.”
- **120 minute timer.** A long-haul focus timer for work that needs two hours of uninterrupted attention.

## Why it works

The aviation skin isn’t decoration. A flight is a container for flow — the constraints, the moving map, and the session lengths come from well-studied attention science.

- **Flow state.** Flow needs a clear goal, immediate feedback, and just enough challenge to hold attention. A flight gives you all three: a destination, a moving map, and a block long enough to disappear into the work.
- **Parkinson’s Law.** Work expands to fill the time available. A flight has a gate time. That constraint is the focus session — not a suggestion, a landing slot.
- **Goal-gradient effect.** People persist more as they perceive themselves getting closer to a goal. Watching the aircraft close the gap makes remaining time tangible, not abstract.
- **Implementation intentions.** “When I take off, I work until landing” is a specific cue–action pair. Research on implementation intentions shows these plans outperform vague goals like “I’ll focus later.”
- **Ultradian rhythms.** Alertness naturally rises and dips in roughly 90-minute cycles. The 90 min timer — and the 25, 45, 60, and 120 minute routes — map onto the blocks most people already use for deep work.

## FAQ

**Is FlowFlight a pomodoro timer?** It’s a focus timer with a destination instead of a tomato. You can fly a 25 minute timer if you want a pomodoro-length hop, or choose 45, 60, 90, or 120 minutes when the work needs a longer block.

**What is the 90 min timer for?** A 90 min timer is one ultradian cycle — the span most people can hold deep work before attention dips. Pick that corridor when you want a full session, not a stack of short alarms.

**Do I need an account?** No. The globe, cabin noise, and timer work signed out. Sign in with Google only if you want hops of 10 minutes or more saved to your logbook.

**Can I pause a focus session?** Yes. Pause and resume from the flight deck. The clock only runs while you’re airborne. End early if you need to — signed-in flights under 10 minutes focused are not logged.

HTML version: https://flowflight.app/how-it-works