Expense App Evaluation

Issues

1. • There is no way to undo delete, or edit actions
   • User control & freedom; Error reporting, diagnosis, and recovery.
   • After deleting or editing an expense, the user might change their mind and want to return the previous expense, but would be unable to do so.
   • Recommendation: add a button to undo the last action.
2. • Save and Delete buttons are next to each other
   • Error prevention.
   • The two buttons are a few pixels apart, making it likely that the user will misclick the wrong button.
   • Recommendation: Move the delete button to the left of the list, or add a confirmation dialogue when saving and deleting an expense. These operations would likely not be common in an expense app, so the tradeoff with efficiency is worth it for safety.
3. • When amount is $0, it is not displayed
   • Error prevention, Consistency & standards.
   • First, $0 expense likely means error from the user, however if the app allows it, it does not display 0 like the other amounts, which is especially apparent when the expense is payed by both Neo and Trinity, as seen in the screenshot.
   • 
   • Recommendation: either not allow the user to enter $0, or allow it and display it like other amounts as "$0".
4. • Default date not set
   • Flexibility & efficiency
   • The default date does not have value, which means during everyday use, the users will have to set the date to today for every expense entered (the date clears after each submit).
   • Recommendation: set the default value of date to today, and do not reset the date after each submit, as the next expense is likely to have the same date.