The website can be found here: 

RemotePlaylist

As a website, our current platform does not contain any requirements for software or hardware.

For our prototype, our group focused primarily on creating high fidelity on look, and left out certain aspects of the backend. Hence, the links between pages are generic, and are not yet catered to the specific party or word search. In the first page, the search functionality leads to a generic list of parties.  Eventually with full backend implementation, it will match up to the user's specific query for search, playlists, and song choices.  

Currently a default anonymous account user is setup, and the website lacks user specific information.    Eventually, we will implement a full login system, and a specific page with aggregated user information will be displayed. 

 

  • No labels

1 Comment

  1. Clean user interface, and nice job with the party create dialog and auto-scrolling effect.  
    Overall though, I think there are a lot of areas of functionality that should exist but don't that make it hard to test this prototype.  For example, you can't get to the individual party screens with songs (even if they were pre-populated songs) without creating a party (i.e. you should be able to get there from the party list).  Also, the create button seems like it is a disabled button when really it is just another function of the site - this is a visibility issue that should be sorted out (though I get that the idea is to highlight which tab you're on... maybe play around with different ways to do that).  There should also be some indication of the current user's liking or disliking status of a given song and an ability to correct an erroneous like or dislike of a song.  I think a good chunk of features are there, but more work should have been done to make navigation and "playing" with the process of doing the tasks in your GR3 easy, even if content was canned.  Also, your statement on the wiki should contain more specifics and details about what exactly is implemented and what exactly is not as fully implemented rather than having users discover this for themselves.