← Back to projects
Productivity 2026 In progress

Timora: work-day tracking and reporting

Timora helps users manage time history, payment calculation, and reporting with strict per-user data separation. It includes complete flows for work days, templates/projects, and period settings on top of a feature-based architecture.

Challenge

Build a reliable app for daily work-day tracking and payment calculation, with configurable business rules and strict isolation between users.

Solution

Implemented a feature-based architecture on Next.js App Router using Server Actions, services, and repositories over Prisma. Added Better Auth, Zod validation, and automatic normal/overtime calculation per template.

Results

  • Create/edit work days with real-time hour and payment calculation
  • Template/project management with per-user rules
  • Exportable reports in CSV, PDF, and image
  • Flexible user-level period configuration
  • Solid technical base ready for new modules

Technical details

Stack and technologies

  • - Next.js 15 + React 19 + TypeScript
  • - Tailwind CSS v4 + reusable UI components
  • - Prisma 7 + PostgreSQL
  • - Better Auth (Prisma adapter)
  • - Zod for Server Action validation
  • - Zustand for client notifications

How it is organized

  • - src/app: routes, layouts, redirects, metadata
  • - src/features: work-days, projects, reports, settings, auth, notifications
  • - src/lib: shared infra (auth, prisma, utilities)
  • - Actions validate input and delegate business logic to services
  • - Repositories encapsulate Prisma access

Key modules

  • - Work-days: create/edit entries and split normal/overtime by cutoff
  • - Projects: user templates with rate and multiplier rules
  • - Reports: range/project analytics + CSV/PDF/image exports
  • - Settings: period preferences and week-start options
  • - Auth: login/register, sessions, reusable guards

Risks / technical debt

  • - Growing overtime-rule complexity may require a dedicated rule engine
  • - Server Action-heavy flow requires strict error-handling discipline
  • - Limited e2e coverage leaves critical flows mostly unit-tested
  • - Concurrent work-day edits should be monitored closely

Need to build or improve a system?

I help turn the need into a clear technical direction and a clean execution plan.

Book a conversation View LinkedIn