GR3 - Paper Prototyping

Prototype Photos 

 

1. Title Page 2. Create Account 3. Empty Home Page 4. Search for a Cause 5. Cause Mission Page 6. Donate to a Cause 7. Add Billing Info 8. Updated Home Page 9. Share via Email 10. Log into Facebook 11. Share via Facebook

Scenarios

Create a Donate2Us account: set up an account with a username and password
Search for a Cause: search for charity you want to support
Donate to a Cause: donate money to a cause
Add Billing Info: add a credit card to charge
Create a Cause: create your own cause with a mission statement and description
Share with Friends: share your cause with your friends via facebook or email

Briefing

We introduced Donate2Us as a mobile application that allows fundraisers or student groups to create and spread the word about their causes. We explained that users can create, join a cause, share, and donate to causes. We told them that this applications is similar to Causes on Facebook but geared towards mobile platforms.

Observations

Below are the most important observations we had during our user testing:

  • There is a loophole in the design - user can create an account, join a case, then donate without credit card information entered. There is no requirements for users to have credit card information in the database before donating.
  • Users should be able to deselect a check box that would not save their credit card information if they don't want that saved.
  • To start joining a cause, some users take relatively a bit longer time to realize that they have to search for a cause first using the search bar at the bottom.
  • Some users think that the search bar is quite confusing; it should be clarified that is the searching applied for just causes on the user’s profile, or causes in the entire database.
  • A user thought that the “Create Account” option on the login page was a text instead of a link to create account.
  • When sharing a cause to friends, a user commented that if he wants to share via Facebook, he would want to put in a message and have a clarification on where his message will go (whether it will be posted on his page or on all his friends’ pages).
  • The same user also pointed out that perhaps we need a login page for Facebook if we want to share the message via Facebook (when designed, we just assumed that the users are already logged in with Facebook on his/her phone).
  • After donating, the app has an optional field that says “Message:” Some users wanted to fill in but were hesitant because they were not sure who his message would be sent to (whether it is to the owner of the cause, or it will publish something on his Facebook page.
  • All users have no problem with creating a cause.
  • Most commented that the app is overall self-explanatory and user-friendly enough.

Prototype Iterations

Below are the main changes we made between the first and second round of testing:

  • Completely revamped the Sharing feature interface. We created separate tabs for sharing via emails and sharing via facebook. For sharing via Facebook, we first prompt the users to log in if he is not already, and then clarify the destination of the message he puts in by labeling it “Post something on your wall:”.
  • Added a pop-up window requiring users to enter billing information when they clicks on Donate, in the case that their billing information are not in the system or that they are outdated.
  • For the search bar at the home page, we added instructions that say “Search for a cause to join...” on the search bar to improve learnability. Doing so will (1) clarify that the search is for searching the entire database for a cause and (2) make it easier for users to know where to start when trying to join a cause for the first time.
  • Changed “Create Account” option into an underlined hyperlinks to align with the normal convention to make it easier for users to locate. Also moved the “Create Account” and “Forgot Password” options below the LOGIN button for better logic flow.
  • We change the label of the optional message field after the user donates from “Message:” to “Message to the Fundraiser(s):” to clarify the intended destination of the message.
  • No labels

1 Comment

  1. "Prototype: it would be more informative to show pictures of your prototype with more ""real"" data filled in (all boxes are empty on your screenshots)
    Briefing & scenario tasks: briefing: don't explain what you did. Pls just report what you said to users, verbatim.
    Good: Tasks seem short and high level
    User testing observations: please make it more explicit that you test at least 6 users
    Presentation: pls. label observations: +/-/!
    pictures aren't aligned with captions on the bottom
    Overall: great that you were able to find a security hole  at this stage

    "