The challenge
Visitor systems are usually designed for the reception desk. At the gate, a guard is standing, often outdoors, sometimes facing a queue of cars, and needs one clear answer: can this person come in or not. A shared admin screen on a desktop does not serve that moment.
Guards also need to act on what they see — deny entry with a reason, tell a host their visitor has arrived, find everyone who has stayed past their pass — and do it in Arabic, in the terms Saudi security teams already use.
Our approach
We built Guard as a separate app from the same codebase as the consumer Aahlan app, with its own name, icon, bundle identifier and build profile, so each can be released on its own. Only security staff and administrators can use it; anyone else sees a clear “not authorised” screen, and the server checks the role again on every request.
One answer per scan
The scanner reads the QR with the camera, or takes the code typed by hand, and returns one of a fixed set of results — valid, awaiting approval, not yet valid, expired, revoked, blocklisted, wrong gate, already checked in, already checked out, not found, not permitted. Each has its own colour, label and haptic feedback.
Nothing faked
Where the backend does not yet support something, the app says so rather than pretending. When the connection drops, it detects it and shows a banner; it does not queue check-ins that could let the same person in twice.