GR6 - User Testing
Design
The Home Page.
This is the homepage. In the main panel there is a display of the most popular streams, each stream consisting of a screencap, stream title, and channel title. On the left there is a column with various stream categories. Clicking on these labels will bring up a thumbnail (screencap, name, user) view of the live streams from that category. Some categories have subcategories; clicking on these categories causes the left panel to update with the subcategories. Clicking "Home Page" takes the user up a level, in the case of subcategories. There is no case where there is more than two levels of subcategories.
Also, clicking on the "StreamBrowser" title itself takes the user back to the home page. The user can also use the back and forward navigation buttons on the browser to the same effect. 
On the top right there is a search box. Typing search terms into the box and then pressing enter brings up a thumbnail view of the streams that match the search. If no streams are found, a message saying that no streams were found appears instead. 
Searching for "starcraft"
Clicking on any of the streams in the thumbnail view takes the user to the embedded player for that stream. Underneath the embedded player is the description of the stream. 
Watching the NHL playoffs
Whenever the user watches a stream, the stream thumbnail appears in the bottom "viewing history" panel. The streams here are ordered from most recently watched to least recently watched. Clicking on any stream in this panel takes the user to the embedded player. In between the first and second screenshots above, the user watched the NHL Playoffs stream, so it appears in the Viewing History.
Finally, we have a neat little spinner for when the page is waiting for a request to a third-party server: 
Waiting for the "football" search to go through
Implementation
StreamBrowser is implemented mostly in javascript with some php. Everything is implemented in one page, and different things are ajaxed in and out based on the request that is sent. Finding the streams are done by making calls to third party sources (currently, only justin.tv api). The viewing history is stored as a cookie on the user's browser. This allows the history to work without having to go through a login system, but on the other hand if a user has multiple computers then the viewing history will not go with them. Since users usually don't want to make new accounts for small features, we feel this is a good tradeoff. It would still be possible to implement a login system later.
Evalutation
TODO:
-How did we find users?
-How representative of the user population are they?
-How were users briefed? What tasks were performed?
-What usability problems were found? What are some possible solutions?
Some users tried to drag and drop thumbnails around in the Viewing History tab. One user commented that the Viewing History tab reminded him of Youtube's playlist, and on Youtube you can drag thumbnails of videos around to reorder the playlist. Although we originally envisioned the Viewing History as a simple list, rather than a playlist, it would be good to implement dragging and dropping of thumbnails in the Viewing History. The solution to this problem would be to simply implement this feature.
Reflection
TODO:
-What did we learn from this iterative design process?
-If we could do it again, what would we do differently?
-Focus in this part not on the specific design decisions of your project (which you already discussed in the Design section), but instead on the meta-level decisions about your design process: your risk assessments, your decisions about what features to prototype and which prototype techniques to use, and how you evaluated the results of your observations.