Every song has a tempo (beats-per-minute). As a group fitness instructor, your workouts are determined by the beat count of the music. For example, a warm-up set will have slower BPM songs versus a workout that is higher intensity cardio, which would have songs of higher BPM.
Find my Beat had the ultimate goal of enhancing a trainee's training experience. All actions revolve around finding the beat count(BPM/RPM). Therefore, I stayed away from adding music control functionalities that were similar to music streaming apps such as Spotify. The only music control functionalities in Find my Beat would be play and pause.
The main flow: allows for the app to listen to the song being played, extracting the correct song and it's BPM/RPM, as well as find a song that has similar beat counts as the song being searched. From here, the trainee can add any song to either a playlist in the app, or export the song to their Spotify library.
Collect the songs that fit the count you want for our workouts in playlists. Once you're ready to really use it, export that playlist to Spotify to play and control those songs at full capacity.
If a trainee has a BPM or RPM they want to find songs for, inputting the count returns a list of songs within the range inputted. For example, warm-up songs are typically around 120 BPM, so the songs returned can all potentially be used in a warm-up playlist.
The biggest challenge that came with training for my certification was counting the beats of songs. As a result, I designed the functionality of my app to revolve around the BPM and RPM of songs.
I mapped out some use case scenarios to get a better understanding of the types of users who would benefit from my solution:
I ultimately decided that the user I was designing for was an instructor in training because I felt like they could benefit more from doing user scenarios.
1. How might we find the BPM of a song?
I first created low-fi wireframes of the actions of playing a song to find the count and then collecting those songs into a playlist.
2. How might we collect songs?
3. How might we find songs for a desired tempo?
Many times in training, I would want to find a song with a certain beat range so I could use the song for different stages of the workout.
To reach this goal, the trainee can manually type in a beat, and a list of songs within a ± 20 range of that beat will be generated.
I did a round of tests with my classmates and then did a test with some of my non-design friends. I wanted to get as many different perspectives as possible.
Here are some of the feedback and questions I thought was most significant and helped me improve my project’s experience:
Paper testing on my political science major roommate!
A huge challenge for me in this particular project was the visual/UI design. This was the first time I had the freedom to create an app with its own “look".
I wanted the main interface color to be blue because the color represents health. I also found myself struggling to design the tap button to indicate that it was listening to the song.
The goal was the interface to be friendly and clean. There are many numbers and I knew I needed to figure out a way to make the BPM/RPMs distinctive and not get lost in song names. I also knew I wanted it to be visual because it would be less intimidating-looking, especially because counting beats is rather technical.
Above all, I wanted the visual design to be straightforward so:
1. Main flow – Find the BPM of a song, save song
I added a capability that actually returns the song being played- similar to the Shazam App. I figured that if the user did not know the name of the song, they would find it helpful as well.
2. Collecting songs to use for workouts
For the playlist detail, I:
3. Finding songs based on a desired BPM range