Versions Compared

Old Version 12

changes.mady.by.user Unknown User (mattocks@mit.edu)

Saved on

compared with

New Version 13

changes.mady.by.user Katrina Marie Panovich

Saved on

Key

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

...

  1. Easily creating a timer.
    1. It is extremely important that a user can quickly and easily create a timer with a simple web based interface.
  2. A user needs to be able to browse their personal timers
    1. A users should be able to browse their personal timers either via a login system or local storage on their computer.
  3. Sharing a timer with your team
    1. The main focus of this app is for users to be able to share timers with each other, so it must be easy to invite other people to use your timer. This can be done via email or Facebook integration.
  4. Finding timers that are relevant to you
    1. A user should also be able to search timers based on their interests and location. A notion of public and private timers should be introduced. 
  5. Sending customizable notifications
    1. A user should be able to set notification settings for each timer that they follow, as well as be able to set default notification settings that apply to all new timers they follow. A texting service like twilio could be used to send text notifications, as well as simple email notifications.
  6. Displaying a timer
    1. When a user visits an individual timer page it should have a large simple countdown timer prominently displayed with few other distractions.

TA Feedback.

This project, as it stands, isn't a stretch. There are a few ways you can handle this - by broadening the user population, or making it mobile (for a reason). We'll discuss this further in person.

You don't actually discuss classes of users, just specific characteristics. Try to think about who your users are more holistically - thinking about them as characteristics first is backwards.

Your list of tasks seems incomplete. For instance, what about changing a timer that is shared with you?

You also don't seem to really get a good feel for what the tasks your users use to solve your problems, and instead you describe actions that your app will let users take. Don't forget that the next step is to make three separate designs - you shouldn't already have picked one. Think of task analysis as the analysis of tasks that need to be done to solve the problems.

Please also be careful about gender generalizations when talking about user personae.

I'd appreciate it if you made these changes, since we'll be working off this document for the whole rest of the project.