Embedded Files
Data Concerns
Data Concerns
Before even getting to the room building interactive, I wanted to take a stab at fleshing out the saving the artworks portion of the experience. One huge initial consideration I was thinking about was the approach when saving artworks/museum objects since the works would need to be associated with a profile of some sort. I didn't want to have the typical log-in form or OAuth system for these main reasons:
A "Create Account" flow is bulky and would detract from the ideal seamlessness of the envisioned experience. At worst, it could deter visitors from trying the experience out if it's they need to create an account first.
Visitors should not be barred from trying out the experience once by needing to create an account if there isn't a need to revisit their account later
Thus I settled on using cookies and unique IDs to save a visitor's curated collection. Using cookies allows visitors to save data without needing to sign up, and I intend to tell the user about what the cookie is used for.
User Journey v1
User Journey v1
Initial QR Test
Initial QR Test
Since I wanted the main mechanism of saving works to be done via the phone and QR codes, I needed to test if cookies would be preserved correctly on the mobile browser when navigating to a link via a QR code. I particularly was interested in the case where a visitor would scan an artwork, save it to their collection, and then close the tab - would their profile and collection persist?
In this initial prototype, I created a test to see if I could create a cookie that would be persisted in the browser once I close the tab. Thankfully it worked!
Apple iOS devices uses its Safari browser to open up websites linked via QR code. Hopefully visitors don't have this feature turned off (I can check wit the code: navigator.cookieEnabled), but if they do, I'll just include a message for them.
QR code for my deployed rudimentary cookies test prototype
Page updated
Report abuse