Timecrack 1.0.1-beta.1 Is Available
Timecrack 1.0.1-beta.1 is out. It carries everything from the alpha — the refreshed interface, tables that work on a phone, installable app support — and adds three things people kept asking for: a pause button on the running timer, a timezone of your own, and a warning when two trackings overlap.
This is still a pre-release. Try it on a staging instance or a copy of your data before you put it on the instance your invoices depend on.
Pause and Resume the Running Timer
The timer can be paused now. A break stays inside the tracking’s duration, but the paused time counts as non-billable instead of quietly inflating what you charge.
That means you no longer have to choose between stopping the timer and starting a new tracking for the same task, or letting a lunch break end up on an invoice. Start it, pause it when you step away, resume when you are back — the duration tells the honest story and the billable total does too.
Your Own Timezone
The account page has a timezone setting. Once it is set, everything follows it: the trackings you see, the filters you apply, the CSV you export, and the manual entry forms.
This matters as soon as an instance has people in more than one place. Until now every user read the same server clock, so a tracking entered at 9:00 in Berlin looked like something else entirely to a colleague in Athens. Each user picks their own now, and the numbers agree.
Warnings for Overlapping Trackings
If the same user has two trackings that overlap in time, Timecrack says so. The overlap is flagged in the history table and marked in the CSV export.
It is a warning, not a block — sometimes an overlap is exactly what you meant. But a forgotten running timer next to a manual entry is the usual cause, and it is the kind of mistake that only turns up when a client asks why the same hour was billed twice.
Everything From the Alpha
If you skipped 1.0.1-alpha.1, this release also brings:
- A refreshed design, built on design tokens, reduced to cinnamon orange plus dark with real contrast.
- Tables that work on a phone — one card per row with the column names as labels, and single-line rows on larger screens.
- Install Timecrack as an app (PWA) with a manifest, icons, service worker and an offline page.
- Larger touch targets, a sticky active timer and safe area padding on mobile.
- Session cookie names derived from
APP_KEY, so two installations on one domain stop logging each other out.
The alpha announcement covers all of it in detail.
Under the Hood
The shared page head markup moved into a single shared.head view, so every page pulls its meta tags, icons and assets from one place instead of repeating them.
How to Get It
Download the release from the GitHub releases page and follow the update steps. Back up your database and your .env file first, as with any update. Coming from the alpha, note that the cookie name change already logged everyone out once — this update does not repeat that.
If you would rather not run the upgrade yourself, Managed Hosting keeps your instance current for you, and Technical Support can help if an update does not go to plan.
Found a bug? Open an issue on GitHub. A beta gets to stable on the back of reports from real installations.
Need Professional Help?
Get custom development, managed hosting, data migration, and technical support — directly from the creators of Timecrack.
Explore Premium