...
Lastly, we made some cosmetic changes to the splash image to reduce its look as a button. Some users tried to click on the splash image, for no reason but that they wanted more interaction. Because each image has a border around it, it gives it the slight affordance that makes it look like a button. Thus, we removed this border to make them look more like pure images.
Implementation
The major features that required the most attention to improve from prototype to beta version included logging in, searching for events, creating events, and uploading songs. We implemented the login system using a simple php library called Light OpenID. Specifically, we limited the available Open ID providers to Google, allowing the user to log in with his or her Google account. Once the Light Open ID library had authenticated the user's credentials, we gathered the necessary user information from the authentication request and stored it in a loosely encrypted form using a PHP Session.
To enable search, we developed a simple algorithm to scan all available event data for strings matching the user input. The application used PHP to connect to a MySQL database, so we used the SELECT SQL query with regular expressions to allow for dynamic search capabilities. To create events we used the CREATE SQL query, submitting text data for the basic information of the event. Since the flyer image was binary data, we used a BLOB column to store it in the database along with the rest of the event information.
Finally, the event page called for multiple key features in the upgrade from prototype to beta. The upload feature used the standard php file upload method, saving the file to a predefined place on the server. To allow the user to listen to the song we used a simple embedded flash player provided free by Google. The source of the player could then be set to the uploaded song's filepath on the server which could then download the data for the user to listen to.
Evaluation
Briefing
We appreciate you taking the time to partake in our evaluation. Our website is called RemotePlaylist and it enables users to upload, download, and browse music that are being played at variety of different venues. As a partygoer, you can search for an existing party or you may create a party of your own. As the website states, “RemotePlaylist is a social music recommendation engine that lets you request your favorite songs before going to the actual party. That way, you know you're going to have a good night before even leaving the door.”
...
User Testing - Usability Problems
User 1
Problem 1: One One user noted that while the buttons on the front page add to the aesthetic value of the front page, he was tempted to click on them.
Given their size and contrast to the background, it is conceivable that they give off the affordance of a button. Nonetheless, this was a tradeoff that we were willing to make because the icons are able to succinctly describe verbally and visually the function of the website. (Minor, button affordances)
Problem 2: There There currently does not exist a discernable ordering of parties.
This will require figuring out a way to incorporate likes/dislikes into the position in which the parties are ordered. (MajorMinor, Flexibility and efficiency)
Problem 3: There isn’t an option to perform an advanced search.
To correct this issue, we will have to find matches from in the database for a specific set of fields that the user would like to search for : (i.e. DJ Zeus, City: New York or Boston) (Minor, User Control and Freedom)
User 2
Problem 1: There currently does not exist a method through which users can browse parties according to specific fields: time, date, location, party playlist rating
One possible solution is to incorporate a tab that allows the user to reorder parties by different fields, in a manner similar to Itunes, which allows users to order music through song title, artists, and length. This can be done by drawing information from the database to create a dynamic view of partylists. (Major, Flexibility and efficiency)
Problem 2: User also reiterated the importance of an advanced search.
As he stated, "I would like to be able to restrict my search results to a specific t ype of party at specific date, and a specific city.
Problem 3: When uploading a song, the program does not check for duplicates.
In order to prevent duplicate songs, we will need to match check songs that and double check that there aren’t any songs with the exact entries for the following fields: song/title, file size, track length. (Minor, Error Prevention)
...
Problem 2: After the search has been populated, the main focus should be on the playlist.
Users Users have a list of all the songs in the playlist on the front page, or at least a sampling of the most popular songs being played, with a link to a player. The purpose behind the website is the enable the user to browse through the selection of songs, and not the individual club. (Minor- Major, User Control)
...