For feedback, we interviewed 3 users about their user experience and continued to interview these same 3 users for the following prototype iterations: storyboard and Invision Studio Wireframe. We originally planned to have 6 users test it, but given the time constraints and being distant, we were not able to gather 6 users. We thought that having the same users test our prototype would be beneficial because they would go through the prototype iterations process and see the "before" and "after" effects of each prototype iteration stage.
The longevity of having the same users be part of the prototype iteration process is highly valuable for us since they can provide constructive feedback.
Standard Questions We Asked
How is your user experience?
Do you like any aspects or concepts about it?
Do you dislike anything about it?
Do you have any difficulties navigating through the prototype?
Can you think about any improvements that can be made?
Storyboard Prototype Feedback
For our storyboard prototype feedback, some things that the users were confused about were whether having an account is necessary, how the results of whether the user is a good listener will be displayed, and what kind of video the user will be watching.
We see why an account would not be necessary because some users mentioned that they would just want to go onto the website without making an account. They wanted to just watch the video and get the results immediately, so they can work on expressing their facial gestures to make it seem like they are good listeners.
It could be said that maybe this website is not complicated enough for users to create accounts. Accounts are meant to save a user's individual information. There are not enough information or features to make use of accounts.
The display of the results of whether the user is a good listener was not clear because the user was not sure how they were being assessed on their listening skills while watching the video.
So, this made us incorporate an instructions page to inform the user of what the user is going to do. Without the instructions page, the user would not know what they are getting themselves into without being told beforehand. It is helpful to have an instructions page that informs the user and that they will be recorded while watching the video.
A suggestion that we wanted to add was the different kind of themes for the video, so the user can pick one of them to watch. So, the point of our final project is to assess people's listening skills based on their facial expressions through OpenFace while watching the video.
The video contains an avatar telling a story based on the theme the user selected. This avatar is meant to simulate as a real person talking to the user. The themes also represent the main emotion being evoked while the avatar is speaking.
Invision Studio Wireframe Prototype Feedback
Do you like any aspects or concepts about it?
"I like on how the layout makes it simple and easy to use."
"It has a clean and cute design."
"It's pretty straightforward... able to click on buttons to go where I need to go."
Can you think about any improvements that can be made?
"Maybe have an account to monitor and keep track of your listening scores."
"Make more features to justify what a good listener is... like reciting some info back of what I just watched. "
"My facial cues shouldn't just account for being a good listener. There's more."
After getting feedback from the storyboard prototype, an instructions page was included in the wireframe. Having instructions to refer to helps the user get notified about what is going to happen onward, as the user tests out the prototype. Another aspect that was included for the wireframe prototype was being able to select 4 different themes: happy, sad, angry, and surprised of the video for the user to watch. The theme selection is meant for what video the user chooses to watch, in which the avatar will tell a story based on the theme the user selected.
The suggestions of what kind of improvements that can be made is helpful. What the users' suggested are future improvements, which are extended features of the project. So these features can be implemented later on if we wish to continue to add more to our final prototype. It would be nice to have an account to monitor and keep track of listening scores for each user, and having voice be involved with reciting information back to the avatar. These are future improvements that can be kept in mind for making a better prototype with a lot more functionality.
As a result, for our final prototype, we could not test it properly with the users because we had a difficult time combining the front-end and back-end. We did not have experience of connecting the OpenFace back-end with the front-end of the website. So, another future improvement that can be made is figuring out how to develop a web API to access the user's camera to record the user while the user watches the avatar speaking video, have this recording be sent through a server to OpenFace, and getting the results from OpenFace to the front-end website to be displayed to the user.
These results would give feedback as to how the user's facial expressions changed as they listened to the speech. Other possible features we wanted to include were a quiz that the user could take before watching the speech to determine the skills that they personally value in a good listener. Overall, the prototype does not fully serve its intended purpose, but with additional time to make adjustments, we believe that ListeningBot could be used as a resource to help people self-reflect about their own listening skills.