Consentful Interface

Description

Building upon the Experimental Camera, add a consentful interface. Using the F.R.I.E.S model as a reference, I tried to add aspects that ask for consent in a freely given, reversible, informed, enthusiastic and specific manner. Unlike the Experimental Camera, the Consentful Interface describes the project in more detail and explains what the user should expect at the end. There is always a button to go back at every stage of the interface so the user does not have to permanently commit to the decisions made.

Design Process

I organized the code so that it would switch scenes with the use of buttons. On the first scene, it begins with the name of the project which I called "Elusive Smile" and has a button that can be pressed to proceed. The second scene is a description of my concept, where it informs the user with more information. There are buttons to go back, and to continue. When the continue button is pressed, the third scene asks for the user's consent to get access to the device's camera. It also specifically explains what the camera is used for so that the user is aware of what to expect. This, in regards to the F.R.I.E.S model, refers to the specific and informed criteria. In order for the user to be willing to give permission to the camera, I thought it was important to clearly outline what the camera will be used for. Furthermore, there is a checkbox to show the user's consent and it will only proceed to the next camera scene when it is checked. On the camera scene, there is a button to go back, so that the user can reverse his or her decisions, rather than having to close the window or refresh the page.

Reflection

The consentful interface recontextualized user interaction and experience of the experimental camera. I had to take consideration into how the user will approach the project and ways to inform the user so that the user would be enthusiastic and willing to provide permission to the device. It created more processes to get to the final result, but the experience of knowing what to expect and then trying it out was more fulfilling. Although there may be instances when unknown surprise could be a significant component to the design, I think that those that require permission to use certain privacy related functions, it is better to be fully aware before committing an action. Also the user interaction changed with the back buttons because the commitments were not permanent and could change throughout the experience, which I wish was more commonly found in other interfaces.