Honest clocks

Hourtick estimates the server's clock on each device, so a laptop with the wrong time still records correct durations.

One running timer, always

The database guarantees one running timer per person, even when several devices come back online at once.

What works without a connection

• Start, stop, continue and switch timers
• Edit entries, notes, dates and durations you can see
• See your recent entries and timesheet from the device's cache
• Actions queue in the order you made them and show as pending until they sync
• Locks still apply: submitted, approved and invoiced time can't be changed, even by an offline device replaying later

What happens when you reconnect

Hourtick first confirms which account the device belongs to, then replays the queue in order. Each action is applied with the time you actually clicked, clamped between the last server event and now, so a wrong laptop clock can't invent hours. If a teammate or another device changed the same entry meanwhile, you get a notice and the server's version wins. Nothing is merged silently.

On every device

The browser keeps a queue, the Mac apps keep one for long offline stretches, and the iPhone and Android apps keep their timer queue and a local copy of your recent work, so screens open instantly even in the subway.