Ian Macabulos

Ian Macabulos

Full-Stack Developer

UA LabSign — Laboratory Attendance System

Device-Bound Laboratory Attendance Across Web & Android

UA LabSign replaces manual laboratory attendance with a coordinated web and Android workflow. Institutional sign-in, device-bound ECDSA P-256 signatures, client-side geofence checks, and short-lived room PINs connect each student check-in with faculty oversight and administrative records.

Next.jsTypeScriptPostgreSQLReact NativeExpo

From manual laboratory logs to a verifiable digital workflow

Paper logs and spreadsheets made laboratory attendance difficult to audit: another student could sign for someone else, entries could be inaccurate, and staff still had to consolidate the records. I built UA LabSign to connect student check-in, faculty review, and administration in one digital workflow with clearer attribution.

An account alone cannot establish attendance

A university Google account establishes who signed in. It does not establish which device submitted a check-in, whether that device signed it, or whether a class PIN is still valid. UA LabSign combines those server-side checks with a client-side location readiness gate rather than treating a successful login as sufficient attendance evidence.

One attendance workflow, two clients

Web portal

The Next.js portal connects student check-in with faculty and administrator dashboards, class sessions, attendance records, and reporting. Prisma and PostgreSQL hold the shared records.

Android companion

The React Native and Expo app handles student sign-in, device key generation, and signed check-ins against the same backend. Private keys stay in SecureStore; readiness checks, history, and device recovery complete the student workflow.

The device becomes part of the attendance credential

Knowing an account’s credentials does not reproduce the device’s private signing key. ECDSA P-256 lets the server check a request against a registered public key while the private key remains on the student’s device.

At registration
The device generates a key pair and registers its public key with the student’s account. The web client keeps the private CryptoKey in IndexedDB; Android stores its private key locally using Expo SecureStore.
At check-in
The device signs a payload containing the student ID, room, and timestamp. The server verifies that signature against the stored public key before accepting the attendance record.

A check-in combines distinct signals

  1. 1

    Institutional identity

    The student signs in through the approved university Google account flow.

  2. 2

    Registered device

    The student must have an active public-key binding; revoking or replacing it changes which key can verify a check-in.

  3. 3

    Signed attendance request

    The device signs the payload with its ECDSA P-256 private key. The backend verifies the signature against the stored public key and checks timestamp drift.

  4. 4

    Location readiness

    The client checks the configured campus geofence before enabling submission. Coordinates are not sent to the attendance endpoint for independent server-side GPS verification.

  5. 5

    Active class session

    The backend matches the room and unexpired PIN to a schedule, checks for duplicate attendance, and classifies the record as late or on time.

Security includes recovery and day-to-day operations

Device-bound signing

The client keeps its private key; the server uses the registered public key to verify attendance submissions.

Short-lived class access

Faculty-generated room PINs expire, narrowing the window in which a class check-in can be accepted.

Recovery and revocation

A recovery PIN lets students re-bind a replacement device. Administrators can revoke outdated or compromised bindings.

Auditable records

Timestamps, history, filtering, manual exceptions, and reports make attendance and administrative activity reviewable.

The check-in is only half of the workflow

Faculty

Start sessions for scheduled laboratory classes, generate short-lived PINs, watch attendance activity, review class records, handle legitimate exceptions, and export reports.

Administration

Manage schedules, staff assignments, and registered devices, then review attendance records and audit history. The record stays useful after the student has checked in.

From check-in to a usable class record

UA LabSign turns a manual process into a connected record that starts with the student’s device and continues through faculty review, reporting, device management, and administrative auditing. The web and Android clients share a workflow built around stronger attribution and clearer records.