Beginning with the January 2012 usage statistics, monthly search statistics include the number of mobile searches done in Melvyl by campus.  Additionally, the mobile search numbers display the number of searches from all mobile devices (iPhone, Motorola Droid) that represent 5% or more of the monthly totals.  The number of monthly mobile searches for each campus Melvyl is tallied separately from the number of monthly desktop searches.  Together the two numbers provide a more accurate overview of the total use of each campus Melvyl.

See Melvyl Statistics for more information.

In the summer of 2010, CDL’s User Experience Design team began investigating the possibility of creating a mobile version of CDL’s newly redesigned website. As part of its design process for creating an interface optimized for mobile devices, the team set out to test its prototype mobile website, m.cdlib, with users. This article describes the process of creating the tool used for mobile usability testing and includes the following topics:

• Challenges of Mobile Usability
• Research
• Designing and Building the Prototype
• Modifying the Rig
• A Few Lessons Learned
• Resources

This article will not delve into the details of usability testing or the results of the tests.

Challenges of Mobile Usability

The California Digital Library (CDL) has had a formal usability practice in place since 2004, and we have carried out usability tests on our websites and web services using laptop or desktop computers. For usability testing of our mobile site, we briefly considered using an emulator with our existing set-up. However, as CDL’s senior usability analyst and DIY enthusiast, I rejected that idea knowing there had to be a way to test on a more authentic platform. After all, interacting with an emulator on a full size screen using non-mobile input devices — i.e., full size keyboard and mouse — is not the same as holding a device in one’s hand and using it.

Another consideration was how to best capture users’ behaviors and interactions, so we could share them with our team. For standard usability testing, we used screen recording software and a backup digital audio recorder. Our team had recently acquired a digital camcorder, but using it wouldn’t give us a detailed view of the screen of the mobile device or users’ interactions with it. This camcorder set-up would also force the user to remain relatively still. Instead, I decided to build something handheld that would hold a small camera in place over the mobile device.

Research

I began with a Google search for existing set-ups using phrases, such as “mobile device usability.” After browsing through a few pages of results, I discovered this post. The author had included two images of the rig he had built, and its simplicity made me confident that I could create our own rig based on his design. I just had to mind two constraints: money and time.

The bowmast.com design used an analog CCTV camera, but we did not have the budget or the time to acquire that kind of equipment. I decided to see if I could use CDL’s webcam, which staff normally used to hold video-conferences. Then, I went to the website of my neighborhood TAP Plastics store to research the cost of creating the plastic part of the rig that would hold the camera and the mobile device in place.

After browsing TAP’s selection of plastics, I estimated that it would cost about $30 in materials to make the rig’s frame. I went to my supervisor to get approval before heading to TAP to see if they could manufacture the rig within three days. (We were scheduled to hold our first usability test the next week.) The manager at TAP Plastics said that all they needed were the exact measurements for the rig, so my next step was to finalize my design.

Designing and Building the Prototype

The bowmast.com design was a great starting point. I briefly considered putting together a flat platform with an attached gooseneck for the camera, which would have provided the greatest flexibility in positioning the camera. However, I had great difficulty finding a suitable gooseneck at my local hardware store, and I decided that the resulting Frankenstein rig might distract users.

I proceeded to design my version of rig based on the following photo:

Figure 1: http://www.bowmast.com/mob-device-cam/

I had to figure out the dimensions and angles that would allow the rig to work with CDL’s webcam, a Logitech C905. Then, I needed to communicate those measurements to TAP Plastics. After contemplating how long it would take for me to sketch a diagram by hand or learn the basics of Google SketchUp, I decided that a three-dimensional, cardboard prototype would be the most efficient and accurate way to convey my design to TAP.

The rig in the photo looked a little skinny to me, so I decided to make the width of the rig just smaller than the width of an iPhone 4. (I knew that our users could be using other mobile devices, but I went with the device that I had on hand.) I cut a strip of cardboard from an Amazon.com box with a box cutter and metal ruler and started playing around with lengths and angles. I didn’t have the webcam with me when I was experimenting, so I did my best to imagine how the webcam would attach using my memory and the following profile image of the webcam from Logitech’s product page:

Figure 2: http://www.logitech.com/en-us/webcam-communications/webcams/devices/6600

After finding a satisfactory configuration, I cut the cardboard to length and used tape to fix the angles in place. I used my iPhone and an app called Clinometer to measure the angles and a ruler to measure the lengths. With a Sharpie marker, I wrote the measurements directly on the cardboard and tape, as shown below:

Figure 3: Prototype - Side View

Figure 4: Prototype - Top View

I dropped off the cardboard prototype at TAP, where they suggested using 3/16” thick acrylic.

Modifying the Rig

