Strava Planner

Strava is a mobile fitness application that works in conjunction with GPS data to track analytics on route-based activities including running and cycling. Their purpose is to serve as a social platform to encourage athletes around the world to continually work towards improvement and accomplishing their goals.

This project is a feature design proposal created in a senior level user interface & experience design course. The objective was to design a potential feature for a pre-existing application, working within their established visual language, patterns and workflows.

In order to better understand the existing application demographic we performed a remote interview with an active user of the platform. Additionally, we conducted a survey consisting of 10 participants (ages ranging from 20-31) to examine their current relationship with their physical activity.

In order to better understand the existing application demographic we performed a remote interview with an active user of the platform. Additionally, we conducted a survey consisting of 10 participants (ages ranging from 20-31) to examine their current relationship with their physical activity.

From the research and insights collected, we wanted to create an extension to Strava that would be targeted to individuals new to fitness or are looking to become more engaged in a physical lifestyle.

Branching off of Strava’s mission, which is to serve as a social platform to encourage athletes around the world to continually work towards improvement, we framed our design opportunity around the concept of answering the question,

By having an understanding of the direction we wanted our design to move towards, I led a brainstorming session to ideate potential feature designs. Upon listing everything our initial ideas, we reviewed each individual proposal and expanded on each. From there we selected the most promising feature and moved forward to further iterate on that concept.

Utilizing the existing visual language, patterns and interface that Strava currently implements within their application, we created a grey-box wireframe to get a clear sense of the design of our proposed feature and visualize the user interactions

Strava Planner seeks to help individuals stay motivated in the beginning of their fitness journey. Getting into the routine of exercising is challenging, especially when navigating through the struggles alone.

For this reason, the Planner’s purpose is to help users keep themselves accountable through training in a digital group setting and set time to devote to fitness by planning ahead.

The Planner is accessed by individuals through a newly introduced section on the main profile. From there, users can create a new event and enter the details regarding the desired date, form of activity, and targeted end-goal. Individuals also have the ability to give the event a human touch and name and describe the event how they chose.

The host can select who to invite to the planned event and once they have been selected, event details are sent out to each individual. However the invitee has the option to accept or decline invitations they are given.

When the time comes for the event to begin, each user must click the “Ready” button to be placed into the waiting room. All participants are able to preview who is present and who is not. The host can decide if they want to wait for the entire party before beginning or proceed without them.

While participating in the group activity, users can constantly view their progress, see who is still actively working within the party and exit at any point they choose. Upon completing their session, users are given an overview of their performance in comparison to the event goals.

This project was the first time where I had to work within a brand guideline. Thought at times I felt limited as I tried to conceptualize layouts, it was important to begin working with constraints as it will prepare me for the scenarios I don't have full control over the style guide. I found that the use of Strava's brand guildelines help me and my team decide which of the iterations were the strongest as it would natrually fit into the existing interface.