Back to the homepageOmarAR

Full-stack case study · 2025—2026

From scattered operationsto one accountable system.

FAYA Staff is the company’s central staff and operations system. It lets teams assign and follow projects and tasks, record work time and attendance, manage leave and payroll, communicate, and generate management reports from one bilingual platform.

Production productView live product
Role
Primary full-stack engineer
Ownership
Product, interface, data & delivery
Platform
Web · PWA · iOS · Android
Status
Live and actively developed

Repository evidence

Verified from the production codebase and automated test suite on 8 Sep 2026.
142
Application pages
338
API route files
108
Data models
287
Passing tests

01 / The challenge

Operational truth was split across different moments of work.

A task board alone could not answer the questions that matter to an operating company: who is working, where time went, what is blocked, how attendance affects compensation, and what managers or clients are allowed to see.

The product needed to make those answers consistent without turning everyday work into administration. It also had to support Arabic and English, office and remote work, intermittent connections, and different levels of financial sensitivity.

A

One connected workflow

Projects, tasks, activity, attendance, requests, and payroll had to share the same operational context.

B

Time that can be trusted

Browser sleep, network loss, duplicate recovery, and remote stops could not silently inflate recorded work.

C

Permissions at every layer

Workspace, project, employee, client, and compensation views required different access boundaries.

D

Usable everywhere

The same product needed to work in Arabic and English across desktop, mobile web, and installable app surfaces.

02 / The solution

A full operating layer, not another isolated dashboard.

I shaped the platform as a connected system of record. Work starts with a workspace and project structure, moves through assignment and execution, produces verified time and attendance data, and ends in payroll, performance, and management reporting.
  1. 01

    Plan and assign

    Hierarchical projects, Kanban boards, sprints, multi-assignee tasks, recurring work, labels, dependencies, files, and approvals.

  2. 02

    Work and collaborate

    Project, direct, and group chat; comments and mentions; meetings, transcripts, AI-assisted minutes, and an internal knowledge base.

  3. 03

    Record and verify

    Time sessions, activity capture, GPS-aware office attendance, face attendance, live location, leave, and controlled offline recovery.

  4. 04

    Calculate and understand

    Hybrid office/remote compensation, rate history, deductions, payslips, attendance sheets, operational analytics, and annual reports.

03 / System architecture

The data follows the work.

The architecture keeps core business rules on the server while the interface stays responsive through optimistic state, live events, and offline-aware recovery.

01Identity & workspace
02Projects & task graph
03Time & attendance
04Payroll & reports

SSE events · Socket.io rooms · Push notifications · Telegram alerts

04 / Engineering decisions

Reliability came from designing the failure cases first.

Server-owned time sessions

Heartbeat leases and server-side stop rules prevent an abandoned browser timer from becoming accepted work time. SSE keeps other tabs and managers synchronized.

Lease renewal · expiry handling · remote stop · stale-session checks

Bounded, idempotent offline recovery

Recovery is validated against the known session window, excludes computer sleep time, caps one incident, and uses a unique recovery key to prevent double counting.

Network recovery · overlap trimming · duplicate protection

Authorization before presentation

Workspace and project roles are enforced at the data boundary, while compensation and sensitive employee fields are excluded for unauthorized viewers.

RBAC · project membership · client access · compensation guards

One product across form factors

Responsive application shells, PWA installation, push notifications, offline states, and Capacitor wrappers extend the same workflows beyond desktop.

Arabic/English · RTL/LTR · Web/PWA · iOS/Android

06 / Technology

A product stack chosen for connected operations.

Product interface

  • Next.js 16
  • React 19
  • TypeScript
  • Tailwind CSS
  • Radix UI
  • next-intl

Data & services

  • PostgreSQL
  • Prisma
  • Zod
  • S3 storage
  • Sharp
  • Nodemailer

Live & mobile

  • Socket.io
  • Server-Sent Events
  • Web Push
  • Service Worker
  • Capacitor

Intelligence & quality

  • AI gateway
  • Speech-to-text
  • Vitest
  • Docker
  • CI-ready releases

07 / The result

A single product that can carry the operating day.

FAYA Staff now covers the path from a new project and assigned task to verified work, attendance, pay, reporting, and team knowledge. It gives administrators, employees, and clients distinct experiences on top of one connected data model.
  • Three role-specific product surfaces: administration, employee, and client.
  • Hybrid office and remote payroll grounded in recorded sessions and rate history.
  • Real-time communication, meetings, knowledge, and notifications around the work itself.
  • A bilingual, installable product backed by 287 passing automated tests.

No confidential employee records, customer data, revenue, or adoption figures are disclosed in this case study.