...
- (Minor) There was a small bug where we didn't have the correct information in the header bar (i.e. a section was blank)
- We already fixed this with a quick patch.
- (Major) Users were much slower on the mobile version. This is a concern, especially since the primary goals of the mobile interface were convenience and efficiency.
- We should label assignments with both the color and name of the class.
- Really old assignments could be moved to the bottom of the list in order to show more recent ones.
- (Minor) "Shared" may be confusing without the prompting of the usability test.
- We could replace the "Shared" check-box with a radio button between "Private" and "Public."
- (Cosmetic) The colors chosen are sometimes too similar.
- One approach would be to allow users to choose their own colors.
- We could also create a more sophisticated algorithm for choosing distinct colors.
Reflection
During our iterative design and implementation process, we arrived to some conclusions tht may be generalized for future projects.
First, although obvious in retrospect, users do not always use the interface as originally intended. We observed this during paper prototyping, as users repeatedly clicked on a class name whenever we asked them to add an assignment. We decided to embrace it and this was implemented in our final design.