CONSENTFUL INTERFACE

DESCRIPTION

The main goal is to get permission from the user for access to webcam. As well as give the user a heads-up on the closed eyes interaction. So I set up two permission pages. Agree on both to experience the camera. Diagree to both or one of the two will not.

DESIGN PROCESS

Initial flow chart:

Then I find it to be a little tedious to set up the agreement scenes in two different stages. So I set up the two scenes following by one another. The user goes through the alert all before the camera turns on.

Refined flow chart:

In terms of design of the interface. I try to make all parts cohesive. So I take some visual elements from the camera design and put into the permission administration pages. Color palette keeps consistent as well.

Landing with the page asking for webcam permisson:
If the user clicks "YES", with move to the next page, which asks permission for closing eyes experience:

If the user clicks "NO" on any of the above pages, will direct to the following page: Users can click "GO BACK" to go back to the first page if they change their mind here.

When permissions are given, the user then can experience the camera. And while they experience, they can change their mind and go back to the first page anytime by clicking the "GO BACK" button below the canvas.

REFLECTION

Link to Final.

A lot of times Apps and websites are not asking for permission to a lot of things. And I find myself getting used to it before this project. Sometimes I forget the fact that they should ask for my permission before they set up the UIUX such ways. Because the majority of Apps are doing the same thing. This project also set an alert for me as a designer. To be mindful about the issue in my future practices.