I performed the think aloud with a 11 year old boy who is very interested in cars and mobile games. His interests, age and knowledge is similair to our primary persona and I think he's a fitting test user. He has experience with quiz apps such as "Quizkampen", but he has never used a QR code. His english knowledge seemed to be sufficient.
I explained the context of the app, how it will be used and what happens if you press different buttons. But I wanted him to mostly explore by himself and so I set up a scenario (a museum visit) to immerse in him in the experience.
The first thing he did was to click on help, he didn't understand everything but he told me he got the gist of it. Then he decided to take the quiz but after answering the first question, it took a few seconds for him to realise there were more questions if you scrolled. When he had answered all the questions he wondered what he was supposed to do next, so I had to tell him that there was no "game over" screen or score board implemented yet.
So he moved onto the QR scanning, he didn't know what QR was but he realised that the code was clickable when he moused over it. I explained how QR worked and it would be implemented later on.
After that, he clicked on the treasure hunt and realized he had to use the scan function to complete it, he clicked on the QR scan and was dissapointed when he got the rockets exhibit again.
So he ignored it and decided to explore the settings. He noticed that the language change didn't do anything and I told him that it wasn't fully implemented yet. Then he clicked on the "clear exhibits" button and I told him about the checklist function, which shows all the exhibits you've scanned on the "home screen", and that he had just cleared all his history.
Because of that, he wannted to take a look at the home screen but he was confused by the lack of a home button and frustrated when I told him he had to press the "back" button until he made it to the home screen.
Overall, he seemed to be able to understand the app and how to use it. I think it would be nice to have an independant QR scan that is assigned to the treasure hunt, this will make it more specific and focused. Navigation seemed to be a little clumsy, with the major flaw being the lack of a home button.
Something unrelated to the think-aloud evaluation that I noticed, was that the quiz automatically corrected every following answer as "correct" if the previous one was correct.
måndag 9 mars 2015
söndag 8 mars 2015
Think Aloud - Arsalan
Tested by 3 people, all of them have had previous experience with apps.
Generally:
They suggested that the app could have a better colour scheme instead of using white and grey. On some pages, the footer bar had 2 buttons but they were not centred (there should have been equal amounts of space between the edge of the screen and the buttons). Finally, they mentioned that the lack of the home button is a bit tedious. This is because if they want to return to the home page, they have to keep on pressing the back button (a button which redirects the user to the previous page).
Home Page:
They liked the placement of the help page (as a pop-up that opens when pressed on). They also found the settings button to be useful and the instructions were simple enough to understand.
QR Scanner Page:
They didn't understand that to advance to the next page, you have to tap on the QR image. The idea was that when you are using this app in reality, the QR page would display what your phone's camera would be seeing. There, you would scan the QR and it would automatically redirect you to the exhibit's page. But since this is a web-based prototype without any features a phone has, we had to improvise by using this page.
Another issue with the QR scanner page is that every time you press it, it only opens the Rocket page. The idea was that it should open up a different page each time you press the QR button.
Quiz page:
They noticed that the quiz would give the pop-up "Correct Answer" on questions 2-5 for any alternative they selected. They also would have liked to have a page which displayed the results rather than have a pop-up after every question.
Exhibit pages:
They noticed that the aeroplane exhibit page has "Rocket" as its header. It was unclear to the users that you could visit a specific exhibit's page by tapping on the image. This information should have been available in the help page.
Settings page:
They realised that the change language button does not actually change the language. I explained that this was a prototype and full functionality isn't required at this point. They tried out the clear exhibits button but it took them a while to realise the effect this had. This is because they had to keep pressing the back button to reach the home page.
Generally:
They suggested that the app could have a better colour scheme instead of using white and grey. On some pages, the footer bar had 2 buttons but they were not centred (there should have been equal amounts of space between the edge of the screen and the buttons). Finally, they mentioned that the lack of the home button is a bit tedious. This is because if they want to return to the home page, they have to keep on pressing the back button (a button which redirects the user to the previous page).
Home Page:
They liked the placement of the help page (as a pop-up that opens when pressed on). They also found the settings button to be useful and the instructions were simple enough to understand.
QR Scanner Page:
They didn't understand that to advance to the next page, you have to tap on the QR image. The idea was that when you are using this app in reality, the QR page would display what your phone's camera would be seeing. There, you would scan the QR and it would automatically redirect you to the exhibit's page. But since this is a web-based prototype without any features a phone has, we had to improvise by using this page.
Another issue with the QR scanner page is that every time you press it, it only opens the Rocket page. The idea was that it should open up a different page each time you press the QR button.
Quiz page:
They noticed that the quiz would give the pop-up "Correct Answer" on questions 2-5 for any alternative they selected. They also would have liked to have a page which displayed the results rather than have a pop-up after every question.
Exhibit pages:
They noticed that the aeroplane exhibit page has "Rocket" as its header. It was unclear to the users that you could visit a specific exhibit's page by tapping on the image. This information should have been available in the help page.
Settings page:
They realised that the change language button does not actually change the language. I explained that this was a prototype and full functionality isn't required at this point. They tried out the clear exhibits button but it took them a while to realise the effect this had. This is because they had to keep pressing the back button to reach the home page.
Hosted version of the prototype
In order to access the final prototype directly, please go to http://dev.ksdn.se/hcikth/.
lördag 7 mars 2015
Think-aloud evaluation of the prototype
This is my think-aloud test, done in a simulated environment with a kid in elementary school age. Keep in mind that the prototype isn't fully functional so i had to explain the whole time why a certain something didn't work. The think-aloud was done entirely in Swedish, but I translated it to English here.
Before i started the experiment, i told the user that this is an app for the technical museum, and his task is to explore all the functions that it offers.
[Start of the experiment]: The user is looking around at the home page.
User is clicking at 'Take the Quiz' button.
User: I'm gonna take the quiz, looks like it has questions.
User sees the first question and chooses one of the alternatives.
User starts to scroll down.
Me: You're scrolling down to get to the other questions.
User: Yeah, i realize that.
User does the same thing with all the other questions. During whole this time he's talking exclusively about the questions of the quiz, so I'll omit what he said here.
At the end of the quiz, the user is still at the quiz page. He looks around and then clicks on the 'Treasure hunt' button.
Me: Why did you click there?
User: I don't know, I'm just testing.
Here I had to explain that the treasure hunt page is incomplete and that he had to go somewhere else, so the user clicked on the 'Scan QR code' button. Once he was in the scanning page, he seemed confused as what to do next, so i explained that he had to click on the QR-code.
(Note: In this prototype, there is no real scanning function, so the user is supposed to click on a picture of a QR-code and pretend that he is scanning)
When the user clicked on the QR-code, he gets redirected to a page with a picture of a rocket and information of rockets. User starts reading the information.
User: I don't understand, too much English.
User clicks on a picture of an airplane and gets redirected to the airplane page. He then looks around and clicks on the settings button. In the settings page, he clicks on the 'clear exhibits' button.
User: 'Exhibits cleared', I don't know what this is supposed to be
User: Oh look, i can change language.
User chooses to change language setting to Swedish. He then proceeds to go back to the home page.
User: Wait, nothing has changed, it's still in English.
Here i had to explain that the other languages weren't actually implemented.
Right then i choose to terminate the experiment because i thought that there wasn't anything more to test.
Since the user choose to click on the 'clear the exhibits' button earlier, he never realized that scanned pages show up at the home page. He also never bothered to click on the 'Help' button despite the fact that he seemed to click on everything else.
The thing that immediately comes to mind when i think of this experiment, is that we shouldn't expect of children to know perfect English or that they know immediately how to change the language to Swedish (or their other language of preference). Otherwise it seems like they understood the interface of the prototype, that they had to click on the buttons and what kind of things they expected to show up on these pages, or that they had to click on the picture of the airplane to get to the page of the airplane.
Before i started the experiment, i told the user that this is an app for the technical museum, and his task is to explore all the functions that it offers.
[Start of the experiment]: The user is looking around at the home page.
User is clicking at 'Take the Quiz' button.
User: I'm gonna take the quiz, looks like it has questions.
User sees the first question and chooses one of the alternatives.
User starts to scroll down.
Me: You're scrolling down to get to the other questions.
User: Yeah, i realize that.
User does the same thing with all the other questions. During whole this time he's talking exclusively about the questions of the quiz, so I'll omit what he said here.
At the end of the quiz, the user is still at the quiz page. He looks around and then clicks on the 'Treasure hunt' button.
Me: Why did you click there?
User: I don't know, I'm just testing.
Here I had to explain that the treasure hunt page is incomplete and that he had to go somewhere else, so the user clicked on the 'Scan QR code' button. Once he was in the scanning page, he seemed confused as what to do next, so i explained that he had to click on the QR-code.
(Note: In this prototype, there is no real scanning function, so the user is supposed to click on a picture of a QR-code and pretend that he is scanning)
When the user clicked on the QR-code, he gets redirected to a page with a picture of a rocket and information of rockets. User starts reading the information.
User: I don't understand, too much English.
User clicks on a picture of an airplane and gets redirected to the airplane page. He then looks around and clicks on the settings button. In the settings page, he clicks on the 'clear exhibits' button.
User: 'Exhibits cleared', I don't know what this is supposed to be
User: Oh look, i can change language.
User chooses to change language setting to Swedish. He then proceeds to go back to the home page.
User: Wait, nothing has changed, it's still in English.
Here i had to explain that the other languages weren't actually implemented.
Right then i choose to terminate the experiment because i thought that there wasn't anything more to test.
Since the user choose to click on the 'clear the exhibits' button earlier, he never realized that scanned pages show up at the home page. He also never bothered to click on the 'Help' button despite the fact that he seemed to click on everything else.
The thing that immediately comes to mind when i think of this experiment, is that we shouldn't expect of children to know perfect English or that they know immediately how to change the language to Swedish (or their other language of preference). Otherwise it seems like they understood the interface of the prototype, that they had to click on the buttons and what kind of things they expected to show up on these pages, or that they had to click on the picture of the airplane to get to the page of the airplane.
fredag 6 mars 2015
Before exercise 5
Hi, i hope everyone reads this.
Before Monday afternoon we have to summarize the results from each person's test and post one short analysis in the blog. We also have to prepare a 5-10 minutes presentation (using a projector) where we have to present our problem, the main scenario and the prototype. How are we going to organize all of this in 2 days? I don't think we'll be able to meet up before Monday since I'm currently away. Do you want to meet up without me anyway, or should we all meet up before lunch time (10-12) in Monday at the library before the exercise session starts?
I personally prefer the second option, and I'll assume that it's what we're going to do unless someone says something otherwise here.
Before Monday afternoon we have to summarize the results from each person's test and post one short analysis in the blog. We also have to prepare a 5-10 minutes presentation (using a projector) where we have to present our problem, the main scenario and the prototype. How are we going to organize all of this in 2 days? I don't think we'll be able to meet up before Monday since I'm currently away. Do you want to meet up without me anyway, or should we all meet up before lunch time (10-12) in Monday at the library before the exercise session starts?
I personally prefer the second option, and I'll assume that it's what we're going to do unless someone says something otherwise here.
tisdag 3 mars 2015
Prototype
Hi guys !
You can find the basic version of our prototype here . Download the folder and just open index.html in a web browser. You will need to resize the browser because we are simulating a mobile device (otherwise everything will look stretched out). Suggest any improvements or critics in the comments below.
Change Log (changes made after this version of the prototype):
Discussion:
Note that each page has a footer bar. In it contains buttons with essential function. Something to discuss would be if the buttons I placed on each page are appropriate for the page itself and whether or not a home button is necessary (a button redirecting the user to the main page).
A colour theme other than white and grey would be great to have, any suggestions for colours to use?
You can find the basic version of our prototype here . Download the folder and just open index.html in a web browser. You will need to resize the browser because we are simulating a mobile device (otherwise everything will look stretched out). Suggest any improvements or critics in the comments below.
Change Log (changes made after this version of the prototype):
- Exhibits can be added and cleared.
- Pictures of exhibits have a name attached to them now (like Rocket, Car)
- You can now click on an image and it will redirect you to the associated exhibit (only works for Rocket as of now)
- Treasure Hunt has been updated.
- Removed Take the Quiz button on Take the Quiz page.
- Changed theme to black (this can be reverted by changing one word in the code)
- Implemented Artem and Abdallah's latest suggestions
Discussion:
Note that each page has a footer bar. In it contains buttons with essential function. Something to discuss would be if the buttons I placed on each page are appropriate for the page itself and whether or not a home button is necessary (a button redirecting the user to the main page).
A colour theme other than white and grey would be great to have, any suggestions for colours to use?
Prenumerera på:
Inlägg (Atom)