Mobile library presence

1,453 views
1,357 views

Published on

California Library Association's Academic Interest Group Webinar presentation.

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,453
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Mobile library presence

  1. 1. Building a Mobile Presence for Your Library: Current Case Studies<br />Matt Critchlow, Michele Mizejewski, Dan Suchy<br />May 11, 2011<br />
  2. 2. Matt Critchlow<br />Web Technical Manager <br />University of California, San Diego Libraries<br />Michele Mizejewski<br />Web Initiatives Librarian<br />University of California, San Francisco<br />Dan Suchy<br />User Services Technology Analyst<br />University of California, San Diego Libraries<br />
  3. 3. Overview<br />What content to include in your mobile presence?<br />Should you develop an app or a mobile web site?<br />You have a mobile site! Now what?<br />
  4. 4. UCSF: By the Numbers<br /><ul><li>The only UC campus devoted exclusively to health sciences
  5. 5. Comparatively small student population with approximately:
  6. 6. 20,400 staff (includes hospitals)
  7. 7. 2,400 faculty
  8. 8. 2,940 students enrolled in degree programs
  9. 9. 1,620 residents (physicians, dentists and pharmacists in training)
  10. 10. 1,030 postdoctoral scholars
  11. 11. First launched mobile site in May 2010 </li></ul>Source: http://www.ucsf.edu/about/facts-figures<br />
  12. 12. UCSD: By the Numbers<br /><ul><li>UCSD includes six undergraduate colleges, five academic divisions and five graduate and professional schools
  13. 13. UCSD Libraries consist of 8 libraries, with more than 7,300 people streaming through the libraries each day.
  14. 14. Library website resources are accessed more than 87,500 times each day.
  15. 15. Fairly large student population:
  16. 16. 23,000 undergraduates
  17. 17. 4,200 graduates
  18. 18. 26,000 faculty and staff</li></ul>Source: http://www.ucsd.edu/explore/about/facts.html, http://libraries.ucsd.edu/about<br />
  19. 19. Going Mobile<br /><ul><li>First big decision:
  20. 20. optimize your existing web site for mobile?
  21. 21. create a separate mobile site or app?
  22. 22. Feb. 2011: Smart phones outsell PCs for the first time*
  23. 23. Trends indicate that the future of the web is mobile!</li></ul>*Source: http://news.yahoo.com/s/ap/20110209/ap_on_re_us/us_tec_techbit_smart_phone_sales<br />
  24. 24. Mobile vs Desktop<br />Source: http://www.morganstanley.com/institutional/techresearch/mobile_internet_report122009.html<br />
  25. 25. Source: http://www.pewinternet.org/Infographics/2011/Generations-and-gadgets.aspx <br />Mobile Saturation<br />
  26. 26. Design and IA Tips<br /><ul><li>Keep content concise!
  27. 27. Most-used content goes at top level
  28. 28. Chunk information and use drilldown to minimize scrolling
  29. 29. Minimize need to type whenever possible
  30. 30. Use existing guidelines like the iOS Human Interface Guidelines*</li></ul>* http://developer.apple.com/library/ios/#documentation/userexperience/conceptual/mobilehig/Introduction/Introduction.html<br />
  31. 31. What to Include?<br /><ul><li>Identify info and services your users would want to access on mobile
  32. 32. Some ways to do this include:
  33. 33. look at stats for your main web site to see what people are viewing with mobiles
  34. 34. see what other libraries and campuses are offering
  35. 35. surveys or focus groups
  36. 36. Make it usable! Less is more.
  37. 37. Always link back to full site </li></li></ul><li>UCSF Mobile Device Usage<br />
  38. 38. Most Bang for the Buck?<br /><ul><li>With limited time or resources, focus on the most heavily used content types for your audience
  39. 39. Some possibilities:
  40. 40. Informational look-ups (hours, locations)
  41. 41. Catalog look-up and circ functions
  42. 42. Ask a question by phone, email, text
  43. 43. Showcase content (tours, digital collections, tutorials)
  44. 44. Searching article databases and reading articles
  45. 45. Reading ebooks
  46. 46. Making room or computer reservations
  47. 47. Maps and floor plans
  48. 48. LibGuides content
  49. 49. Wordpress blogs</li></li></ul><li>The Problem of Control<br /><ul><li>Third party content may or may not offer mobile interfaces
  50. 50. databases
  51. 51. ebooks
  52. 52. library catalog
  53. 53. Inconsistent approaches and quality
  54. 54. Test any VPN or proxy requirements and how they work in mobile environments</li></li></ul><li>Library or Campus?<br /><ul><li>If there is a campus mobile site, the library should be represented
  55. 55. Users want key services in one place
  56. 56. In reality, sometimes that = just the catalog
  57. 57. If no campus site, consider blazing the trail with a library site
  58. 58. Proof of concept and possible beginnings of campus collaboration</li></li></ul><li>UCSF Mobile<br />
  59. 59. UCSF Library Mobile Usage<br />
  60. 60. UCSD Libraries Mobile<br />
  61. 61. UCSD Libraries Mobile Usage<br />
  62. 62. Apps vs. Websites<br />Mobile apps are not the same as mobile websites.<br /><ul><li>Apps are software designed for mobile use and coded for a specific smartphone platform.
  63. 63. Mobile Websites are web pages designed for mobile use and built to work regardless of smartphone platform.</li></li></ul><li>Websites<br />Apps<br />
  64. 64. Why go with a mobile app?<br /><ul><li>Your users already think of everything as an app
  65. 65. The "apps are sexier factor"
  66. 66. Content can be stored in the app and available offline
  67. 67. Access to smartphone bells and whistles
  68. 68. Gives your library a presence in the Apple/Android app stores
  69. 69. You have access to programmers who know the language(s)
  70. 70. You have the budget</li></li></ul><li>So what's the catch?<br /><ul><li>Costs
  71. 71. Varying technologies depending on platform
  72. 72. Apple -> Objective-C
  73. 73. Android -> Java
  74. 74. BlackBerry -> Java
  75. 75. Palm -> C/C++
  76. 76. Symbian -> C++
  77. 77. Windows Mobile -> C++
  78. 78. Potential issues with support
  79. 79. Limited audience
  80. 80. Updates must go through app store vetting process</li></li></ul><li>Why go with a mobile website?<br /><ul><li>Reach the most people
  81. 81. Low development cost
  82. 82. Web Standards</li></li></ul><li>More control over content<br /><ul><li>Redirect users to your mobile site
  83. 83. Consistent statistics
  84. 84. Instant Updates (no app store vetting)
  85. 85. Search engines will index your site</li></li></ul><li>Reuse Content<br /><ul><li>Using a CMS like WordPress or Drupal?
  86. 86. Even if you’re not, you can probably reuse content</li></ul>Hours Data<br />Regular Website<br />Mobile Website<br />
  87. 87. Mobile Website Frameworks<br /><ul><li>“Write Less, Do More”
  88. 88. Advantages and Overview</li></li></ul><li>So what's the catch?<br /><ul><li>Your users already think of everything as an app
  89. 89. The "apps are sexier factor”
  90. 90. Some of the new HTML5/CSS3 features aren’t standardized yet or available in all browsers
  91. 91. Mobile frameworks are still relatively young
  92. 92. Still missing access to features like accelerometer, camera
  93. 93. Potential for duplicate content</li></li></ul><li>Hybrid Frameworks<br />Appcelerator and PhoneGap<br />Source: http://www.phonegap.com<br />
  94. 94. The Mobile Site is Live! Now What?<br />Develop a maintenance strategy<br /><ul><li>How does content get added and weeded?
  95. 95. Who decides what is relevant for mobile?
  96. 96. Maintaining 2 (or more) sets of content </li></ul>Reuse content whenever possible!<br />Iterative development<br /><ul><li>Gather feedback from users
  97. 97. Watch stat trends
  98. 98. Make improvements incrementally and over time</li></ul>Market your new site<br /><ul><li>mention on your main site
  99. 99. mention on facebook, twitter
  100. 100. create signs, cards, etc</li></li></ul><li>Tips and Lessons Learned<br /><ul><li>Let usage stats and mobile trends help prioritize your efforts
  101. 101. Stats and reports on trends can also secure get buy-in to develop
  102. 102. Assign someone to be your library's mobile trend spotter
  103. 103. Brevity, brevity, brevity.
  104. 104. Always test using real mobile devices
  105. 105. Realize that you should constantly reassess and improve in small ways</li></li></ul><li>Resources and further reading<br /><ul><li>Libraries and the Mobile Web(February/March 2011)
  106. 106. Pew Internet on Mobile
  107. 107. iOS Human Interface Guidelines
  108. 108. UCLA Mobile Web Framework
  109. 109. CDL Mobile Support Policy for CDL Licensed Resources
  110. 110. Mobile: Letting Go of the Device and Building for Innovation
  111. 111. Mobile First Helps with Big Issues
  112. 112. W3C Mobile (browser check)
  113. 113. HTML5Rocks
  114. 114. CSS3.info
  115. 115. Appcelerator Titanium Framework
  116. 116. PhoneGap Framework
  117. 117. jQuery Mobile Framework
  118. 118. Sencha Touch Mobile Framework</li></li></ul><li>Mobile Sites/Apps Mentioned<br /><ul><li>Northwestern Mobile
  119. 119. DCPL for iPhone
  120. 120. NCSU Mobile
  121. 121. UCSF Mobile
  122. 122. UCSD Libraries Mobile
  123. 123. SJPL Mobile App
  124. 124. LMU Library Mobile</li></li></ul><li>Building a Mobile Presence for Your Library: Current Case Studies<br />Matt Critchlow, Michele Mizejewski, Dan Suchy<br />May 11, 2011<br />

×