Time Tracker

Time Tracker is a personal project built as an internal analysis tool over already-collected time-tracking data. The React 19 frontend loads the main entry set and a separate overtime set through the API, combines them chronologically, and calculates statistics by project, language, and day. If the API is unavailable, reads fall back to the static JSON files included in the application.

The reporting pipeline does not use just the raw time. For each project, except for entries marked Unknown Project, the calculation utility adds a fixed 50% overhead for testing/processing and distributes it across the project's entries, keeping the original time and the added time separate. Projects configured as excluded are then removed from statistics and reports. This is an explicit rule of the analyzed snapshot, not a UI-configurable model.

The dashboard offers quick filters for today, this week, this month, last month, the last 7 or 30 days, a custom range, projects, languages, and text search. Filtered data can be exported as CSV. Recharts is used for the top projects, language distribution, and daily activity, and a sortable, paginated table component exists in the code, although it is disabled on the main screen.

For financial reporting, projects can be grouped and associated with an hourly rate. The group report identifies the projects' entries, calculates the resulting hours and value, then requests the EUR exchange rate from the BNR through the backend for an indicative conversion to RON. Both the group billing report and the hours report have dedicated print layouts.

The administrative area includes manual entry addition, CRUD for project groups, bulk JSON import that replaces the main dataset, management of excluded projects, and editing or deleting overtime hours. Some of these operations are accessed via keyboard shortcuts, as an internal interface rather than a separate admin with role-based authorization.

The Express backend persists data directly in JSON files under public/, with no ORM or database. Authentication uses JWT with a 24-hour expiration and an in-memory registry for active tokens. Deployment is prepared for a single PM2 process with automatic restart and file-based logs. The PWA is configured through vite-plugin-pwa with auto-update and caching for static assets/fonts, but the code does not implement Background Sync or an offline write queue.

The snapshot should be treated as a personal tool/operational prototype, not a hardened multi-user product. Extending it toward multi-user use would require additional hardening for credential storage, per-role and per-resource authorization, concurrent/atomic persistence, and automated validation through tests and CI/CD.