Shane B., Esther K., Curtis S., Jennifer W. evolve Shane B., Esther K., Curtis S., Jennifer W.

Value Proposition and Problem/Solution Overview evolve: Get connected. Get motivated. Get fit. Many people struggle with maintaining the motivation for their exercise goals. evolve drives people to reach their fitness goals by harnessing the power of both peer pressure and community through personalized group matching, a goal tracking system, and a group communication platform.

Three Tasks Find a group of people with the same/similar goal (simple): fill out the survey, customize your challenge settings, and join a group Track your progress towards the goal (moderate): upload a photo of your workout to complete your check-in for the day Communicate and share experiences in a group (complex): read the group chat and send an encouraging message to another group member

Revised Interface Design: All Sketches (This is an overview of all of the sketches that we did. Major changes will be discussed in the next few slides.)

Revised Interface Design: All Sketches (continued)

Revised Interface Design: Major Design Change 1 We got rid of the group members’ avatars surrounding the countdown timer because several participants from our low-fi prototype testing noted that they looked too clickable and distracting. We also added the concept of rest days and some progress indicators (a progress bar towards the weekly goal as well as an behind/on track/ahead status message) to provide real-time feedback to the user and made the check-in button larger so that it was easier for the user to see and click.

Revised Interface Design: Major Design Change 2 We separated the challenge-related information from the group members-related information by using tabs. We also plan to add a tab to see the list of group members and view their detailed profiles. We did this because we noticed that our low-fi testing participants had difficulty performing the check-in task. We thought that breaking all of the functionality down into multiple screens would look less busy and crowded and make it easier for users to figure out how to interact with our system.

Revised Interface Design: Major Design Change 3 We changed the potential groups carousel into a more detailed customization form in order to give the user greater control over their challenge. Based on feedback from our low-fi testing participants, we noted that the user may want to consider factors other than simply the number of times per week when deciding which challenge they would like to join. By asking for this information in advance, we can take it into account during the matching process.

Revised Interface Design: Medium-Fi Task Flow 1

Revised Interface Design: Medium-Fi Task Flow 2

Revised Interface Design: Medium-Fi Task Flow 3

Prototype Overview: Prototyping Tools Tools used: Adobe XD, Marvel How the tools helped: Both tools had a relatively smooth learning curve. The interfaces were simple and intuitive to use. It was easy to share and reuse assets that were common across screens in Adobe XD. Marvel supported simple animations via various transitions and automatic timing. How the tools didn’t help: Adobe XD’s layer system was very difficult to organize and navigate. Marvel’s interaction and animation features were quite limited and we sometimes couldn’t get the input fields, pop-up notifications, and page transitions exactly the way we’d envisioned. Neither tool was easy to use for real-time collaboration.

Prototype Overview: Wizard of Oz Techniques After the user fills out the survey, they are matched to a group by our AI system. Since we did not implement this back-end system (due to lack of time and AI background, no database populated with other users that the user can be matched with), the group that they are matched to was predetermined. Right after the user initially joins the group, the warning notification for not checking in automatically appears after 1 second in order to demonstrate the remaining rest days (the number of days in the week that the user can afford to skip checking in) feature. In reality, this notification would not pop up immediately after the user joins the group in the beginning; it would only be shown to the user if they actually did not check in the previous day.

Prototype Overview: Hard-Coded Features All input fields (the survey fields and group chat messages) Challenge task (4 days per week for 4 weeks, 30 minutes per week, starting today) Group members’ names and avatars Time displayed on the countdown timer (always 15 hours and 30 minutes) Check-in photos for the user and another group member It was necessary to hard-code these features because Marvel makes it complicated to save input fields, so features that depend on user input, such as the challenge and group that the user is matched to, needed to be initialized in advance. Other features, such as the countdown timer and mobile camera, would have been difficult to completely implement in the amount of time provided.

Prototype Overview: Limitations/Tradeoffs To focus on the main task flows, we left out features such as an onboarding tutorial on the very first screen, logging in, detailed profiles for the group members showing their past check-ins and current status, the option to check in by syncing activity with a different fitness app or device, changing the theme of the app to “high-achiever” mode if the user completes all of their check-ins for the week, and some sort of introductions feature to help the group members initially getting to know each other. Due to Marvel’s limited features, some gestures and animations were simplified. For instance, buttons should change in appearance on hovering to indicate clickability and notification animations could be more of a popping out rather than a simple fade.

Additional Prototype Screenshots Additional screens: warning notification for not checking in automatically appears after 1 second to demonstrate the remaining rest days feature

Medium-Fi Prototype Links Marvel link README Embedded on website link