As a locker owner, i want to be guided through the process of setting it up

As a locker owner, i want to be guided through the process of setting it up

Wireframes

Note: The following wireframes have Singly in the header, but this is generic functionality for Lockers, regardless of where they're hosted.

Acceptance criteria

• Browser support

• Chrome (latest stable)
• Firefox (latest stable)
• Safari (latest stable)

• Selenium Test(s)

• Start to finish with installing all services (Facebook, Google Contacts, Twitter, GitHub, Flickr) using test OAuth tokens.
• Test using bad tokens
• Test with bail out

• Backend Tests

• Connector Endpoints
• Collection Endpoints

• HTML matches Wireframes (roughly)

• User Test with working prototype with 5 social web users (facilitator asks each participant to complete an action). This process is based on Steve Krug's approach defined in "Rocket Surgery Made Easy".

• Video camera captures the user's reactions, as well as what they're doing on the screen.
• Welcome: Facilitator welcomes participant with pre-defined script (5m, p70)
• Questions: Questions are asked about participant (2m, p73)
• The Tour: User is presented with a brief home page tour (3m, p75)
• The Tasks: Facilitator asks user to complete the task of completing the wizard (5-35m, p76)
• Probing: Facilitator provides participant time to go back and probe the process they just went through in order to get more feedback about what they're thinking (5m, p78)
• Wrapping Up: Ask "Does that seem like a worthwhile way to spend XXX minutes?", and thank them for their time and help (5m, p79)

User testing, Week of August 15

• John Britton:

  • Part 1: http://www.youtube.com/watch?v=-ss7PjOsCRs
  • Part 2: http://www.youtube.com/watch?v=gh_LrzpXNn0

• Martha Denton:

  • http://www.youtube.com/watch?v=R-Kjlj7Usmo

• Jasmine Trabelsi:

  • Part 1: http://www.youtube.com/watch?v=m02m3jDLffc
  • Part 2: http://www.youtube.com/watch?v=-5gJCXssjac

• High level feedback (with a more thorough and robust set of notes following the completion of the 5 usability tests):

  • People were receptive to the service avatars for their simplicity
  • 3 of 3 subjects were confused by the spinning wheel. They all thought they had to wait around for it to finish spinning.
  • Showing node.js was confusing, even for John Britton (Twilio's ex-hacker extraordinare)
  • People had guesses as to what "contacts," "links" and "photos" might be, but they lacked certainty.
  • No one wanted to read the copy on the front page regarding what a locker is. Everyone just wanted hit, "Let's get started." I had to ask them to read the copy.
  • 3 of 3 subjects were most uncomfortable adding Facebook.
  • Folks had no idea what to do when they first got the mainly white page after connecting a service. One refreshed, one moved it down below.