...
Upon creation of the bill, the user is taken to the main User Page screen. Here, the user sees the test House household, along with the bill that was just created. The Pie chart is no longer grayed out, and the calendar now displays the date when the water bill is due. There is a "news" subsection of the test House Household, and it updates to say that "testUser added waterbill."
Rob then clicks on the "test Household" link itself, which gives him a breakdown of what him and friendUser each owe, and offers him the ability to pay his bill with a "pay" button. Rob is not ready to pay his bill yet, so he decides that he has made enough progress for one day and signs out of his session.
...
Learnability of the site for the initial tasks is good. The website uses large buttons to transition the user to the different states of creating an account, creating or linking to an initial household, and adding or paying a bill.
Visibility
d
Efficiency
Learnability for some of the less frequently used tasks like deleting a household or bill may be more difficult since there is no information scent on the main user interface to direct users to where these additional features can be found.
Visibility
Visibility on this site is very much like learnability. There is little information scent to direct users to the less frequently used features of the site making their visibility poor. This is a trade off for good visibility of the states the user would normally find himself in
Efficiency
An advantage of this design is the efficiency of having most states that the user would want to see available from the original user view. The direct manipulation of bill creation helps error prevention by only allowing "approved" information to be entered into the bill form; however, users trying to create bills quickly will find the direct manipulation will slow down progress by making users need to click more objects instead of being able to navigate through the form by tabs.An advantage of this design is the efficiency of having most states that the user would want to see available from the original user view.
Error Prevention
The confirmation screen after creating a bill helps prevent error prevention by making users confirm the bill information twice. There appears to be nowhere to edit bills once they are the bill is created, which will allow errors to propagate if they are created. The detachment of having the delete bills and household from the main interface will prevent accidental deletions helping error prevention.