chamkank
commented
6 years ago For the hacker IDs, could we use the alphanumeric keys generated for the objects in Firebase? That way if they changed the value, it would probably be an invalid key in the database (which wouldn't be the case if we used something like applicant number). We have 144 bytes of programmable memory to use so I think it would fit?
d4l3k
We've ordered NTAG213 tags. https://www.nxp.com/docs/en/data-sheet/NTAG213_215_216.pdf
There's two main components to the system, "provisioning" and "tracking".
The tracking system will just read the hacker ID from the tag and then save it into firebase. This should track when and how many times it's been read for a number of different categories. These will be things like "Friday Dinner" or "Workshop: React". Displaying number of times will be useful for tracking things like seconds etc. It should be possible to add new categories either through the site or the app.
Provisioning will be how we assign the hacker ID to the tag attached to a specific nametag. Pretty much only phones have NFC so we'll need a phone and a laptop for registration. Most user friendly way I can think of is to setup firebase messaging to send a message from a laptop to the app and then tap the phone against the card. This should probably display the name on the app to eliminate any lag or errors.
We might consider password protecting the NFC chips but it's probably unnecessary and might be nice to give people NFC chips to play with later.