...
Our group learned many things about development, design, and prototyping throughout this course and the iterative design process of making our application. One of the main things was that we aren't the users. We realized that you don't know how users will interact with your product until you allow them to access it in some level 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.
Another issue thing we faced is learned was that in design there is not always a right answer, while in the Hall of Shame
what one user might consider as a convenient feature another user may consider
Another big thing we learned about design is there is not necessarily one right answer. In many cases we studied in class on the. In class when we viewed Hall of Shame examples, most times there were blatant aspects that we as a class could agree made the interface more difficult to use. However, most applications don't have clearly defined lines like this. We frequently encountered user issues where one user might consider an aspect a convenient feature while another user considers it a terrible design flaw. We encountered these decisions even amongst our team, such as when we were deciding how to do self populating fields in our add/edit bill interface.