Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Interview 1

  • Twitter** Follows 600+ accounts*** Keep general tabs on various groups of people/areas of interest
    • Phone interface is most natural
    • In the morning, scroll back as far as the client will go to catch up*** Wouldn't want tweets going to e-mail because it's harder to Mark All as Read (don't want to miss out) than to be limited by Twitter's scroll-back history
    • Receives tweets from important people as text messages
    • Favorites tweets she wants to revisit
    • Occasionally would want a tweet via e-mail
  •  
  • Google Reader** Doesn't want to think about how many unread items she has** Wants to split the feeds into Good and Meh (my words) so that she can regularly read the good without feeling bad about ignoring the meh
  • E-mail** Uses e-mail as a TODO list (regretfully)** Would see tweets and RSS items as TODOs and doesn't want that* Sometimes, when she's expecting a stressful e-mail, she doesn't want to open her e-mail client at all
  • Has never used an automatic filterer that worked well. She's the best judge of what she would find interesting and feels the investment is worth it.

...

  1. Users want to be able to identify the most useful information as soon as possible (hence why Interviewee 2 does not like Facebook or Twitter, and utilizes the front page of reddit)
  2. Not all users feel overwhelmed by their high-volume information streams, so our application should reflect this
  3. Though users may have too much to read, they don’t want to have too little##  We should allow users to adjust this quickly and on the fly## example: when a user checks in with our application to consume some information, she runs out of things to read. So she adjusts her preferences to increase the amount of information she sees and our application immediately adds previously unseen items to her visible updates.
  4. Our application would be most beneficial if users could access it on their computers and on the phone## We discussed this and for the scope of the class we will focus primarily on use via phone (but will more than likely have to make sure users can access it comfortably via computer)

...