Engineering Work
Biometric Attendance System
A tamper-proof fingerprint attendance system — from sensor hardware and RTOS firmware to a role-based web dashboard — deployed across schools and offices with full hardware-to-dashboard delivery.
Engineering Work
A tamper-proof fingerprint attendance system — from sensor hardware and RTOS firmware to a role-based web dashboard — deployed across schools and offices with full hardware-to-dashboard delivery.
Manual and card-based attendance systems are fundamentally insecure — proxy sign-ins are trivially easy and attendance records are inaccurate. The goal was a biometric attendance system deployable in schools and small offices without enterprise hardware budgets or per-device subscription licensing.
The system had to work offline (the fingerprint reader must always respond even without network connectivity), sync records reliably when the network returned, and produce per-department reports accessible to administrators without exposing all data to all staff.
Deployed across schools and office environments, the system eliminated proxy sign-ins entirely — attendance records became verifiable and consistent. Hardware cost per unit was kept below what commercial fingerprint terminals cost without any of the cloud dependency or subscription requirements. The project delivered the full stack from physical hardware to browser-based reporting.
Architecture
The architecture visual is intended to show how edge capture, buffering, transport, event processing, and operator-facing systems fit together under real deployment constraints.
Systems Map
A concise overview of edge capture, reliable transport, event handling, and operator visibility.
What to look for
What I Would Do Differently
Replace the synchronous Wi-Fi sync with a local-first queue and background flush. The original approach blocked the fingerprint reader thread during sync operations — causing visible latency spikes when the network reconnected after being offline. A queued approach would keep the sensor always responsive.
Stack
The implementation choices below reflect the boundary between field reliability, event architecture, and operator-facing systems.