...
Figure 6 shows the "settle dispute" pop-up menu. In this pop-up menu, there is a "new amount" field that is defaulted to $0.00. This default has been chosen to make it easy for users to accept disputes (clearing the debt). This type of menu also makes it easy for the two users to agree on a new amount of the debt if they choose so. if the new amount is set to $0.00, the debt will be automatically deleted on both of the user's accounts.
Analysis: Dimensions of Usability
...
PROS
...
Learnability:
- Simple, table style interface.
- No “settings” menu to complicate things
- Large, easy to hit buttons (on touch screen phones)
- Consistent, clean layout
...
- Deletion and Dispute functions execute immediately, with no easy way to undo the action
- Deletion action is available for debts, so technically, someone could just delete all debts even though he/she has not repaid the lender
- “Disputes” button is on each person’s row in the main screen. This can be accidentally hit when a user tries to just click on a person’s row to see all of their mutual debts.
Design #2 Storyboard
Note: For some reason, the image link does not work. However, you can right click and click "view image" to get a larger view.
...
Safety: When there are faulty transactions, users have the ability to post a dispute for mistaken transactions. (Although not shown here in this design, the original poster of a transaction should have the ability to cancel it).
CONS
Learnability: While there are many features here that are commonly found in some well-known applications, it may be unclear what a transaction implies (as in, who is allowed to make a transaction and type of transaction). Since our implementation involves only one-way directional transaction relation, this may be difficult to learn or understand for users.
...
Suppose Sally wants to dispute a transaction with Bob, she can do so by viewing the details of her transaction with him. This will lead to a page that shows the total that she owes Bob, or however much Bob owes her. This also shows a list of dates and money amounts for every past transaction she has had with Bob. Next to each transaction where Bob claimed that Sally owes him money, Sally can click the “Dispute” button if she disagrees with that transaction. The “Done” button brings the user back to the home page.
Analysis: Dimensions of Usability
...
PROS
...
Learnability:
- The buttons are clearly labeled and accessible from the home page.
- All pages have buttons to easily return to the home page.
- The dates for transactions are listed so that the user can recall certain transactions.
- There are only five distinct pages that the user will see, making it simple for the user. The main page is the home page, and from this page the user can get to any of the other four.
Efficiency:
- There are no dialog boxes that pop up to confirm if a user wants to dispute or settle a transaction.
- The list of current transactions on the home screen shows that total amount of all transactions with another person. The user can choose to view more details by just clicking a button.
- The home page shows the total amount across all transactions that the user owes other people or that other people owe the user.
- Past users that the user has had transactions with are listed in a drop down menu so that it is easier for the user to add a new transaction with them.
Safety:
- All pages have buttons to easily return to the home page.
- The user can view the details of every transaction to double check for correctness.
- The user can dispute transactions that the claimer may have claimed incorrectly.
...