natHACKS 2024

natPass

One scan to check in a hacker.

Role
Co-president, NeurAlbertaTech
Team
Hiritikk Kumar · Jihoon Og (badges)
Built
One night
Stack
Next.js · Baserow · SignNow
natPass in check-in mode: a hacker's details, and a checklist showing registration, payment and waiver all confirmed

01The problem

Check-in ran on spreadsheets. Four things to check for every hacker, by volunteers who were new every year.

Before

Accepted
Paid
Waiver signed
Needs on the day

Four sheets, one at a time.

After

  • Accepted
  • Paid
  • Waiver signed
  • Needs on the day

One scan.

02What we considered

  1. Keep the data where it was

    natPass reads straight from Baserow.

  2. No typing

    Hackers got a QR code by email. Volunteers just scan it.

  3. Read-only by default

    You switch into check-in on purpose.

  4. Don't chase people

    Missing waiver? natPass emails it.

“okay sick I think thats everything for the mvp.. now to get 10 hours of sleep in the next 3 hours”

The commit that shipped it

  1. First commit
  2. MVP done
  3. Asleep
  4. At the hackathon

Volunteers stopped checking four things.

They scanned a code.

03Looking back

Start earlier. Stress test it with a fake line of hackers, instead of deploying it the morning of.