...
A user can see all of their bills on a single page. We took an idea from the way that groupon lets users organize their coupons. In particular, users can see bills that have already been paid, and those that are yet to be paid. This gives us a high degree of error correction, in case a user accidentally marks a bill as paid. This means that bills are never actually deleted, and gives the user a full record of their payments. The bills are arranged in a table, ordered by date due.
Any bill that has not been paid can be edited by the user. This page looks very similar to the page for adding a bill, except for the fact the the existing bill's information is pre-loaded into the text box fields. In this way, the user can exactly see the bill state at any time, and can change any aspect of the bill.
...
- User could not understand timeline functionality and was not able to find all bills due within two weeks.
Severity: MinorMajor
Solution Solution: Have the user use the timeline for the long term, and have them use the calendar view for any bills due in the short term. bills ordered by date so that it is clearer to see that bills are being added by date when the slider moves.
- User thought that slider on timeline was too small, and had trouble clicking on it to drag it
Severity: cosmetic
Solution: make the slider larger and more visible to the user
- User was unable to find all bills due within two weeks
Severity: Minor
Solution: Order bills by date on the view bills page or include the timeline as another part of the view bills page and consolidate the two features
- User tried to click on the number in the Overdue Bills section on the main page to access their overdue bill
Severity: Minor
Solution: Allow clicking on the overdue bills section to take the user to all of the bill that are overdue
Reflection
Our group learned many things about development, design, and prototyping throughout this course. We learned about the iterative design process of making an application. One of the main things that we had to deal with was that we are not the users. We realized that you don't know how users will interact with your product until you actually allow them to access it. This comes in the form of prototyping, which provides challenges we were not used to as a developer. It is difficult to design a backend for an ever changing front end implementation.
...