...
- User while editing a bill removed himself from the bill accidentally. Since the bill no longer affected him, he could not access the bill again to re-add himself to the bill
Severity: CriticalMajor
Solution: Show all bills connected to the household under household so that user has access to bills even if they do not apply to him at the current moment.
- User entered password incorrectly when signing up, and then could not log into account.
- Severity: Major
- Solution: Have a confirm password entry textbox where the user must type in a matching password.
- User accidentally paid a bill and was confused when the bill disappeared.
- Severity: Minor
- Solution: Have a pop-up that asks if the user is sure of their action. However, the bills are still available to the user under the "Paid Bills" section and they can correct their mistake there.
- User could not understand timeline functionality, was not able to find all bills due within two weeks.
- Severity: Minor
- 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.
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.
...