Closed neilsarkar closed 6 years ago
Oh also I don't think we should make it hotpink
, just leaving the option in there in case u want to fux w the color
Lmao should definitely leave it hotpink
Aren't we supposed to be generating the QR codes serverside? Then I figured we need to store some sort of byte info in the db attached to the user? We want the QR code to be the same for the entire lifespan of the user's row in the db, no?
When you say generate the QR code serverside, you mean generate the URL right?
Bc even if there's a slight variance in the QR code between clients/backend, as long as QR code readers resolve it to the same url it should be chill.
And we already have a unique url for the user's lifetime based on the user id, which is what we're using here.
The missing piece to make everything work is that we need to do is create a scanner app that reads the QR code, grabs the user data, and shows the bouncer a picture of the person so they can make sure it's the right person and that they have access.
Like most scary things, ended up being not a big deal at all. Found this interesting though, the qr code is rendered as javascript injected into a canvas tag in a webview. Loading time/performance seems totally fine. This might be a good path forward to utilizing your web skillz for fussy animations:
https://github.com/cssivision/react-native-qrcode/blob/master/lib/Canvas.js#L29