Two days later, I picked up the manufactured rig and the prototype. TAP did a great job, and I rushed back to try it out with the webcam. My original thought was to attach the webcam to the rig using its integrated clip.

Figure 5: Webcam Clipped to Rig

Well, doing that resulted in a recorded image that was upside down. (D’oh!) To fix this, I stuck the webcam to the underside of the overhang with Scotch mounting adhesive. This worked okay, but I worried that the webcam would detach due to gravity eventually. I decided to supplement the adhesive with a zip tie, which required me to drill two holes in the overhang. (I had asked TAP to drill one big hole in the middle to accommodate a bolted camera like the one used in the bowmast.com implementation.)

Figure 6: Rig and Drill

The result actually looked better, because the webcam didn’t jut out over the platform as much.

Figure 7: Close-up of Webcam

To complete the rig, I had to figure out how to attach users’ devices to the rig. I didn’t want to use adhesive Velcro, because it would be difficult to remove and it felt like an imposition on the user. (I personally would not want someone sticking something on my gadgets.) The method I used had to be effective at holding the device in place, non-marking, and removable. I originally wanted to use 3M Command adhesive strips, but the local drugstore had Scotch mounting tape, which seemed like a satisfactory alternative.

Figure 8: Final Set-up with iPhone

A Few Lessons Learned

During the course of our mobile usability testing sessions, we learned the following from the different environments we encountered:

• Certain lighting situations required adjustments to prevent glare on the mobile device’s screen.
• Differing levels of ambient light required changing the exposure level of the camera at each location.
• Meeting users in their workplaces meant that sometimes there were interruptions.

Overall, the video capture of users’ interactions using the rig and Logitech’s software worked very well. We were pleased by the following discoveries:

• The rig held the camera perfectly steady in relation to the device being used, so we could see exactly what actions participants took.
• The Logitech webcam’s software allowed us to disable autofocus and fix the focus of the camera, which is absolutely essential for testing. (Otherwise, the camera’s autofocus would focus on the user’s hand instead of the screen.)
• The software also allowed us to adjust the exposure levels of the camera, which was important because of the different levels of ambient light we encountered in different locations.
• The webcam’s microphone was positioned perfectly to capture the participant’s voice. (This was an unexpected benefit of using the rig.)

Participants’ feedback about their experience using the rig itself was generally very positive. They reported that the webcam’s placement did not obstruct their view of the screen. And after a few minutes, most participants seemed to interact with the rig as though they were holding just their mobile devices. That is, they didn’t seem to notice the rig at all.

Designing and building the rig was one of the most satisfying parts of this round of mobile usability testing. The most frustrating part was converting the captured video files from WMV to MP4 format. (The only video editing software I had was iMovie, which uses MP4. Unfortunately, Logitech’s software recorded in WMV.) After several unsuccessful conversion attempts, I found an application called Wondershare Video Converter that I could use for free, as long as I didn’t mind having a giant watermark on the video. Since I would be screening the video for the User Experience Design team only, I did not bother to eliminate the watermark by buying the full version of Wondershare.

With the success of this first rig, I hope to have the opportunity to refine both the rig itself and our process for mobile usability testing in future usability projects.

Resources

Websites:
Bowmast User Experience Design & Research
TAP Plastics

Hardware:
Logitech C905 Webcam
Windows laptop to run Logitech software

Software:
Logitech software to set up webcam (exposure, focus, etc.) and record video
Wondershare Video Converter to convert video files
iMovie to obtain highlight clips to share with team
Clinometer to measure angles

Since the launch of our new web presence in January, 2010, the User Experience Design team has continued our commitment to finding new and timely ways to serve our users’ needs. In the summer of 2010, we embarked on a mobile user research project that culminated in our creation of a new mobile version of CDL’s website. We want to support our users whether they are at their desks or on the go in a mobile context.

We have enabled an auto-detect feature to recognize when certain mobile devices are trying to access the CDL website; the auto-detect automatically sends users to the mobile site. We’re providing quick hits of information geared specifically for mobile use– things like contact info, directions, system status, CDLINFO news.

Learn more about the process we used to arrive at this first iteration of the mobile site.

