QR Check-in

The door, and nothing else. Scanning has to be instant, has to work with no signal, and has to refuse a second scan of the same ticket.

From$549

Open the preview Request a quote

Function: 22
User types: 1
Platform: iOS & Android

React Native
TypeScript
PostgreSQL
Expo

Inside the app

What it does out of the box

22 connected functions on one schema across 1 user type. Everything below is in the template before a line of customisation.

Scan
Camera open on launch, result in under a second, large and readable in bad light. The whole app is this screen.
Offline
The door list is on the device. Scans validate locally and sync afterwards. Venue wifi failing must not stop a queue, and it will fail.
Single use
A ticket scans once. The second attempt is refused clearly, with when and where the first scan happened.
Find a name
For the dead phone, the wrong email and the person who never got the ticket. That queue exists at every event.
Live count
Admitted, by session and by entrance, which is what safety limits are actually measured against.
Multiple doors
Several devices scanning the same event, staying consistent without waiting on a central connection.

User types

One user type, and a very short list of jobs.

A door app that also shows reports is a door app that slows a queue. Everything an organiser needs to look at lives in Attendee Management instead.

User
3 of 3 screens
The door
One user, one job: get people through the door quickly and correctly. Anything else on this screen is a queue getting longer.
Preview as the user
- Scan and admit in under a second
- Works fully offline at the door
- A ticket scans once and only once
- Find a name when a phone is dead
- Live count of who is in

The limits

What this is not.

The same list we give for every app in the catalogue, because the fastest way to a bad project is a promise made in a meeting that nobody wrote down.

It is the door and nothing else
No reporting, no editing, no messaging. Those live in Attendee Management, deliberately, so the queue keeps moving.
It does not replace door hardware
It scans on standard phones. Turnstiles and access control are integrations we scope rather than assume.
It is not a safety system
The live count helps you manage capacity. Fire and safety compliance remain yours.
It needs tickets from somewhere
It scans tickets issued by Ticketing or Event Booking. On its own it has nothing to check.

Questions

Questions, answered plainly.

If yours is not here, ask it on the call rather than guessing from a pricing page.

Not covered here?

Ask a consultant directly. No form to fill in first, and no follow-up sequence.

Book a consultant All questions

Does it really work with no internet?

Yes, and this is the one requirement worth being blunt about. The door list is held on each device, scans validate locally, and everything reconciles when a connection returns. A venue basement is the normal case.

What if two doors scan the same ticket?

Devices reconcile with each other when they can, and a duplicate is flagged with where and when the first scan happened. Deciding what to do about it is a human job.

What about a dead phone or a lost ticket?

Find them by name and admit them manually, with the ticket marked used. Every event has this queue and an app that ignores it creates a bottleneck.

Can several people scan at once?

Yes, on as many devices as you like. There is no per-device or per-scan fee.

Do I get the source code?

Yes, on the same terms as every app here. No licence key and nothing that calls home.