Team Christian White Michael Peterson Filippa Karrfelt Nathan Schager Helen Fang Varis Niwatsakul Minna Xiao

Overview of Problem Interpreter’s Problem: Low motivation to become a qualified ASL interpreter due to the technical barrier to entry. Deaf Users’ Problem: Difficult to share live moments with loved ones because he/she is not the intended audience

Solution Interpreters’ Solution: Engage in passion projects (interpreting live music events) that do not require official certification. Deaf-Users’ Solution: Give them a more interactive/enjoyable live event experience.

Presentation Outline Concept Video Design Evolution Current UI description/demo Points for improvement

Concept Video

Needfinding Talked to people throughout the mental/physical disability space, one of my team members interviewed Alyssa, who has deaf parents. We were intrigued by the idea that deaf/hard of hearing people had less interactive live event experiences because of their disability, so we sought to solve this problem through our app.

Low-Fi Prototype We have two screen flows, that follow from a login screen - one for interpreters and the other for the concert-goers. You can see a few things that we ended up getting rid of - choosing genres, so we put a list of upcoming concerts first. Also were confused about voting for interpreters, so we made took out the swiping feature there.

Medium-Fi Prototype Users said they preferred to see events listed by how soon they were approaching, and thought that having a countdown would be more beneficial than how many friends they knew who were going

Medium-Fi Prototype Cont’d Users thought it would be difficult to have one take to get their submission right, so wanted a chance to make a video, try it and then submit it

Through our HE’s, we found that having a timer was not as helpful as we thought, so we just threw in the submission deadline instead to make it simpler. Also although the kanye and rihanna concerts were on the same day, gave separate cells in our hi-fi to standardize

Also through HE’s, we found that having a countdown didn’t seem to serve much purpose here, so we again put the deadline. You can see this on the last screen as well, but here you can see that we made the bar on the bottom simpler, because all of those images seemed confusing and again not all having a clear purpose.

Our big design decision here was to take out the create button entirely and just leave an upload button. This took out confusion for users about the difference - were confused because didn’t know whether create would give them one or many opportunities to make a submission, and tbh we weren’t 100% sure either. Now we allow them to go into the videos on their phone and upload from there. That way they can practice as many times as they want and just upload the final copy.

Simple Task Find upcoming concerts in your area to submit a video for. Chose this task because interpreters want to be able to use their skills to get on stage with some of their favorite artists by submitting a video.

Simple Task Demo

Medium Task Find and vote for your favorite interpreter out of the pool of submissions. Chose this because concert-goers want to have some input on who is signing at the concert they attend and they can thus go and vote.

Medium Task Demo

Complex Task Engage and establish relationships with your favorite interpreters. Chose this because if concert-goers have a good experience with one interpreter, they want to coordinate with them to see which concerts they both will be attending.

Complex Task Demo

Hard-Coded Features Concert data Tracklist data Video submissions Track mp3’s

Ideas for future enhancement Interpreters can create profiles concert goers can vote for and interact with them Dynamically get list of upcoming concerts Some way of getting artist setlists Connect to iTunes to get tracks Some way of communicating with concert networks To actually get interpreters on stage

Summary Finished: UI, Taskflow Unfinished: Hard-coded features, logistics