FITBIT

Historical data searchability made easy and intuitive.

Team

Project Mentor &
Peers

My Role

End-to-end
UX/UI Designer

Tools

Figma, FigJam &
Optimal Workshop

Timeline

80-Hour
Solo Project

Project Background & Key Features

Fitbit, a leader in the health tracking device sector, has a powerful app and what makes it so approachable is its simple design.Even still, there are repeated complaints from Fitbit users having trouble finding their historical data.
Fitbit would like to add a feature to its free & premium app dashboard, giving users the ability to quickly and easily find specific date ranges.
DISCOVER

METHODOLOGY

  • Product SWOT Analysis
  • Guerilla Testing & Eye Tracking

OBJECTIVE

I've been tasked with making data searchability easier and more intuitive on the app.

CHALLENGES

I’d like to make finding historical data in the Fitbit App more accessible.

SOLUTION

Conduct guerilla testing to learn how people navigate & where they expect to find certain information to provide an intuitive solution.

STUMBLING BLOCKS

I do not own many of these devices. Downloading the app wasn’t helpful as there was no data input. I relied heavily on google search results and a few people I knew who owned some of the devices mentioned.

Product SWOT Analysis

I compared 4 of Fitbit’s major competitor’s  to see how have solved the same problem. Going by the screenshots I managed to find, it seems these apps offered a more intuitive way of looking up historical data.

Polar Flow

Company: Polar
How did they solve the problem:

Day, week, monthly overview
Screenshot:

Apple Fitness

Company: Apple Fitness
How did they solve the problem:

Day, week, monthly calendar
Screenshot:

Garmin Connect

Company: Garmin
How did they solve the problem:

Daily, weekly, monthly & yearly calendar
Screenshot:

Samsung Health

Company: Samsung
How did they solve the problem:

Daily, weekly, monthly & yearly calendar
Screenshot:

Conclusion

In summary, because all participant’s struggled to find this data, there was room for improvement.
DEFINE

METHODOLOGY

  • Personas

OBJECTIVE

Since the product is a data tracking device, there can be many different personas. I focused on the individual who might be dependent on accurate & easy to find stats.

Personas

Two distinct users were defined during interviewing. The leisurely person who likes to view daily activity and the athlete that used the device for training. I focused on the latter.
IDEATE

METHODOLOGY

  • Information Architecture

OBJECTIVE

The guerilla testing & eye tracking conducted at the beginning proved to be helpful in determining how to approach the solution and where to allocate key elements.

Information Architecture

The user flows shows the screens a user will navigate to find data from the past.
PROTOTYPE

METHODOLOGY

  • Style Guide
  • Low Fidelity Wireframes
  • High Fidelity Wireframes

OBJECTIVE

Using the existing UI, I needed to add the new feature.

UI Branding & Style Guide

I used Fitbit’s existing UI Kit since I was only adding a feature, but included it in the study to show the new components that were created.

Wireframes

Low Fidelity Wireframes

The first approach to the problem was to add an icon in the navbar leading to a calendar. I also pooled all of the data so user’s could view it all in one place.

High Fidelity Wireframes

Using the brand colors, hi-fi wireframes were created. An icon was added to the navbar as well as a calendar with daily activity overview. Ability to view various stats that were embedded under several pages were brought to the forefront with the option of viewing a graphical chart.
EVALUATE

METHODOLOGY

  • Usability Testing
  • Iteration

OBJECTIVE

Now that I had a working prototype I wanted some feedback on its functionality.

Usability Test Results & Iteration

After some deliberation, the bottom nav icon was removed and replaced with a calendar icon at the top of the page. The result is an uncluttered navbar with an easily accessible calendar that leads to all the historical data at the top of the page.

Calendar background color was added to section off each month for easier viewing.

Conclusion

Executed

Finding historical data on Fitbit made easier.

Trials

Since I don’t own all of the competitor’s devices, I relied heavily on google for  screenshots of their app.

Learned

I learned to discern between what user’s do and what they say.

Next...

Some users compared their app with Fitbit's, and mentioned different monthly viewing capabilities. Might be something to explore.

Outcome

My biggest take away from this project was learning how to discern between the opinions of the user’s and my own judgment as a designer without sacrificing the design.

Future Considerations

A calendar is just one way of finding information. Delving deeper into the user’s and how they use the product may result in a different solution.
Copyright © 2023 Suzy Kong