We hope to continue to grow and develop our site by monitoring use patterns, incorporating more features and content as needed. So stay tuned and visit us (http://www.cdlib.org) when you’re on the go…

Last week, the British Library published an articulate and impressive 10-year strategy, their 2020 Vision. They tie the ideas to their organizational mission and vision, and they make 6 forecasts. I’m quoting from the document:

• The consumption of media by young people will continue to increase across the full range of media channels, day and night, seven days a week.
• Free, ‘open access’ scholarly works will enable improved access and will drive research increasingly towards open access models.
• Mobile devices will soon overtake personal computers as the most common web access tools worldwide.
• Users will increasingly demand searches that identify sources of quality information and expect prompts for new information based on previous patterns of activity–giving new context to content.
• Technology will encourage and enable discourse in a more diverse, open and participative way.

Are these outrageous claims? I don’t think so. And I assume that they are based on the consultative interviews and research described by Dame Lynne Brindley in her Foreword to the document. Interviews and research are a good way to determine the lay of the land, and even to look ahead a little bit.

Recently, CDL released the findings from a summer-long look into “All Things Mobile.” Here are just a few of the things that we found out:

• Slightly more academic survey respondents own mobile phones without internet (61%) than mobile devices that with internet (53%). Faculty were the most likely respondents (63%) to own a mobile device with internet, followed by graduate students (53%) and then undergraduates (41%).

• Most told us that they prefer to use internet from their laptops rather than their mobile devices, yet many don’t carry laptops to campus or have internet access at home.

• Most noted that they did not want to do actual academic research on mobile devices. Many see research as a difficult activity that would only be more difficult on a mobile device.

• Most of our participants prefer notifications by email instead of text message.

One of the recommendations from the study was to keep on top of this topic by revisiting it every six to twelve months, because it is subject to so much change. Interviews and research have to be done over and over, in other words, and some of it has to be done locally.  Some of these trends are simply not universal.

Here, I think of Char Booth‘s call for local studies: “understanding local patron culture is essential to creating used and useful (technology) services. Environmental scanning is a scalable means of using data to test your notions of true/false.” Sometimes, we can apply the comparable studies others have done, and sometimes we need to do our own. In the case of mobile, it looks like we need to do our own.

Here at CDL, we’ve been working hard all summer immersing ourselves in all things mobile. And we’re excited to share with you our findings and next steps for mobile support and development for some of CDL services.

To re-cap, our mobile investigation was conducted as a three part harmony:

1. Rachael Hu, User Experience Design Manager, and Alison Meier, UC Berkeley iSchool intern, conducted a user research inquiry to understand how UC students, faculty and staff were adopting and utilizing mobile devices in their academic workflow. The final report and detailed project findings and comprehensive resource listings as well as other project deliverables can be found on the CDL mobile research wiki project page (https://confluence.ucop.edu/display/CMDUR/Home ). In addition to the main report are separate reports on Discovery and Delivery and Digital Special Collections.
2. Holly Eggleston, Electronic Resource Analyst and Resource Liaison Coordinator, with the cooperation of the Resource Wranglers Team, drove the effort to test, investigate, and formulate CDL’s mobile activation and support strategy for CDL Licensed Resources.  For details about supported resources, known technical issues and considerations for campuses who are implementing mobile, please see http://www.cdlib.org/services/collections/mobile.html .  
3. Lena Zentall, Discovery and Delivery Project Manager, spearheaded an effort to develop Discovery and Delivery mobile strategy for their services, such as UC-eLinks and Request. Findings from the user research inquiry as well as a detailed mapping of the inter-relation of these services with CDL licensed resources helped to formulate next steps for mobile accessibility.

We plan to communicate our harmonized findings and next steps to UC campuses and beyond throughout the fall. Stay tuned for more information. But in the meantime, please take a look at the CDL mobile research wiki.

We hope you find the information as illuminating as we did…

CDL is beginning a formal exploration and investigation into mobile device use on the UC campuses and how that impacts our services. We will be:

1. Studying mobile device user patterns to inform CDL service development
2. Using the Discovery & Delivery Program as a case study for CDL’s mobile readiness
3. Assessing licensed database and e-journal vendors’ mobile functionality and campuses’ readiness to access this functionality

Rachael Hu, CDL’s User Experience Design Manager, is leading the mobile device user research component with the assistance of an intern from UC Berkeley’s School of Information. Coordinating the Discovery & Delivery Program’s case study is Lena Zentall, Project Manager, and Holly Eggleston, CDL’s Resource Liaison Coordinator and Electronic Resource Analyst, is leading the assessment of the mobile functionality of licensed resources and campuses’ readiness to adopt and deploy this functionality.

Our goal is to gather user-based evidence to help formulate guidelines in developing mobile compatible versions of CDL services, as well as aid in the mobile discovery and delivery of licensed resources. We also hope to hear about and coordinate with UC campuses and their work surrounding mobile service development.

Work is beginning now and will continue through the summer. CDL will be conducting literature reviews, comparative analysis of mobile application and service functionality as well as talking to library and IT staff, students, faculty, and researchers. We will also be conducting a survey of end-users and in-person interviews as needed. We are sensitive to our campus colleagues’ time and work priorities so will coordinate our campus communication efforts. The ultimate goal of our exploration will be to provide services that better support campuses in their role as facilitators for meeting UC patrons’ growing mobile-based information needs.