...
Based on feedback from testing we fixed several issues with RScanVP
- We redesigned the homepage to better fit on narrower devices.
- We added a drop down for times to the event details page.
- We added a poster to the event details page to communicate the poster metaphor.
- We decided to take away the "Download" button altogether. This makes it a little harder for users to acquire the QR code that has been generated. We made this decision so that the user was not redirected away from the site at any time because we could not figure out any other way to do it.
...
- After getting the users who would participate in the test, we told them that we created a website to help with the tracking of results for advertised events.
- Poster Maker - You are in charge of publicizing for an event. Your first task is to use our site to create a QR code that prospective attendees can scan to send an RSVP for the event. Later on, you will be tasked with viewing the statistics for your event.
- Prospective Attendee - Your task is simply to scan a QR code, RSVP 'yes', and choose to get an email reminder/add it to your calender.
Usability Problems and Non-Implemented Solutions
- User did not know what a QR code was - Major - We could add more information about what a QR code is to the homepage.
- Download Obscurity - Catastrophic - Users were unsure of how to actually download the QR code. There was a note saying to right-click and download the image, but users got stuck because the term "download" was not consistent with the supplied option of "Save Image As...". In order to fix this, we could simply change the line of text telling the user how to download and make the syntax consistent. Further, we could simply email the image to the user when we email them the Admin link so that they do not have to worry about downloading it. However, this means that supplying an email would not longer be optional.
...
- Error Text - Minor - As noted by the TA, error text was far from the fields that had the error. This was not mentioned in the user testing because the screen that we used for user testing happened to be larger than the one used for GR5 demoing. Thus, it was clear to users when the text appeared that it had appeared.
- User did not know if they had a QR code scanner - Catastrophic - We could ask poster makers to insert instructions on how to download a QR scanner. We could ask poster makers to also provide a text URL for them to enter.
- Color took a while to change - Minor - We could indicate that the page was processing while the new QR code was loading.
- Didn't hit set size - Minor - The user typed in a size, but did not hit "Set size". We could automatically set the size when the box loses focus.
- The user did not want to give their email - Minor - We could add a message saying their email will only be used once.
- Network slow - Out of Scope - The user was confused when the internet network was slow; little you can do about this.
- User surprised could see other RSVPs - Out of Scope - Security was not a requirement for this project.
Reflection
- The main thing that we learned over the course of the semester is that we are not our user. That is, even if we think something is simple, obvious, or clear, this does not mean that the user will feel the same way. We have a lot of preconceived notions about what things should do because we actually created them, the users of our system will not be in that position and are thus much more likely to be confused.
...