I designed and engineered LeadX HRMS for Genius PMO as one source of truth for workforce operations. The responsive web platform and focused Android companion share a FastAPI and PostgreSQL backend that owns identity, scoped permissions, workflow state, attendance decisions, and audit history. The result moved beyond a prototype into a deployment-ready source handoff with automated checks, reproducible delivery, backup and recovery procedures, and a physically tested preview APK.
Workforce platform for Genius PMO02 /Product experience
What the product does.
01Responsibility-Aware Workspaces3 capabilities
Company Admin & HR
Company controls, organization setup, employee lifecycle, schedules, leave, documents, equipment, requests, reports, and audit history share one operational model.
Scoped Leadership
Department Managers and Team Leads receive only their assigned department or project context, without broader HR access.
Payroll & Self-Service
Payroll receives a minimum-data preparation view while employees manage only their own profile, requests, documents, payslips, and attendance.
02Connected Operations3 capabilities
One Linked Identity
Additional responsibilities are additive and explicitly scoped, so people do not need duplicate accounts to move between authorized workspaces.
Shared Workflow Truth
Schedules and leave affect attendance; attendance and adjustments feed payroll; decisions create notifications, reports, and audit history.
Inclusive Product UX
English and French, light and dark themes, responsive layouts, reduced motion, keyboard-aware dialogs, and focused system states support daily use.
03Security & Delivery3 capabilities
Server-Authorized Attendance
The backend derives identity, schedule, leave, work mode, and attendance state before it accepts a Check In or Check Out.
Approved Office Networks
Office mobile attendance fails closed unless the backend resolves the client inside an active, audited Office CIDR approved from Company Settings.
Deployment Handoff
Production images, migrations, configuration checks, health endpoints, CI, matched backups, restore guidance, source exports, and a tested preview APK support company deployment.
03 /System design
How the pieces connect.
System workflow
Two clients. One workforce system.
The web platform and Android attendance companion share backend-owned identity, permissions, work-mode rules, and attendance records.
Documented project flow
Role-specific clients
Next.js webHR, leadership, payroll, admin, and employees
Android companionEmployee profile and Check In/Out
Authenticated requests
Backend authority
FastAPIScope, work-mode rules, attendance decisions, and audit history
Validated writes
Shared records
PostgreSQLWorkforce data with versioned migrations
Protected uploadsSeparate, matched backup and restore
01One Platform, Two Focused Clients
A responsive Next.js application and the LeadX Attendance Android companion share one backend and one database. FastAPI owns authentication, authorization, operational transitions, attendance decisions, and persistence rather than trusting the clients.
Dedicated Company Admin, HR, Manager, Team Lead, Payroll, and Employee experiences.
Mobile
A small employee app for sign-in, profile, today's assignment, and Check In/Out.
API
Server-derived identity, scope, rules, workflow transitions, and attendance authorization.
Data
PostgreSQL persistence with versioned Alembic migrations and protected upload storage.
02Technical Architecture
The product separates presentation from backend-owned security and business rules. Signed HttpOnly web sessions and protected mobile bearer sessions reach the same API, while production configuration validates trusted hosts, origins, cookies, proxy boundaries, and required secrets.
Argon2 credentials, signed web cookies, and SecureStore-backed mobile access.
Scope
Backend-derived role, responsibility, employee identity, and data projection.
Operations
Request IDs, security headers, throttling, health/readiness, and audit history.
Persistence
PostgreSQL operational data and separately protected uploads.
03Server-Authoritative Mobile Attendance
The employee cannot choose a different work mode in the app. Remote uses the normal public HTTPS API, External Site stays mobile-only, and Office stays mobile-only with backend-resolved approved-network verification. Leave and Not Scheduled remain blocked.
The resolved client address must be inside the active approved Office CIDRs.
Remote
Web or mobile can use the same public API and daily attendance record.
External Site
Mobile-only attendance uses the assigned mode from HRMS.
Fail closed
Missing Office configuration, invalid scope, leave, schedule, duplicates, or state conflicts block the write.
04Delivery, Verification & Recovery
The company handoff includes exact-commit source exports, production containers, explicit migration steps, a tested preview APK, configuration guidance, and a matched PostgreSQL and upload backup with verification and restore procedures.
Company, department, project, payroll, and personal responsibilities needed different navigation and minimum-data projections while still sharing one employee identity and one operational source of truth.
02
Convenient Attendance Without Trusting the Client
The web and Android interfaces needed clear actions, but only the backend could safely derive the employee, assigned work mode, schedule, leave, network eligibility, duplicate state, and valid transition.
03
A Product That Could Leave the Development Machine
Persistent data, safe migrations, fail-closed production configuration, repeatable Android builds, automated checks, matched backups, and company-facing recovery guidance were delivery requirements rather than later polish.
06 /The toolkit
Each tool has a job.
Open a technology to see its role in this project.
Web Experience
Next.js 15 +
Responsive role-aware web application
React 19 +
Interactive operational workspaces
TypeScript +
Typed client contracts and workflows
Mobile Attendance
Expo 54 +
Android application and build workflow
React Native 0.81 +
Focused attendance companion
SecureStore +
Protected mobile bearer-session storage
EAS Build +
Reproducible preview and production builds
API & Data
FastAPI +
Authentication, authorization, rules, and workflow transitions
Python 3.12 +
Backend application runtime
PostgreSQL 17 +
Persistent operational source of truth
SQLAlchemy +
Asynchronous data access
Alembic +
Versioned database migrations
Delivery & Quality
Docker Compose +
Web, API, and database orchestration
GitHub Actions +
Automated quality and build checks
Playwright +
Chromium workflow regression coverage
Ruff +
Python quality checks
SHA-256 Backups +
Matched database and upload recovery packages
07 /Delivery notes
The documented scope.
125
Backend Tests
The final HRMS revision passes the verified backend test suite.
09
Browser Workflows
Chromium regression coverage spans Employee, Team Lead, Department Manager, HR, Payroll, and Admin responsibilities.
02
Connected Clients
The responsive web platform and Android attendance companion share one backend, database, identity model, and attendance record.
Next milestone
The next step is defined.
Add the company HTTPS API URL, DNS/TLS, production secrets, database settings, and exact Office/proxy networks, then rebuild the final Android release.
