Final Presentation
Project Recap
Our Client
Gallery is a photo album management tool made for organizing and sharing photos online. It is akin to other content management systems where a server is required along with site administration skills on the part of the gallery owner. It was created as part of an open source project under the GPL software license, and is maintained and developed by a community of users and developers. The development is a distributed effort, with collaboration from around the globe. It is the most widely used open source system of its kind.
Current Gallery Users
Most gallery users are adept with computers and specifically maintenance for sites hosted on private servers. Most users are very familiar with the ins and outs of gallery and have been using it for many years. Forums, IRC channels, and mail-lists provide some pace where Gallery users gather and communicate, but they are a largely disperate group of either photo or web enthusiasts from different walks of life.
The Problem
To reach new users, the gallery project team wants to refurbish the system to make it simpler and easier. They want to reach ‘average’ users but have little inkling who these people might be, since user research is difficult in an open source project where the code is simply put out there, one of our goals was to help them this.
The Process and Solution
Over the course of the semester we have tried to identify their ‘middle-ground’ user and scope our project around them. While conducting contextual inquiry, we found that the end-user or viewer needed to be taken into consideration during development. Through the use of personas, scenarios, and lo-fi prototype, we aimed to make the look and feel of the system very simple.
Hi-Fi Prototype
Based on our contextual inquiry research, we drew major redesign goals from that amalgamated successful practice of the current Gallery version. Our key improvements upon included creating a minimalistic look and feel, made browsing images fast and easier, provided a way to comment on and region tag images, and created automatic notifications. But now, it’s time to take it to the users.
User Testing
We completed 5 user tests to learn what features users liked, which they had trouble using, and to see if there were any design oversights on our part. We used the data we collected to improve our prototype.
We had users perform 3 tasks concerning commenting, tagging, browsing, using different view types, changing settings. After users completed the tasks, they were asked questions regarding their experience with our prototype. The tasks are below.
- Imagine that you received an email notifying you that your friend Ryan has uploaded new pictures to his album on his website. You received this notification in your email with a link that brings you to the current (Notifications) page that is open in front of you. Browse through Ryan’s photos and find your favorite one. When you find a photo you like, try to comment on the photo.
- Browse the photos some more, try viewing the Travelogue album in different view-types. When you find another photo that you like, try to tag the photo with descriptive information. Also, try to find a way to print or email the photo, but don’t actually do either.
- Return to the notifications page. Imagine that you’d like to receive notifications for another one of Ryan’s albums as well. Navigate to the settings for notifications and change them accordingly. Save your changes.
User Testing Successes
Look and Feel
All users commented on the simple, uncluttered design, that helped to focus attention on the images.
Mosaic Image view with thumbnails
All users commented on this being the most usable and preferred way for browsing images.
Notifications
Users mentioned liking that people can subscribe to user’s albums and be notified when new images are uploaded.
User Testing Findings
Below is an overview of the usability issues found during user testing. We will examine the 5 most important issues and provide more detail of each issue and propose a possible solution. For a longer list of findings, please see our user testing page.
|
No.
|
Usability Problem |
Priority
|
|
1
|
‘Next’ and ‘Prev.’ buttons require precision to operate |
High
|
|
2
|
Mosaic view does not provide large image for browsing |
High
|
|
3
|
Image controls (Print, email, etc) are hidden and difficult to discover |
High
|
|
4
|
Carousal view type is confusing and out of control |
High
|
|
5
|
Common features (Notifications, Settings) are difficult to locate |
Medium
|
Finding 1
|
1
|
‘Next’ and ‘Prev.’ buttons require precision to operate |
High
|
User had trouble with the next and previous buttons because they were only visible on mouse-over and required too much precision. This is a violation of Fitts’s Law. Also, mouse-over effect was inconsistent, possibly due to how the software implemented the rollovers.
Possible Solutions:
Assign a fixed space for these buttons near the bottom of the picture. Another possible solution is to split the image into two halves, and allow the users to click anywhere in the two halves to control next and previous actions.
Finding 2
|
2
|
Mosaic view does not provide large image for browsing |
High
|
Users wanted larger main image while viewing the album in the mosaic view. The thumbnails consume too much real estate in the default view.
Possible Solutions:
Provide larger image size and reduce thumbnail panel in the default view and provide options to view an image at different sizes. Other possible solution could be to provide a slideshow option that would enable users to view images in a larger size.
Finding 3
|
3
|
Image controls (Print, email, etc) are hidden and difficult to discover |
High
|
User had trouble with the print / email / download buttons because they were only visible on mouse-over and because mouse-over effect is inconsistent, possibly due to how the software implemented the rollovers. This issue is similar to the next / previous buttons issue.
Possible Solutions:
Provide better visual cues and mouse-over effects, assign a fixed space for these buttons near the bottom of the picture. Another possible solution could be to show the control initially and have them fade away within a few seconds so the user has a chance to see them.
Finding 4
|
4
|
Carousal view type is confusing and out of control |
High
|
Too many images are in focus at the same time and fast rotation makes it difficult to chase an image. Clicking on an image leads to a new window, which disrupted the image viewing experience.
Possible Solutions:
Redesign the Carousal to only allow on image to be in focus to draw and keep the users attention on a single image. Alternatively, we could discard carousal feature and focus on simpler experience using a mosaic view and slideshow, considering many users found it useless.
Finding 5
|
5
|
Common features (Notifications, Settings) are difficult to locate |
Medium
|
Users have to go through many links to find the settings page. It wasn’t obvious that My Gallery contained their settings, notifications, and potentially their albums. Perhaps users did not understand the scenario correctly or we did not sufficiently explain the relationship between them and the Gallery administrator.
Possible Solutions:
Put Setting and Notifications links in a prominent place on the interface and allow shortcuts to these pages from all other pages, such as the header near the login box.
Future Directions
If our team were to continue with this project, these are the things we would do next:
- we would first implement fixes for usability issues and conduct another round of user test.
- Second, our team would further develop new prototypes and view types, then user test to compare the results to the other prototype.
- Third, start exploring admin interfaces for secondary persona.
- Finally, meet with other Gallery team to consolidate research and design.





