Milestone 8: Final Presentation (6/4)



Slide Deck

Poster

Cliq Source Code

Check out our source code!

Milestone 7: User Study II (5/29)

Milestone 6: Functional Prototype II

Main Changes to Initial Prototype

New Features

Implementation Progress

You can track our progress on this excel sheet.

Milestone 5: User Study

Introduction

Motivation

After discussing our app’s features with some of the CS247 staff, we decided that testing different methods and timings for notifications was important in determining the potential success of our app. Because our app is a mobile-optimized web application, our notification methods are essentially limited to email notifications and SMS notifications. We decided to test both of these options to determine which yields higher user satisfaction and quicker response times. We also really want to simulate our testing in the most realistic way possible, in order to get the best feedback among different user groups. We decided to send out notifications as previously described to users at different times of the day, and vary our user groups (close friends, long-distance friends, mere acquaintances) in order to produce the most reasonable data.

Questions and Hypotheses

1. Which method of notification do users prefer? Which method of notification produces quicker response time?
Hypothesis: Users will prefer text-messaging over e-mails because it is faster and requires less overhead for the user.

2. Do users prefer to be notified when their competitors post a photo?
Hypothesis: Users will prefer to be notified only after all competitors have completed the round because this ensures that all participants play their round.

3. Do users prefer to be notified at a random time or a time that they had mutually agreed to?
Hypothesis: Users will prefer to be notified at a random time because it adds a level of uncertainty that’s exciting!

Methods

Study design

We decided to recruit our friends for this user study, and here are the four different cases: We thought this was a comprehensive group of real user cases.

Milestone 4: Functional Prototype 1 (5/8)

We created an initial prototype of our mobile web-app, Cliq. Further details are below.

Check out our prototype!

Features Implemented Thus Far with Rationale

Tasks left to complete in the future in order of priority

You can see our progress on this excel sheet. The first section contains our tasks for this past week, and the second section contains tasks we need to complete in the future, in order of priority.

Milestone 3: Wizard-of-Oz Testing (5/1)

After meeting with our mentor-coach this past Tuesday, we decided to take a slightly new direction with our CS247 project. Our new project idea is similar to "FamCam", our photo/video timeline sharing app, but we have made it more of a photo sharing "scavenger hunt" type application. Details can be found in presentation embedded below. We're really excited about it and hope you like it!



And here are some of the wonderful photos and videos our participants captured!

Cliq (Prototype 1)

Prompt: Take a photo with somebody named Joe.




PromptMe (Prototype 2)

Prompt: Take a video of yourself dancing for five seconds.





...and the unexpected twerk:

Milestone 2: Storyboarding (4/24)

Our skit can be found at the bottom of the following document: Idea Brainstorm Google Doc

1. Storyboard - Communicating With Family Members ("FamCam")

2. Storyboard - Music Recommendation Communication ("ZShare")

3. Storyboard - Communicating Questions in Lecture

Milestone 1: Team Formation and Ideating (4/17)

Idea Brainstorm Google Doc

1. Communicating With Family Members

Communicating with your parents on a weekly basis can be challenging. We want to make this process friendlier and easier. Here is the general flow of how this mobile app would work:

  • Student initially enters his/her general availability times for each day upon sign up
  • Every day at some point during the user's window of availability, the app would remind the student to take a picture or record a short video with a description.
  • This video would then be directly sent to the parents’ emails
Target Users: Mainly college students

From our personal experiences, we see that many students have trouble finding time to communicate with their parents weekly, much less speaking with their parents on a every-day basis.

Communication: Communication between kids and their parents.
Context: College students away from home

We are mainly concerned about college students who are going to school away from home. Especially at Stanford, many students are from out of state, and have trouble staying in touch with their parents.

2. Carpooling Communication

Coordinating carpooling or picking up a friend can be annoying. It would be great to somehow send a quick message, piece of information, or media while driving that is safe and is an accurate description of the driver's location. Here is the idea flow:

  • Before driving, you open your app
  • Your phone already immediately begins recording your location, and once you’re 5 minutes away from the destination, it sends a pre-recorded video/audio clip or message to the friend at the destination locatio.
  • Your friend at the destination location gets this message and is prepared for the pick-up and walks outside just in time without any wait time for either party
Target Users: Anyone who drives and/or carpools

We have all have had experiences when we needed to arrive somewhere on time and picking up a friend or group of friends up took much longer than necessary due to miscommunications that resulted in wait time.

Communication: Communication between a driver and passenger(s) at the destination location(s)
Context: Anytime

When you’re picking a friend up on a date, to go to the movies, or to go the gym - you name it. If both friends are using our app, this should eliminate the potential wait time for both parties.

3.Communication Across Cultures/Languages

Most people enjoy meeting new people from different backgrounds, but there can exist a language barrier that requires an extra step in communication, whether it be via a translator, Google translate, or a dictionary. We propose to build a chatroulette-like platform that connects people across cultures by having what you say immediately translated into subtitles on the other person’s screen. They will then respond in their own language, and you will get the subtitles in your own language.

Target Users: 2 or more people that speak different languages
Communication: Communication with a language barrier
Context: Anytime, using our app

This could happen when you want to speak with another person that is not fluent in your language, or if you just want to meet new people that are foreigners.

4.Music Recommendation Communication

Optimizing the music recommendation and sharing experience is something a variety of applications/social networks are continually working on. SoundCloud, Spotify, YouTube, and last.fm all have social network-type features such as listening-activity sharing, music listening timelines, and music listening data aggregation, but it seems as if no one application has perfected the music recommendation experience. Sharing music with friends who have similar tastes seems to be the most efficient way we share music now but music listeners often don’t have time to listen to an entire song, so we decided that we’d digitalize and optimize this process. Here’s how the app would operate:

  • You create an account with the app and add your favorite music artists and Facebook friends
  • You can send music/music video blasts using APIs (SoundCloud, YouTube, etc) to friends/friend groups that combine short < 30 second clips into one < 1 minute audio/video clip
  • You can view a timeline or received messages that have these short clips
Target Users: Avid music listeners looking for new music recommendations from friends
Communication: Communication via audio/video clips that combine into an optimized music recommendation experience
Context: Anytime, when you want to share music with friends and neither of you have time for music discovery