Reality Rush

Watching your favorite reality show with your friends has never been better.

About

Reality Rush is an application that turns watching reality television into an interactive activity that promotes friendly competition with your friends.

Our Motivation

We realized that the reality television market is very niche and has room to grow when it comes to platforms that allow enthusiasts to come together. Watching television is used to spend time with those around you and can strengthen relationships, which is why we decided to use reality television and make it even better. Using the foundation of Fantasy Football, we realized that if we gamify watching reality television, because there are an incredible amount of individuals who already enjoy watching reality television, we would be able to make this even more of an enjoyable and bonding experience.

Even if one does not enjoy watching reality television, gamifying the social experience of watching television with your friends or loved ones incentivizes individuals to participate.

Social Setting

You & your friends

Our application focuses on the in-person environment of being with your friends but goes beyond that by including an asynchronous option so your friendships aren't affected by distance.

Design Process

Brainstorming

As we thought about what we wanted the experience of the application to be like, we looked at examples that would help us integrate a leaderboard and point system based on speed & could group individuals, hence, Kahoot & Slido.

Practice Version #1

Kahoot

Kahoot was an ideal platform to use for our prototyping experience as it incorporated a leaderboard & showed users what they got wrong after answering a questions.

However, it did not allow for separate teams to play (everyone would have to play as one large group) and it did not allow us to play videos in-between questions or incorporate questions with the platform.

Practice Version #2

Slido

Slido was a great option as it allowed us to have a Q&A section for users, a chat page, and the ability to release questions when we wanted to during the social experience.

Unfortunately, we could not embed videos within the platform and to truly use Slido's full functionality we would have to pay.

Why Google Sheets?

There was no learning curve in creating the prototype for our group, it would allow for us to mimic teams in groups with respective team pages, and it would allow for a leaderboard within groups and a global leaderboard.
Prototype V1

Google Sheets

For our first prototype, we asked participants to join a Google Sheets document where they would join their respective team's sheet & were prompted to answer questions between each of the clips that were played to which corresponding points were awarded per person as answers were put in.

At the end of playing the different clips, we totaled the participants’ scores and showed them their global leaderboard that showed the who got the most points out of all the teams.

Visit Prototype V1

Feedback from Prototype V1

Clips were too long

We created the first prototype thinking the experience needed to feel cohesive, resulting in us showing three 5-9 minute long clips.

Unfortunately, users were not engaged, were confused, and could not remember names of the cast members which resulted in skewed results.

To fix these different points, we shortened our clips, provided multiple choice options in Prototype V2, and provided the names of the cast so users were not confused.

Users could test answers based on the visible scoreboard = skewed results

Each team had their own sheet where team members could see each others scores. Users could then see how inputting a certain answer would increase or decrease their score, resulting in them changing their answers to gain the most points.

We decided to remedy this by creating more of an individualized gameplay so that users could not see others' answers in Prototype V2.

Possibility for Asynchronous game play

Although the application's main selling point was synchronous gameplay, users told us that they would like flexibility with when they could answer the questions.

This resulted in our group creating an option for asynchronous gameplay which we integrated in Prototype V2.

Why Google Forms?

Forms also did not have a learning curve, subjects' answers could not be changed based on what users see their friends putting down, and the answers were locked in after being submitted. Making the prototype as quiz also allowed users to see what their score was and what questions they got incorrect after submitting.
Prototype V2

Google Forms

For our second prototype we took a cleaner approach and decided to explore an Asynchronous option to Reality Rush, resulting in the two types of gameplay that are available on the app.

As part of the prototype, participants were separated into Asynchronous & Synchronous users and Asynchronous users preemptively entered their answers before the episode while Synchronous users answered “live”.

After participants submitted their answers, Synchronous users got their score back immediately while Asynchronous users got their scores released after the episode “aired" & and in the end everyone's score was released on the global leaderboard.

Visit Prototype V2

Feedback from Prototype V2

Showing right answers after answering the question

Because we used a Google Form in a quiz format, our system did not allow for users to see what the right answers were right after it was submitted.

We decided to integrate this idea into the final product so that users could receive feedback to their answers without waiting for the show or spoilers to tell them the correct answers.

A discussion board

In order to have fruitful asynchronous gameplay, we wanted users to have the ability to discuss among themselves within the application because watching television with your friends is just more fun.

A discussion board would also allow users to have social interaction with each other and chat about their shared experience.

A shareable link with a summary of the answers

Some feedback we got from the prototyping experience was that it would be great to have the ability to give users an option to share a link to direct individuals to the team's rankings & perhaps a summary of the questions and answers.

Ultimately, we decided to create a shareable link for users to invite members to join the groups they create for watching a show for our iteration but it is something to keep in mind for the future.

Final Design

Here we have our final design that is semi-playable with the major Home, Play, and Profile interfaces set up. Feel free to look through our various screens!

Visit our Figma
COGS 123 - Team MACS

Meet our team

We are seniors at UCSD that are excited to get out in the design world.

Please contact us if you have questions or feedback!
Mehul Sharma
Cognitive Science - Design & Interaction, '23
General collaborator, aided in the creation/distribution of research survey, conducted user research & user interviews, created Prototype V1 & V2 and led social experiences, created final mockups of the UI screens, and created the portfolio website.
Alexis Chin
Cognitive Science - Design & Interaction, '23
General collaborator, conducted background research and aided in creation/distribution/analysis of the research survey, conducted follow-up interviews. Helped with ideation and social experience of prototypes.
Carmen Li
Cognitive Science - Design & Interaction, '23
General collaborator, aided in the creation/distribution of research survey, conducted user interviews, designed wireframes and high-fidelity prototypes of the UI screens.
Shendo Yafuso
Cognitive Science - Design & Interaction, '23
General collaborator, aided research survey creation/distribution, general research, focused on prototype feedback and changes.