The Consentful Fly

Part One

I usually start out with a ton of questions before I attempt a project. In the dropbox link, you'll find some the questions that I used to frame how I want to structure this project. https://www.dropbox.com/sh/n5knq46r5248nd2/AADD2CkPPFbGZOJV71FLg50ta?dl=0

Making the Code Consentful

Consent can be conveyed in a myriad of ways. As much as the design of the interface helps aid how users interact with it, the microcopy is also a huge component.

Microcopy is all the small bits of informational copy that guides users along a journey. They inform you of important info too. Microcopy has a hand in consent just as much as design does. For this project, I wanted to focus on the copy too.

Of course, when you run the program, the browser asks if you'd like to use your webcam. Technically, this could be seen as consent. But, I think consent is only helpful as it relates to the person's life. Asking to use the camera is one thing, but going further and asking if it's "okay to share your face and surroundings" really preps the user for exactly what will happen. It puts what may be a risk on the table for the user to decide. Asking a question that directly references the risks is important for the user to grasp the effect of using the product. Only referencing the webcam only feels like you're asking to use the product in general. If someone opens an app on their phone, it's clear they want to use it. The copy should always have some form of risk aversion in my opinion.

Flow

When the user starts the code, they're welcomed with an example image of the filter. I think it's helpful to show them exactly what will happen before they commit too. Once they press yes, the camera will start and will be displayed in the canvas. You'll always be able to turn it back off by pressing "no" too.