After the paper prototype user testing sessions, we decided to modify the general structure of the site. Although it was hard to identify from the three evaluations, we decided to limit the number of tabs on the menu bar mostly because of how small the screens are on the smartphone to have so many. We also changed up our main ‘recording expenditure’ page to not have a photo upload button. This is because we found that most of the users we interviewed wanted to just jot down the numbers quickly.
We also found that making the list, map, and chart interacting with each confuses the user significantly, and thus we made them separate from each other.
We were originally planning to make each of the bar on the chart be interactive, and make them lead to displaying the expenses for that day as a list. However, we could not find an api that would allow us to do that, and in addition, as stated before, making the charts and list interactive could end up confusing the user, so we removed that functionality altogether.
implementation
We conducted our user tests at two different places: one at a fraternity, and one at the student center on campus.
We wanted to look for smartphone users with a variety of background. They were quickly briefed with the fact that this website is to keep track of their expenditures. They were not shown any demos. The task is as follows:
Test Process 1
Here are the results from the testing.
Test process 2
Ways to fix Issues with usability: Mainly reorganizing the “Add Debts” page would clarify some confusion
Akira
I had a lot of fun making this website. I had never used jQuery Mobile, which handles things very nicely for the most part. It was also interesting to see the different problems we found when opening our site on the computer and a smartphone: some codes that worked on the computer crashed on the smartphone, or the size of the smartphone screen was much smaller than we had imagined. When having our prototype tested, I thought it was really interesting to see how much people who use the application for the first time get confused with what the makers thought was easy to understand. Ideally, I would want to continue working on this site and make the changes that reflect on the comments we received from our testers.
Nahom
I really enjoyed working on this website, I especially enjoyed working on the front end aspect of the site. The biggest difference was probably working on a mobile site rather than an actual one mainly because you have to consider and prioritize different things such as screen size which play critical roles when you transition from desktops to mobile devices. Overall, I think one of the things I would of tried to understand/work on more would be figuring out what features we can add and implement into the site using Flask. This was my first experience with the Flask framework, so I think given more time it would be one of the things that I would of tried to understand more and add to our application.