Prototypes

Prototype A

28daysmock_homepage28daysmock_homepage_color

 

This is the homepage of the application. As the app is more certain that the user is close to her period, the zombie will fill up with color.

28daysmock_blood28daysmock_pain28daysmock_moody 28daysmock_crave

 

The above screenshots allow the user to log symptoms. Each image corresponds to a button on the homepage.

28daysmock_calendar 28daysmock_stash  28daysmock_details

 

Also on the homepage are buttons for a calendar view, the “Stash” which is a list of recommended items to combat “zombie” periods, and the bottom graveyard takes the user to a history/analysis page.

Prototype B

This prototype is divided into sheets for easier printing. The first sheet contains the two widget screens, as well as various values for mutable fields. For example, if the user edits a forecast in the first widget, its title changes from “Forecast for…” to “Record for…”. This lets the user know that the data they entered has been saved.

sheet0

Next is the sheet for the home screen, which contains a pullable calender tab. We make use of an Android convention called a “toast” for providing user feedback. This allows us to follow the mobile paradigm of avoiding explicit saves, while still assuring the users that the data they entered has been written to disk.

sheet1

The third sheet holds the settings screen (accessible through the gear icon on the home screen) and the custom zombie screen (accessible through the + button on the home screen). These provide additional options and customization.

sheet2

Finally, here are symptom zombies that can appear in the first widget and on the home screen.

sheet3

Tasks and Script

Thank you for participating in our study.  We’re going to have you go through five tasks that touch on the main functions of our app.  We are using a method called “Thinking Aloud”.  There are no wrong answers; we’re testing the prototype, not you.  Any trouble you have in completing the tasks points to elements of our design that we need improve and make more intuitive.  In “Thinking Aloud” testing, we ask that you talk through everything you’re thinking about – first impressions, confusing instructions, why you decide to click a specific item, etc.  Try to figure it out without our guidance, but if you really get stuck, we can give you some guidance.

Our app is a zombie-themed period tracker called “28 Days Later”.  It is used for tracking symptoms and it provides predictions for when your period will start (and the symptoms that will accompany it).

[for prototype A]: For this prototype, you start at the application’s home screen.

[for prototype B]: For this prototype, you will begin on your device’s home screen, rather than inside the application. We’ve included optional widgets in this prototype, something that advanced users may find helpful for speeding up data entry.

  1. Imagine you’re at the doctor’s office and your doctor asks for the date you started your latest period. Use 28 Days Later to answer his question.
  2. Figure out the date that your next period is predicted to start, according to 28 Days Later. There are a few different ways to go about this and we are curious which are the most obvious. There are no wrong answers.
  3. Use 28 Days Later to log symptoms.  The app predicted you would have mild cramps, but they are severe. Update the cramps icon.
  4. Add a new symptom to the symptoms list. Find zombie pictures in your phone’s photo gallery that represent 3 different severities for “susceptibility to illness,” and put them into 28 Days Later.
  5. Share your daily prediction with a “blood buddy” friend.

Great, you’ve completed all the tasks.  We have a few follow up questions:

  1. Can you imagine using this app to track your period?
  2. Which specific features appealed to you?
  3. Which specific features did you dislike?
  4. What was your overall impression of the paper prototypes?
  5. Which design was easier to use?
  6. Do you have any more specific feedback about features, usability, or the interface?
  7. If both apps were available in the app store, which would you download?
  8. Do you have any other questions or comments about the app?

Thank you again for participating.  Your contribution helps ensure we don’t run off with a “great” design idea that is totally incomprehensible and unusable for the people we are designing the app for!

Time Estimates

Introduction:  5-7 minutes to give the information, get settled, and begin.

Testing:  Each question will take about 3 minutes.  About a minute to read the task, and 1-3 minutes for them to perform the task.  All tasks can be easily accomplished in under a minute, but if our design is confusing, it could take up to 3 minutes (which doesn’t sound long, but would feel very long if a user were trying to accomplish a very simple task).  Since there are 5 tasks and 2 prototypes this part would take about half an hour.

Questions:  10-15 minutes to allow time for as much feedback and debrief as possible.

Total:  About 45 minutes.

Testing Schedule

Toni and Mia will recruit at least two people each to complete the prototype testing. We will be asking friends and friends of friends at this point. At least one person will have been a participant in the survey research study, but none of the cultural probe respondents will be available. Recruited women will be representative of our target audience and personas. They will be in their 20s or 30s and have varying symptoms and regularity.

Our team members are available at different times of the week. Janeen is only available on weekends. Mia is free weekends and weekdays after 3:30. Skatje’s schedule varies. Toni is available evenings and most weekends.

We will analyze and discuss our findings in person on November 9th. Each prototype test will involve 2 team members (one to run the paper prototype and one to facilitate/take notes). The tests will take place between Halloween weekend and the first week of November.

Contribution Report

Mia constructed the task list and script. Toni and Janeen created prototypes A and B, respectively. Skatje generated the testing schedule. Janeen assembled the information into this post.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s