...
Learnability
This design is very pretty learnable to the first time user. The large buttons, underlined links, and tabbed interface give many affordances to the user to instruct the on how to use the site. The majority of the site takes on a form interaction style with the user, which allows the user to operate in a setting that they are used to seeing. The fact that some preference screen and edit screens can only be reached by certain screens will delay learnability by the user needing to recall the process to get to a certain interface. This can be fixed by a slightly adjusted layout providing more access points to similar pages throughout the website.
Visibility
Efficiency
Efficiency may not be as optimal as it could be. Users have to add bills individually so a user creating multiple similar bills would have to enter the same information in many times. Also, many changes like deleting a bill can only be done through certain interfaces such as the household view and not through the household itself, which hurt both learnability and efficiency. Editing bills is made efficient by having much of the information autofilled for the user.
Error Prevention
While hurting efficiency, deleting bills individually helps prevent errors.
Design 2
; however, users may ignore confirmations out of habits and still delete bills accidentally. There is no error recovery currently in place so if a delete is mistakenly made, the user must redo their previous work. It is also ambiguous if deleting a household deletes the entire household or just unlinks it from the account which could cause further errors. Bill status is shown clearly in every interface which will allow any mistakes that have been made in submitting the bill to be seen immediately after the mistake is made.
Design 2dd
Storyboard 2
Rob Miller is a returning user of Housebill.com. He navigates to the site's home page, where he is greeted by the friendly "Welcome to Housebill!" banner. Because he is an experienced user, Rob does not bother looking at the main page with the screenshots and just types in his username, "BobtheBanker," and password, "SuperSecretBob," into the column on the left for returning users. He clicks the "Login" button, which takes him to his User Page. Here, he sees his username, a list of the households that he is a part of, his current balance, and the credit card that he has on file. Under these pieces of information are collapsible/expandable lists that detail the bills that he has due, the money he owes to other members, the money that other members owe him, and his recent activity. On the left column of the User Page, Rob sees a button to add new households. Under that, but also in the left column, Is the pertinent information to his most commonly accessed household. Here he sees that household's address, a list of members, and a list of pending members. These pending members are people who have requested to join the household, but have not yet been approved by the members of the household. Rob decides to click on one of the households, which was titled "MyHouse".
...
Not great. Does not allow user to undo transactions, although before a transaction goes through the user must review a confirmation page.
Design 3
...
Storyboard 3
Analysis 3
Learnability
dd
Visibility
...