Skip to content
zhan9 edited this page Oct 30, 2016 · 15 revisions

#Welcome to the TeamPreview wiki!

Summary: what is the problem space and how did you address it?

The problem space for this project is bias in movie reviews. The aim of the project was to create an application that would allow people to see a movie reviews rating without that person’s bias. This is done by taking into account the reviewer’s history of reviewing movies and creating an adjusted score for that review. For example, if a reviewer always rates horror movies less than 7 when they give a horror movie an 8 it means it would get an increased adjusted score to reflect that the reviewer like it for horror movie.

#Problem and Resolution

We created web application that gathers reviews from other websites, sources and from user submission that allows users to read those reviews and view the scores free from the bias of the reviewer. This app aims to address the bias in movie reviews. It will do this by calculating an adjusted score for the given review based on the reviewer’s history against other reviewer’s history.

###Choosing a genre

pickgenre

Choosing genre(s) is a process done by user when creating a new user profile in our app. This is to give focus on which genre(s) a user interested in. With this, other reviewers will acknowledge what kind of movie genre(s) this particular user will review and interested in. Also, the recommended movie to this user will be around his preferred movie genre(s).

###Choosing rated movies

ratingmovies

User also will be asked to choose at least 3 rated movie during the process creating a new user profile. This will strengthen which movie genre(s) they interested in.

###Movie review page

screenshot 385

This is the Movie review page. From this page, reviewer will be able to see all reviews on this movie. It evolved since we added an adjusted score to final product of Movie reviews page. This score is effected when reviewers give more or less score to the movie.

###Homepage for not log-in user

screenshot 386

This is the homepage for user who is not log-in to our app. It evolved when user is still can look for a movie that they interested in. Just that it is not focused to their preference. Below is the image of suggested new movies released to non-log-in user. User is still able to look at each of the movie reviewed score for them to decide whether they interested in that particular movie or not.

screenshot 387

##Limitations There were limitations during our developments of our prototypes. A limitation we encountered was that initially this site had a niche target of reviewer enthusiasts, the problem was when we wanted to do user testing it was very difficult for us to find that niche near us although this target audience is probably very large as students we could not find anyone that would satisfy that niche target. So we decided to user test on people who would use review sites casually/regular basis.

In saying that we opened up our audience to regular/casual people who look at review sites our feedback became very biased towards "we only want to see ratings of movies" in comparison to " we want to see what the reviewer has said about 'x' movie" This was quite prevalent in all of our feedback. We designed two iterations of a news feed page one was rating focused and the other was reviewer comment focused and to no surprise a majority of our feedback wanted rating iteration. As a team we did not want to focus on only ratings so we decided to design another iteration that would satisfy rating focus as well as the reviewer focus.

We chose our final prototype to be designed on InVision as a high-fidelity version. There were few limitations, although we managed to get most of our features to be exhibited there are limitations on how we showed them due to InVisions features. In saying that this prototype proved to be quite useful as it exhibited what we liked in a high-fidelity version in comparison to our balsamiq low-fidelity version. Some specific features that we couldn't really show was how recommendations would be personalised on an algorithmic level. Due to the fact that this prototype only allows us to link pages to other pages we were only able to show how the recommendation process would work through a taste test page where users are able to pick what genres they are into and rate movies within those genres.

#Task Done by Each Member

Angus Wood

Worked on coding and content of the promotional website as well as designing some pages for the low fidelity balsamiq prototype. Also conducted a user testing session for a version of the balsamiq prototype.

Kevin Leong

Kevin compiled all documentation of the processes in the github wiki. He also did user testing aswell as aid in coding the promotional website for the prototype aswell as design some pages on the low-fidelity balsamiq prototype.

Fatin Shahrol

In-charged of user testing for high fidelity prototpye- InVision app. Added a test protocol and user testing results and feedback on wiki https://github.com/deco3500/teampreview/wiki/Team-Preview-%7C-User-Testing---Feedback. Also, did a few user testing for low fidelity prototype and designed a few pages for the low fidelity balsamiq prototype (profile page(s) and Write a review page).

Joy Zhang

Designed some of the pages for the balsamiq prototype, also conducted the user testing for it. Developed and designed the final prototype in InVision.