My app will be used in conjunction with NFC tags (each tag will be preconfigured by myself to open a predefined unique URL on the phone of whoever taps the tag).
Essentially, here is the flow I’d like to create.
1. Customer buys NFC Tag.
Customer taps the card to their phone to set up, it takes them to a page where they can sign-up and enter their details. Once finished their sign-up, it’ll create a virtual business card hosted on Bubble which they can edit etc.
Now they’ve set up, when somebody taps the card against their phone they are now taken to the virtual business card.
How would I achieve this in terms of URLs and data structures?
I have worked for an app that use similar pattern.
Basically, the “virtual business card” will always be the endpoint for the url.
You should first create the URL by creating a new “card” in your bubble DB. Create an url that point to yourappp.com/virtualcard/unique_id (from bubble unique ID).
When the user first tap the tag, it will go to the virtualcard page and check if the current page tag belong to someone (have a field that point to user DB for example). If not, show a popup or redirect to another page to create an account and fill their informations.
The virtual card is set to always display information. You just need a WF on page load that check if the tags is assigned to an account or not
