You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our QR codes are fairly basic for now!
We need to implement a better "ticket" UI that does include the QR code but also a lot of information!
Since the QR codes are generated both on the front-end and the backend and to avoid replicating this, we should create an API endpoint that, given the signature and the signed details will generate a PDF. This API will be used on the front-end from the keychain so it can be sent by email... as well as a from the websub worker directly.
The ticket should be in the PDF format and should include the following:
the NFT image
the lock name
the token id
the owner address
Once we have more specific metadata for events we will add them to the tickets (location, date... etc)
The text was updated successfully, but these errors were encountered:
Any reason to switch to PDF from PNG currently for QRcode?
PDF file won't be shown by default in gmail and other clients unlike PNGs. They also cannot be displayed on the frontend without pulling in dependencies so we will need the actual UI or PNG.
Our QR codes are fairly basic for now!
We need to implement a better "ticket" UI that does include the QR code but also a lot of information!
Since the QR codes are generated both on the front-end and the backend and to avoid replicating this, we should create an API endpoint that, given the signature and the signed details will generate a PDF. This API will be used on the front-end from the keychain so it can be sent by email... as well as a from the websub worker directly.
The ticket should be in the PDF format and should include the following:
Once we have more specific metadata for events we will add them to the tickets (location, date... etc)
The text was updated successfully, but these errors were encountered: