2025 · Zendata · Enterprise client (NDA)
Asset checkout control with QR scanning and offline operation
Records which asset leaves, who authorized it, and when it was validated at the checkpoint, even without a network. I built the Laravel backend and the Ionic app. Next step: measuring its reliability.
- Laravel
- Ionic
- Capacitor
- QR
- Offline-first
My role
Laravel backend and Ionic/Capacitor mobile app. The team extends the modules and QA validates them.
Evidence
What I did
- Laravel backend: assets, checkout requests, and validation.
- Ionic/Capacitor app with QR scanning.
- Offline operation: records are stored on the device and synced when the network comes back.
Still to be measured
- Latency, errors, sync time, and duplicate or lost records.
Next step
- Measure first, optimize after: baseline, one change at a time, with before and after.
- An independent public version as a personal AWS project, written from scratch.
The idea
If validation depends on the network and the connection drops at the gate, the process stops. That’s why the app works offline and syncs later.
request ──► authorization ──► QR scan ──► local record ──► sync ──► Laravel APIWhy it’s still open
An offline system can fail without anyone noticing: duplicates on retry, scans that never arrive, or slow syncs. The next step is to measure before optimizing, then build my own public version on AWS (Docker, CI/CD, infrastructure as code) that works through the same problem with nothing from the client.