A QR code conundrum for anyone interested in weighing in.
In tandem, I have also been building an associated Cashback Web App (that I need to link to the mobile app somehow - currently two separate app projects - eek!).
The Web App platform offers greater functionality in that it enables my clients (Partners) to create dynamic shop fronts and advertise their cashback deals (Products) from uploaded product data. It also allows customers (Users) to create dynamic user profiles, where they can explore Partner deals, track their cashback accruals and recent purchase history etc.
The Mobile App is exclusively user-facing and is really just for scanning QR codes on receipts in-store and displaying simple cashback and product data at a glance. For the in depth analysis, the Mobile App would redirect users to the Web App.
I’ll explain the User journey for the QR Code Scanning and then the problems that have arisen. Hopefully some of you wise and talented people might have some ideas about how to attack this one!
1 - User visits the Partner store in person. They do their shopping. They open the Mob App at the checkout.
2- They pay for their shopping and are presented with a receipt that displays a QR code. They open the Scan Page and click the “Scan” button, activating their phone’s camera. They scan the code. (NB: I am not using a dedicated scanner plugin for this, just the device’s native camera).
3- A successful scan redirects the User to a dynamic landing page (yet to be built), that will populate with the data extracted from the QR code. Purchased products that match the Product ID’s uploaded by the Partner on the Web App will be displayed, along with associated cashback rates and amounts accrued.
4- User taps a button to accept cashback terms, triggering a return to the home screen where they can now see their cashback info displayed. The original QR code (or access to cashback landing page) would also be rendered closed, thereby avoiding fraudulent cashback logging from an already scanned receipt.
Problem #1 - Partners will need to generate a QR Code for each User’s unique shopping basket. They will have to do this at checkout. Each QR code generated is obviously going to be different with each unique shopping basket. Also, it may include both cashback product data and non-cashback product data that the Mobile App needs to be able to differentiate between.
Q: How might I enable retail Partners to generate compatible QR codes at checkout, relative to not just each User’s unique shopping basket but also my backend database? Would the Partner’s inventory management software need to create it? Would my Web App need to create it and be connected to their inventory management software through an API? If yes, is there an API that is recommended here or will it be contingent on the specific inventory software used?
Problem #2 - For the scanning itself, the camera seems to work fine on my iPhone 11 (iOS 15.0.2) when accessing the Mob App in the Google Chrome browser. I have read in other posts that some people have had issues getting this feature to work once launching native app versions.
Q: Is this a problem I should prepare for by building in a QR code scanner plugin from the get-go, rather than simply opening a smartphone’s native camera (which seems way easier)? Would this be the failsafe to allow other, perhaps older devices to access the scanning feature?
Problem #3 - In case you hadn’t already guessed, I am a Bubble Noob. It has taken me some time to get to this stage, since I’ve been trying to learn on the job!
So if anyone has any thoughts/solutions to some of the aforementioned, please feel free to phrase these as if speaking to a small child There shall be no offence taken, I can assure you!
Ben from Treea