Prototype Review

• First, provide a general review of the prototype and its ability to serve ALL of the UX stories I provided for the assignment.

This prototype does allow the user to navigate between screens quite seamlessly and intuitively. You are also able to create an account and log in. There is some what of a lacking however with the stats of the application on the log in pages. There is one states page if the form is not filled out it shows an alert at the bottom. I would like to be able to see what would happen if one area is filled out wrong or forgotten.

There also does not seem to be a functionality that allows the to sort the to do list items by due date which was one of the requested items in the user story. There is a place to set a due date but the prototype does not walk the user through how this would work which I think would be nice to have incorporated.

It is very clear when you click on an item that there is the option to mark the item as complete how it does not show what will happen to this once that item is marked as complete.

The edit button is clearly shown but there is not an edit screen that displays what this process would look like or how to edit each item.

• Then, choose a set of heuristics or principles from Module 1 and evaluate the UI against those criteria.

Visibility of System status

• Overall I would say there is good feed back about what is going on though this is hard to tell since it is only an early stage prototype. In terms of states I would be nice to see more of these states and how the app is going to handle errors, lack of information, incorrect passwords etc.

Match b/t system and real world

• In terms of link between real world it should be evaluate how a to do list works in person and what the perks are of why people are more likely to use pen and paper than a TO DO list app the already exists.

User control & freedom

• It feels very controlled but this is heavily because this is still a prototype. I think for a to do list app however it should feel almost similar to pen and paper, easy to see what you’ve done and what you have to do, possibly both on one screen.

Consistency and Standard

• In terms of consistency and standard this did feel that if fit a lot of the norms and what would be expected in terms of navigation and functionality.

Error Prevention

• There does seem to be a lack of error prevention due to the lack of indicators letting the user know which fields are required and which once are not.

Recognition rather than recall

• In terms of recognition rather than recall the major functionality of the app is pretty intuitive, ex. how to add a new task, mark it as complete. There are a few icons that I have not seen used before that could possible lea to some confusion on their functionality.

Flexibility and Efficiency

• This is something that would come with high frequency of the app but could be nice to add short cuts or custom options that the user may want to do frequently.

Aesthetic and minimalistic design

• This app does a good job of keep the design aesthetically pleasing as well as very minimalistic.

Help and documentation

• The lead in to using the app does a great job of explaining to the user and questions they may have. However, the user is very likely to skip through this wanting to get to the app and know how to use it with out instructions.
• Then, evaluate the completeness of the prototype. Does it adequately illustrate flow? Are the appropriate states of each view well represented? Does each view communicate primary action? Is there sufficient distinction between different actions? What do you like or dislike about the presentation of the prototype?

Overall this prototype works well in terms of documentation and description. I feel there could be more added to this about the functionality of the states of the pages for the login as well as what happens when items are added, deleted, sorted, and completed.

I would also like to see what each of the function do like setting items with a certain level priority, and what attachments and

• Finally, wrap up by providing some general recommendations for improving the prototype, its delivery, and its design, etc.

This prototype is off to a good start but I would to see as a more functional piece really being able to feel like you are using the app with more screens developed.