song-snippet

Song Snippet

Avid music listeners often spend hours trying to find new songs that suit their tastes. Having to listen to each individual song will consume a lot of time that could be spent doing other activities. Our goal is to allow users to discover and like new songs in a timely manner without having to waste hours finding songs to add to their playlist. Our app will allow users to listen to a snippet of the song and give them a general idea of what the song will sound like. The user will then be able to like or dislike the song by swiping left or right; which they then can add to their playlist on their music platform of choice. We want to make discovering music more enjoyable and less of a chore.

UX Team Members

User-Centered Design Artifacts

Phase I: Analyzing Users, Competitors, and Initial Designs

Executive Summary

Song Snippet’s goal is to give users more accessibility of finding new songs to listen to. In our first phase, we spent our time gathering information to better understand our users and needs, how we compare to our competitors, and where we should be going forward.

To gather our data we performed a Competitive Analysis and Heuristic Evaluation to better understand our competitors and see what we can do to make our product stand out amongst our competitors.

Full phase I report

Phase II: Refining interaction and designing wireframes

Executive Summary

In Phase II, we created wireframes. This gives us the opportunity to visualize where we should place different elements of our ideas without the need to code the product. We also performed cognitive walkthroughs of our wireframes to see how users would interact and see what areas need the most improvement. Based on the information that we have gathered in Phase I, we have decided to go with a simplistic design that allows users to achieve their goal with relatively no trouble.

Our wireframes include such features as:

Upon the results of our cognitive walkthrough that we have performed, the feedback we have received is mixed.

With the informal feedback that we have received, we have concluded that our application was simple and straightforward.

From what we have learned throughout Phase II, we have decided that we do not need to incorporate that much design toward our user testing in Phase III. Rather we plan to focus more on our interaction with users and make it easier for them to interact with. We will plan to implement design along the way, however it will not be our main focus moving forward.

Full phase II report

Phase III: Prototypes and User Testing

Executive Summary

In Phase III, we put our prototype to the test. By testing our prototype against users, we were able to gather useful information and see where we stand up against our competition. We gathered 5 participants and had them test our prototype against one of our competitors Shazam. By performing the same tasks on each application we were able to determine the strengths and weaknesses of our prototype, so that we could later improve upon them.

Our protocol during the test included these tasks:

Upon the results of the user test, we gathered much useful feedback and have determined that while our prototype is functional and simple to use. There are still some areas that can be improved upon.

After discussing our prototype further with the participants, we received some interesting feedback on ways that we could improve our prototype in the future.

Using the information that we have gathered throughout our user test, we have learned much about how users interact with our prototype and the kind of expectations they have of it. We have come to the conclusion that while users had not as much difficulty navigating through the prototype there are still some areas that need improvement. Going forward our next goal would be to change around some aspects of our prototype and move on to focus more on the design.

Full phase III report