Consentful Interface
Design Process
I created the following flow chart to inform how the user would interact with a F.R.I.E.S. compliant interface:
From there, I created the initial (rough) sketch for the consentful interface in a separate p5.js file.
Once working out the logic in JavaScript, I duplicated my original Experimental Camera, and plugged in the consentful interface code into a new file. The biggest challenge for me was getting the camera element to show within the structure of switch statements and various functions. Additionally, since the capture also functions as a DOM element and my camera dealt with filter overlays that were images, I had to spend some time figuring out layering.
Reflection
The above interface responds to the F.R.I.E.S. model in the following ways:
- Freely Given- The interface does not manipulate users into a decision or action that they normally wouldn't do.
- Reversible - On the camera screen, there is an option for users to change their minds and revoke camera access.
- Informed - The interface uses clear and accessible language to inform users about the Nostalgia Camera, rather than burying this information behind layers of fine lines.
- Enthusiastic - Users do not have to give their consent in order to experience the Nostalgia Camera. The filter gallery option on the disclosure page depicts this.
- Specific - This consentful interface only uses data the user has directly given, the use of the camera device, not data acquired through other means.