Soo’s Detailed Project
Insights from user feedback
by Sooyong Chu
Insights from FireMelon
Now that we had a prototype that we can base from, we asked our fellow partner team FireMelon to give us initial feedbacks for our design. Team FireMelon provided positive insights that shaped our design more user friendly and efficient. Team FireMelon generally agreed that there were room for improvement but were fascinated with our initial design and idea. Luis, one of a team members of FireMelon, quoted “The prototype seems to have a good potential”. Kevin, another member from FireMelon commented that our app had a good potential for not only for university campus use but also for a wider community.
Their feedback was valuable because it was the first testing done by someone else other than our team members. It helped us to extend our views on how the design will develop for wider users. Our team did discuss about how our initial prototype may intimidate users with so many things going on one page. the user feedback reinforced our concerns and asked to be redesigned. Many times they asked us what each features did and we had to explain what they did, but they were corporative and patient and showed interest in our prototype layout. After going through their insights, our team were eager to improve our design as we new that the initial prototype had many things to be developed.
General feedback we received was that it was confusing what was going on on our homepage. Because we wanted to have every features to be available in one page, our prototype drawing may have caused confusion. But after explaining what each boxes and pop-ups were doing, they agreed that it would look more clean and simple.
Another important feedback was about privacy settings. They liked the feature of showing and hiding user’s location to other users but explained how our design may confuse users. Another important feedback was about how adding friends should be linked to school email, regarding the fact that some users may not use Facebook. Their insights and feedbacks covered things that our team missed or have not thought about when designing our prototype.
Design decisions, based on heuristics and user feedback
by Sooyong Chu
With insights and feedbacks we have received, our team discussed on how to improve our design. As we evaluated, first we decided to include features that were necessary in our design that we missed to implement. From visibility of system status, our design was on point except that we forgot to show the profile of current user. For match between system and the real world, we concluded that there was nothing much more we needed to do because our user interface is simple and direct. For user control and freedom, the main issue was that there was no feature that let users to create/destroy session on the main page, which was crucial to our focus and priority of our design. Another point out was made on consistency and standards in that use of buttons/bullets/boxes were inconsistent. Wendy also mentioned that current design my depict unclear difference between leave/end session. For error prevention Johnny and I suggested that some sort of assurance mechanism for leaving/ending session may be required. Also, users will only be able to join one session at a time, thus graying out other sessions when the user is already in a session. For recognition and recall we were concerned that the check in image may be unclear for users, and feedbacks we received today reinforced our concerns. For flexibility and efficiency of use, we concluded that we lack shortcut implementations for more advanced users. For aesthetic and minimalist design all of us agreed that our use of space is not efficient and thus may provoke overwhelming depiction for users. For help and documentation we did not provide any.
Now that we went through heuristic evaluation, we achieved further understanding of how we should develop our design. we considered highly on user feedback from last meeting and discussed how we should make changes. We divided design decision from high importance, middle importance and low importance. For high importance we listed implementing confirmation button, online/offline button, exit conformation pop-up, shortcut to leaving session, sign-up system and tag search bar. For confirmation button we will implement a button to confirm creating or ending a session. for online/offline button we will implement visibility shortcut UI for users. for shortcut to leave session we will add a shortcut next to check-in/check-out button to easily leave a session. for sign up system many ideas came up but we decided to create a signup system for users that do not have a Facebook account. These were considered high importance because these features directly defined what StudyTerminal should do to help future users achieve their desired goal.
Middle importance listed session details title change, current session user, change of main icon depending on session status and notification pop-up. We decided to change title of session details box to indicate if user is editing the details of an existing session or creating a new one. For current session user conflict we decided to display picture/name of the current user on the home page to identify who us currently using StudyTerminal. For notification pop-up we decided to have a notification text box pop-up for 3 seconds and then change the color of the notification button to alert the user.
Low importance listed map refresh button, clear direction for leave/end session, join new session pop-up, shortcuts for favorite/saved session and novice user wording. As we were discussing we realized that some features were unnecessary hence decided to think more about implementing them to our design in the future and not just yet. We had to make decisions on whether we wanted to follow our design style or to take in every feedback and heuristic evaluations to farther develop StudyTerminal. It took us awhile to go through every detail of heuristics and user feedback but realized how important and necessary it was to make our design better.