Note: Need to make sure our way of 'news verification' is correct
Questions to ask the user
(After explaining how the current verification system works) Do you think this way of verifying news works - is it reliable? Will you trust a piece of news verified in this way?
Do you think this idea is better than current existing social networks?
Interview for the actual prototype
Preparation
Note: interviews are to address specific questions regarding the current design/prototype implementation. Surveys are to ask for general feedback regarding the whole concept/high-level stuff
Questions about the prototype (i.e. the research question)
Is it easy to navigate around the app with the current implementation?
Tasks
[ ] Develop paper prototype (Nhan)
[ ] Create protocol runsheet (Khoi)
Interview Protocol
What are the order of things to be done at the beginning, during, and after an interview?
Who will be assigned to which tasks?
Tasks for users to perform
Comment on a headline
Rate a headline
Go to the page of an author from a headline page
Go to a different 'universe' (?)
Questions to ask the interviewee at the end of the interview
Do you know how to comment on a headline?
How long does it take you to know how to use the application?
The 4 'buttons' on the main page are not clear about what they do - they thought those buttons actually lead to the pages themselves and not to the tutorials
But they thought that having the tutorial section explaining the features is useful
Start page
(Given the current design of the paper prototype) they did not know what the 'planets' are for, and it was not clear that the 'headlines' on the right are clickable - they did not know what they can do while looking at the page
Headline page
The comment section should be bigger and maybe in the middle instead
Signup page
Too simple
'Login with Facebook' should just be a button, instead of a form
Person 2
Main Page
The buttons on the horizontal lines should look more like buttons
Description 'Visual Social News Network' should be on a separate line
Start Page
How will the planets be designed? They want to look at the actual graphical design to give comments
What does the '=' button do? - need to show that feature in the prototype too
Headline Page
Buttons for functions may be too big when implemented - they take up a lot of space but does not look that nice
Image/graphics of the planet will probably look nicer if faded into background and not taking away user attention from other features
(They) like the idea of contents in the middle
Login page
Want to see a more complete design first before being able to comment
The four tutorial slides seem helpful but, there must be a better way to show to 'first-time users'. And it would be better if there is a skip button in case if the user already know how to use the web.
Start page
The side menu shows the head line from every categories, it would be better if they can be sort out.
Person A thinks the planets look fine at the moment but there are going to be way more categories and planets in the future so it might be too complicated for the start page. Better user interface seems required.
Person B found difficulties in finding out how to play around planets. (Even though she had read the tutorial slides already)
Headline page
Person A thins it is better to have mobile friendly user interface and layout of the page.
The size of the buttons are too big and the comment space is too small. (Simplify the design as much as possible)
Signup page
Link to Google account or Facebook
More graphics may be required. (It is currently too simple)
Interview for Concept
Note: Need to make sure our way of 'news verification' is correct
Questions to ask the user
Interview for the actual prototype
Preparation
Note: interviews are to address specific questions regarding the current design/prototype implementation. Surveys are to ask for general feedback regarding the whole concept/high-level stuff
Questions about the prototype (i.e. the research question)
Tasks
Interview Protocol
Tasks for users to perform
Questions to ask the interviewee at the end of the interview