Product principle

A prompt that waits. Persistent acknowledgement.

Useful alerts can sound once, disappear and be forgotten while attention stays on the screen. UP Timer keeps the prompt visible and continues the selected sound or voice until you acknowledge it. Acknowledgement confirms that the prompt was seen—not that an action was completed.

Designed for the moment attention is still somewhere else.
UP Timer alert Waiting for acknowledgement

Focus session complete

Your selected focus phase has reached its endpoint. The prompt remains active until you respond.

Male voice example Focus session complete. Time to take a break.
Acknowledge

The design problem

An alert is only useful if it returns attention to the moment.

The difference is not more notifications. It is what happens after the selected timer point is reached.

A conventional alert

Sounds once. Disappears.

The message may be missed, dismissed automatically or lost beneath another task while the user remains focused elsewhere.

Alert cleared
UP Timer acknowledgement

Stays visible. Waits.

The on-screen message remains active and the selected audio continues until the user gives a conscious acknowledgement.

Waiting for acknowledgement

Three-stage behaviour

Due. Active. Acknowledged.

The same core behaviour supports Focus, Hydrate, Move and Learn while each timer keeps its own message and settings.

01 / Due

A timer reaches its selected point.

A focus phase completes, a water reminder becomes due, a movement cadence ends or a Learn Sprint is ready.

02 / Active

The prompt remains on screen.

The chosen sound or male or female voice continues, subject to browser permission, device settings and volume.

03 / Acknowledged

The user consciously clears it.

The active alert ends only after the acknowledgement control is used.

Clear boundaries

What acknowledgement means—and what it does not.

This distinction matters for honest product communication, personal use and future Company privacy boundaries.

It does mean

The alert received a response.

  • The on-screen prompt was consciously cleared.
  • The selected persistent audio can stop.
  • The timer can move into its next state.
It does not mean

The real-world action was verified.

  • It does not prove that water was drunk.
  • It does not prove that movement or an exercise was completed.
  • It does not prove learning, recall, focus or productivity.

One behaviour across four timers

Different prompts. The same deliberate response.

Focus phase complete. Water reminder. Time to move. Learn Sprint ready. Each event has a different purpose, but the acknowledgement behaviour keeps the transition visible until the user responds.

  • Focus Completed focus and break phases.
  • Hydrate Selected water reminder points.
  • Move The end of a chosen movement cadence.
  • Learn Immediate or scheduled Learn Sprint prompts.
UP Timer alert Waiting for acknowledgement

Time to move

Your movement prompt is active.

Female voice example Time to move. Stand, stretch or change position.
Acknowledge

User control

Noticeable without pretending every environment is the same.

Browser notifications and audio depend on permission, device volume, operating-system settings and the way the browser handles background activity.

01

On-screen prompt

The active alert remains part of the timer interface until acknowledgement.

02

Sound or voice

Choose the alert treatment that is easiest for you to notice, including available male and female voice options.

03

Desktop notification

Allow browser notifications to bring a timer event back into view when the timer is not the active part of the screen.

Focus. Hydrate. Move. Learn.

Use a timer that waits for your response.

Start with free Lite and experience persistent acknowledgement across the connected timer workspace.