Efficient QR Code Scanner Fix: Streamlined Event Check-InEfficient QR Code Scanner Fix: Streamlined Event Check-In
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
I fixed the QR Code scanner issue we were having. Created a new event to test with. #configmakeathon
The scanner no longer verifies an already verified guest and stops updateing the row with the same data over and over again.
Here's how every scan outcome now behaves:
Success — green modal with the guest's name, email, tier, quantity and Crowd9 ID. Ledger row is added. Dismisses after 2 seconds.
Already checked in — amber/yellow modal saying "ALREADY CHECKED IN" with the guest's name and a note that they've been admitted. Ledger is not updated (no duplicate row). Dismisses after 2 seconds. 3.Invalid QR (bad JSON, wrong event, not found) — red modal with "INVALID QR CODE" and a specific reason. Ledger gets a rejected row only for structural failures (not duplicates). Dismisses after 2 seconds.
The server now blocks duplicates at the source — a second scan of the same registration_id returns a 409 with code: "ALREADY_CHECKED_IN" before any write happens.
@figma @miggi @contra #buildinpublic #makeathon @tranmautritam @_radnolan @thedesignely @janm_uiux #figmamakeathon
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started