This document summarizes case studies of mobile sites created by university libraries. It discusses key decisions in developing a mobile presence like whether to optimize an existing site or create a separate mobile site/app. It provides tips on design, content to include, and maintenance. Examples from UCSF and UCSD Libraries are presented, showing their mobile sites increased usage of key resources like the catalog on mobile devices. The document considers tradeoffs of mobile sites vs apps and development frameworks.

1. Building a Mobile Presence for Your Library: Current Case StudiesMatt Critchlow, Michele Mizejewski, Dan SuchyMay 11, 2011

2. Matt CritchlowWeb Technical Manager University of California, San Diego LibrariesMichele MizejewskiWeb Initiatives LibrarianUniversity of California, San FranciscoDan SuchyUser Services Technology AnalystUniversity of California, San Diego Libraries

3. OverviewWhat content to include in your mobile presence?Should you develop an app or a mobile web site?You have a mobile site! Now what?

4. UCSF: By the NumbersThe only UC campus devoted exclusively to health sciences

5. Comparatively small student population with approximately:

6. 20,400 staff (includes hospitals)

7. 2,400 faculty

8. 2,940 students enrolled in degree programs

9. 1,620 residents (physicians, dentists and pharmacists in training)

10. 1,030 postdoctoral scholars

11. First launched mobile site in May 2010 Source: http://www.ucsf.edu/about/facts-figures

12. UCSD: By the NumbersUCSD includes six undergraduate colleges, five academic divisions and five graduate and professional schools

13. UCSD Libraries consist of 8 libraries, with more than 7,300 people streaming through the libraries each day.

14. Library website resources are accessed more than 87,500 times each day.

15. Fairly large student population:

16. 23,000 undergraduates

17. 4,200 graduates

18. 26,000 faculty and staffSource: http://www.ucsd.edu/explore/about/facts.html, http://libraries.ucsd.edu/about

19. Going MobileFirst big decision:

20. optimize your existing web site for mobile?

21. create a separate mobile site or app?

22. Feb. 2011: Smart phones outsell PCs for the first time*

23. Trends indicate that the future of the web is mobile!*Source: http://news.yahoo.com/s/ap/20110209/ap_on_re_us/us_tec_techbit_smart_phone_sales

24. Mobile vs DesktopSource: http://www.morganstanley.com/institutional/techresearch/mobile_internet_report122009.html

25. Source: http://www.pewinternet.org/Infographics/2011/Generations-and-gadgets.aspx Mobile Saturation

26. Design and IA TipsKeep content concise!

27. Most-used content goes at top level

28. Chunk information and use drilldown to minimize scrolling

29. Minimize need to type whenever possible

30. Use existing guidelines like the iOS Human Interface Guidelines** http://developer.apple.com/library/ios/#documentation/userexperience/conceptual/mobilehig/Introduction/Introduction.html

31. What to Include?Identify info and services your users would want to access on mobile

32. Some ways to do this include:

33. look at stats for your main web site to see what people are viewing with mobiles

34. see what other libraries and campuses are offering

35. surveys or focus groups

36. Make it usable! Less is more.

37. Always link back to full site UCSF Mobile Device Usage

38. Most Bang for the Buck?With limited time or resources, focus on the most heavily used content types for your audience

39. Some possibilities:

40. Informational look-ups (hours, locations)

41. Catalog look-up and circ functions

42. Ask a question by phone, email, text

43. Showcase content (tours, digital collections, tutorials)

44. Searching article databases and reading articles

45. Reading ebooks

46. Making room or computer reservations

47. Maps and floor plans

48. LibGuides content

49. Wordpress blogsThe Problem of ControlThird party content may or may not offer mobile interfaces

50. databases

51. ebooks

52. library catalog

53. Inconsistent approaches and quality

54. Test any VPN or proxy requirements and how they work in mobile environmentsLibrary or Campus?If there is a campus mobile site, the library should be represented

55. Users want key services in one place

56. In reality, sometimes that = just the catalog

57. If no campus site, consider blazing the trail with a library site

58. Proof of concept and possible beginnings of campus collaborationUCSF Mobile

59. UCSF Library Mobile Usage

60. UCSD Libraries Mobile

61. UCSD Libraries Mobile Usage

62. Apps vs. WebsitesMobile apps are not the same as mobile websites.Apps are software designed for mobile use and coded for a specific smartphone platform.

63. Mobile Websites are web pages designed for mobile use and built to work regardless of smartphone platform.WebsitesApps

64. Why go with a mobile app?Your users already think of everything as an app

65. The "apps are sexier factor"

66. Content can be stored in the app and available offline

67. Access to smartphone bells and whistles

68. Gives your library a presence in the Apple/Android app stores

69. You have access to programmers who know the language(s)

70. You have the budgetSo what's the catch?Costs

71. Varying technologies depending on platform

72. Apple -> Objective-C

73. Android -> Java

74. BlackBerry -> Java

75. Palm -> C/C++

76. Symbian -> C++

77. Windows Mobile -> C++

78. Potential issues with support

79. Limited audience

80. Updates must go through app store vetting processWhy go with a mobile website?Reach the most people

81. Low development cost

82. Web StandardsMore control over contentRedirect users to your mobile site

83. Consistent statistics

84. Instant Updates (no app store vetting)

85. Search engines will index your siteReuse ContentUsing a CMS like WordPress or Drupal?

86. Even if you’re not, you can probably reuse contentHours DataRegular WebsiteMobile Website

87. Mobile Website Frameworks“Write Less, Do More”

88. Advantages and OverviewSo what's the catch?Your users already think of everything as an app

89. The "apps are sexier factor”

90. Some of the new HTML5/CSS3 features aren’t standardized yet or available in all browsers

91. Mobile frameworks are still relatively young

92. Still missing access to features like accelerometer, camera

93. Potential for duplicate contentHybrid FrameworksAppcelerator and PhoneGapSource: http://www.phonegap.com

94. The Mobile Site is Live! Now What?Develop a maintenance strategyHow does content get added and weeded?

95. Who decides what is relevant for mobile?

96. Maintaining 2 (or more) sets of content Reuse content whenever possible!Iterative developmentGather feedback from users

97. Watch stat trends

98. Make improvements incrementally and over timeMarket your new sitemention on your main site

99. mention on facebook, twitter

100. create signs, cards, etcTips and Lessons LearnedLet usage stats and mobile trends help prioritize your efforts

101. Stats and reports on trends can also secure get buy-in to develop

102. Assign someone to be your library's mobile trend spotter

103. Brevity, brevity, brevity.

104. Always test using real mobile devices

105. Realize that you should constantly reassess and improve in small waysResources and further readingLibraries and the Mobile Web(February/March 2011)

106. Pew Internet on Mobile

107. iOS Human Interface Guidelines

108. UCLA Mobile Web Framework

109. CDL Mobile Support Policy for CDL Licensed Resources

110. Mobile: Letting Go of the Device and Building for Innovation

111. Mobile First Helps with Big Issues

112. W3C Mobile (browser check)

113. HTML5Rocks

114. CSS3.info

115. Appcelerator Titanium Framework

116. PhoneGap Framework

117. jQuery Mobile Framework

118. Sencha Touch Mobile FrameworkMobile Sites/Apps MentionedNorthwestern Mobile

119. DCPL for iPhone

120. NCSU Mobile

121. UCSF Mobile

122. UCSD Libraries Mobile

123. SJPL Mobile App

124. LMU Library MobileBuilding a Mobile Presence for Your Library: Current Case StudiesMatt Critchlow, Michele Mizejewski, Dan SuchyMay 11, 2011