Sync Timer — Shared Focus Sessions for Teams

Create a timer, share a link, and keep your whole team in sync. One host controls start and pause — everyone else sees the same countdown in real time.

No Account — Link-Based Sessions

1–2 Second Sync Accuracy

Optional Co-Host Control

New shared session

Focus

25 min

Short break

5 min

Long break

15 min

Enable co-host

Generates a separate invite link. Co-hosts can start, pause, and reset the timer. If you close your tab, a co-host keeps the session running.

Session expires after 24 hours · No account required

Why sync matters for focus work

Remote teams working in parallel often drift out of sync — one person is in a break while another is deep in focus, making interruptions more likely. A shared timer solves this by giving everyone the same rhythm. When the host starts the focus block, every participant sees it start. When it ends, everyone gets the cue to break at the same moment — no Slack message required.

How the sync works

Rather than sending a tick every second (which would flood the connection and still drift), the host broadcasts a single event: “started at timestamp T with N seconds remaining.” Every viewer independently counts down from that anchor. The result is sub-second accuracy with almost zero network load — and late joiners get the current state the moment they open the link.

Frequently Asked Questions

How does the shared timer work?

You create a session and get a link to share. Everyone who opens the link sees the same timer running in real time — synced via Supabase Realtime (WebSockets under the hood). The host controls start, pause, and reset; viewers just watch.

What is a co-host?

A co-host has the same controls as the host — they can start, pause, and reset the timer. If you enable the co-host option when creating a session, you get a separate invite link to send to someone you trust. If the host closes their tab, the co-host keeps the session running.

How accurate is the sync?

Typically within 1–2 seconds. Rather than sending a tick every second, the timer broadcasts a single timestamp when the host presses Start. Each viewer independently computes elapsed time from that timestamp, so the drift is just network latency — usually 50–200 ms.