Fitted
A UI Case Study on an exercise companion app.
I’ll create a companion app that’s ready to tackle
all aspects of health.
WHO’S IT FOR?
People who are new or returning to fitness, want to find activities they like, and get into a good routine will be interested in Fitted.
Their Stories, their wants.
● As a new user, I want to learn about different exercises, so that I can figure out what is best for me.
● As a new user, I want to be shown how the exercises are done, so that I know I’m doing them correctly.
● As a frequent user, I want to be able to schedule exercises for working out, so that I build positive habits.
● As a frequent user, I want to be able to earn achievements or rewards, so that I can stay motivated.
● As a frequent user, I want to complete daily challenges, so that I can have an additional way to stay motivated.
● As a frequent user, I want to track progression and record what I’ve done, so that I can see my progress over time.
● As a frequent user, I want to be able to share routines with my friends who may also be interested, so that I can encourage them to become healthier.
I know who and I know why.
Now let’s find out how.
The Primary Tasks
We want the core features of our app to hit each main task our users want to complete.
“As a frequent user, I want to be able to schedule exercises for working out, so that I build positive habits.”
“As a frequent user, I want to track progression and record what I’ve done, so that I can see my progress over time.”
“As a new user, I want to learn about different exercises, so that I can figure out what is best for me.”
User Flows
I have to distill each Primary task to a User Flow, ideally making them as simple as possible on inception. Each task will inevitably become more complex with more features and requirements. So its crucial at this point to have be as easy as possible.
Schedule Workout
The prototype and my ideas have been evolving from this point, I was removing and adding things until my users stopped running into any usability errors.
I created 3 color palettes for some variety, and maybe some surprises.
I chose the second palette above, since it had black, orange and a very dark blue.
Typeface
Logo
Color Iterations
My first iteration of the colors in the UI held tightly to the color scheme I picked in the beginning. However there were two problems with this color scheme; Red can be too alarming on the eyes in this color scheme, and the Orange I’ve used may not read clearly on white.
So I went with my gut and reduced the color usage per page within the UI itself.
Colors as status
I didn’t want to place colors down just to make the current screen look good by itself. Each screen needed to be familiar to the one before it.
As I was building each screen, I noticed my main process was to start with a white background then dark blue elements making the majority of UI coloring, and orange as status elements! I enjoyed using orange for progress bars, stars, play buttons and achievements. This became the visual language I was talking about before.
Iconography
All iconography was made in Adobe Illustrator, a mix of hand drawn and pen tool objects. Line widths had to be as similar as possible except when a line width would obfuscate an icon’s meaning in a different scale.
Imagery
Animation
With my background in animation and game development, I am able to make animations within XD to give Fitted that extra juice! Completing workouts, seeing your progress, reaching achievements, and creating new content should be accompanied by animation:
Some Final Screens
Retrospection and Introspection.
I’ve learned so much from working on Fitted.
So much of visual and user design can be based on initial reactions! However, you can build your own aesthetic and design language by training the user with reinforcement and building a common language.
Simple designs will inevitably get complex, which is OK! After this happens you will learn how to shave down features, or spread out steps across multiple screens. This is the growth and constriction that’s part of UX/UI, and that’s so fascinating!
Mobile-First design is key! If you can make a symphony with 2 instruments, you can create something an order of magnitude greater with more space.