Program Lucru (Work Schedule)

Program Lucru evolved from a shift viewer into a multi-user operational product. Each employee has their own calendar with work, off, or vacation days, start and end times, and notes. The schedule can be edited on a single day or in bulk for a month, is available in day, week, and month views, and feeds the monthly statistics, time tracking, and ICS calendar export. The current implementation persists shifts explicitly per day; the repository does not implement a formal recurrence rule that automatically generates the schedule.

Time tracking links actual time to the planned schedule. The user can clock in and out, view monthly history, and the system calculates the estimated clock-out time and statistics such as lateness relative to the scheduled time. Manual entries are supported for corrections, with ownership control for the user and administrative access to view or operate other accounts' data. Separately, time-off-in-lieu has its own CRUD flow, with reason, number of hours, pending/resolved status, and resolution date, and the totals are included in the monthly statistics.

The product has three surfaces connected to the same API. The React PWA provides the main responsive, installable interface, with a Service Worker, offline caching, and Web Push. The React Native/Expo app reproduces the essential flows on mobile and adds precise local alarms: alarm rules are kept server-side per user, and the client synchronizes the schedule for the next 14 days and schedules the alarms locally via Notifee. The backend also includes a Web Push message scheduler adapted to the shift phase or day type, plus management of messages and the target user.

The confirmed roles are consultant, merch, and admin. The administrator can manage users and roles, inspect time tracking, view aggregated statistics, and temporarily enter an employee's interface through server-side controlled impersonation. Access to the BBD module is restricted to consultant and admin. BBD tracks products by brand and batches with an expiration month/year, quantity, and resolved status, offers server-side search and filtering, barcode scanning, brand-level notes, buyer history, and a grouped Excel export.

The backend is an Express/TypeScript application with a SQLite database loaded via sql.js and persisted to disk. The schema went through incremental migrations for multi-user support, expiring sessions, BBD batches, and moving the resolved status to the batch level. Authentication uses cryptographically generated session tokens, bcrypt passwords, and transparent migration from old SHA-256 hashes, and login is protected with rate limiting. Web and backend deployment runs automatically on push to main via GitHub Actions and SSH to a VPS, with a Node.js build, Nginx, and PM2; the database has a separate daily backup script with a seven-day retention.

The architecture is suited for an internal product with moderate volume and single-instance deployment, but the code is not presented as a horizontally scalable solution. sql.js persistence exports the database to a file after mutations, the push scheduler lives inside the API process, and some older scripts — notably the JSON importer for the single-user schema — have fallen behind the current model. These limits matter for technical evaluation and define the natural directions for evolution: transactions and stricter validation for bulk writes, conventional server-side persistence for higher concurrency, and isolating offline caches by user identity.