Designing for Mobile Devices in Higher Education Research
Posted December 21, 2010on:
While researching mobile library services, I’ve read a few research papers produced by other projects recently. Doing so has provided some guidance on our own research techniques and allow me to make comparisons with our own findings. One very comprehensive project in particular has proved quite informative: The California Digital Library Mobile Device User Research Project conducted a range of thorough research on the mobile strategy for their institution. Their Mobile Strategy Report includes details of surveys and interviews which they carried out earlier this year. The findings were used to detail barriers to mobile use and make recommendations when designing for mobile devices. I’ve decided to present some of their findings as I have found many similarities to our own findings. The design recommendations are also useful as they apply to all higher education institutions who may be thinking about developing mobile services. I do recommend you read the full report if you are interested in this area of research and design.
Designing Native Applications and Mobile Websites
There is a lot of debate on whether to design for native applications or provide a mobile website. As native applications are designed for a particular platform they work on a limited number of handsets. It also means that you may have to design a native applications for each platform separately which could be three or more if required. However, a mobile website is accessible to more mobile users as users are not required to download anything before use and you don’t need the approval of an app store like iTunes before it is available. California Digital Library (CDL) research indicates that a mobile website is currently the best option. Perhaps the website should be prioritized first and then development for a native application can follow. The report points to the book by Brian Fling, Mobile Device Design and Development which provides guidelines on the circumstances when a native application is the best route:
- Charging for it
- Creating a game
- Using specific locations (though some devices are able to detect location through browser applications)
- Using cameras
- Using accelerometers (to detect motion or rotation)
- Accessing file systems
- Offline users
Research findings and recommendations:
Smartphone ownership: “Smartphone ownership will likely increase over the next couple of years.” – the findings from the surveys conducted at University of Edinburgh in March and November this year support this conclusion as they have shown an increase in smartphone ownership by 17% to 67%.
Activities on mobile devices with internet: “They are used less for academic purposes and are also not used often for uploading content.” – this is also supported by our own survey findings which revealed a similar story. Top activities on internet capable mobile devices included finding information such as directions or opening hours, email and text messaging, reading news articles and blogs but not academic content, social networking and video & music consumption.
Library resources for research on internet enabled mobile devices: “Most interviewees did not want to do actual academic research on their mobile devices. Despite this there was still interest in having the option to access library databases, catalogues and resources from mobile devices.” A great metaphor is referenced in the report which describes Internet consumption on mobile devices very well:
Desktop internet is like scuba diving, where the search can be “immersive” and “invites exploration and discovery.” Mobile internet use is closer to snorkeling, where”shallow dipping in and dipping out of content for quick checking of key content is desired.
(Hinman et al., 2008)
– Again this supports our findings which showed that half of respondents had not accessed any library services using their mobile devices.
- Keep in mind that ownership of internet capable mobile devices may not translate to high usage of academic mobile tools.
- Gear mobile sites and apps towards the mobile user who is looking for quick pieces of information (no complicated tasks).
- Make library websites, databases and catalogues available on mobile devices, but do not provide all the functionality of desktop versions.
- Provide easy methods to transfer research and resources to other devices, such as by email.
Reaching your mobile audience: Something that was not directly surveyed at UoE, California Digital Library found that 60% of students ranked fellow students as the most likely sources for finding out about new tools and services. Consequently spreading the word about new tools and services can be difficult. This is something for UX2 and UoE to be aware of when designing mobile library services.
- Auto-detect mobile devices and automatically display mobile version of a site (though always provide obvious links back to the full version of the site).
- Create mobile websites rather than apps whenever possible so that users do not need to download software in advance of using it.
- Advertise through a variety of channels, including campus or departmental emails, campus websites, library websites, and blogs.
Overall CDL design recommendations:
- Set up testing practices and environments for the most heavily used device platforms (Apple iOS, RIM Blackberry OS, and Android OS). Test with physical devices where possible rather than emulation environments.
- Support mobile web access as opposed to building standalone mobile applications.
- Adopt and maintain web analytical tools to accurate mobile device tracking and usage statistics for online services.
- Continue to survey constituents and end-users annually or bi-annually to capture rapidly changing behaviours.
The recommendations provided are based on the research findings and are therefore very useful. Evidence supporting the creation of a mobile website first is something which we hope to explore in the focus group next year. As other platforms follow Apple’s example and provide native applications, it will be interesting to see how user behaviour and attitudes change. Web analytics are also important as forward planning can help to monitor the success of mobile library services and identify when further advertising is required. Again this is something that will be explored during the development and implementation of mobile library services within the UX2 project.