"Providing Mobile Web Library Services"


Published on

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

"Providing Mobile Web Library Services"

  1. 1. The Education Institute Providing Mobile Web Library Services David Woodbury, NCSU Libraries Fellow Jason Casden, Digital Technologies Development Librarian NCSU Libraries
  2. 2. David Woodbury Project Planning and Design
  3. 3. Why invest in mobile development? 5 billion reasons
  4. 4. “ People expect to be able to work, learn, and study whenever and wherever they want to.”
  5. 5. Our motivation
  6. 6. About NC State University Libraries <ul><li>We serve the largest higher education institution in the state </li></ul><ul><ul><li>31,000 students & 8,000 faculty members </li></ul></ul><ul><ul><li>Large focus on science, technology, engineering & mathematics </li></ul></ul><ul><li>History of innovation & collaboration </li></ul><ul><ul><li>Endeca discovery layer on our catalog </li></ul></ul><ul><ul><li>Early mobile library site (MobiLIB) </li></ul></ul>
  7. 7. Our mobile services
  8. 8. NCSU Mobile Web (Campus Site)
  9. 9. NCSU Libraries Mobile Team <ul><li>Jason Casden, Digital Technologies Development Librarian </li></ul><ul><ul><li>Developer </li></ul></ul><ul><li>David Woodbury, NCSU Libraries Fellow </li></ul><ul><ul><li>Project manager </li></ul></ul><ul><li>Markus Wust, Digital Collections and Preservation Librarian </li></ul><ul><ul><li>Developer & co-creator of MobiLIB </li></ul></ul>
  10. 10. Project timeline <ul><li>Project planning, site wireframes in September (one project manager) </li></ul><ul><li>Development and testing in October (two developers) </li></ul><ul><li>Formal launch & promotion in November </li></ul><ul><li>Main website redirect in December </li></ul>Three months from planning to launch
  11. 11. Project timeline <ul><li>Enhancements added by other developers </li></ul><ul><li>Bug fixes as needed for new devices </li></ul>Iterative development since launch new new new
  12. 12. Our mobile services <ul><li>Locations & Hours </li></ul><ul><li>Computer Availability </li></ul><ul><li>Book & Article Search </li></ul><ul><li>Room Reservations </li></ul><ul><li>GroupFinder message board </li></ul><ul><li>Reference Services </li></ul><ul><li>News & Events </li></ul><ul><li>Webcam Feeds </li></ul><ul><li>Link to campus mobile site </li></ul>http://m.lib.ncsu.edu
  13. 13. Locations & Hours
  14. 14. Computer Availability
  15. 15. Catalog Search
  16. 16. Catalog Search
  17. 17. Reference Services
  18. 18. GroupFinder (message service)
  19. 19. What to mobilize? <ul><li>What services are currently available? </li></ul><ul><li>What services are applicable on a mobile device? </li></ul><ul><li>What services translate well to the mobile environment? </li></ul><ul><li>What tools can be created easily? </li></ul><ul><li>What would be fun to see? </li></ul>
  20. 20. Don’t mobilize everything <ul><li>Nearly 100 links! </li></ul><ul><li>Always can link back to home page, if needed </li></ul>
  21. 21. “ Mobile” is not just shrinking the page
  22. 22. Use only essential, relevant content
  23. 23. Use only essential, relevant content
  24. 24. Reduce options, simplify
  25. 25. Limit data to mobile context
  26. 26. Limit data to mobile context <ul><li>For time oriented data, we assume current day & time </li></ul><ul><li>We assume action oriented </li></ul>
  27. 27. Use the mobile interface
  28. 28. Provide appropriate tools for the user’s context
  29. 29. Expose hidden, useful content
  30. 30. Jason Casden Technical Planning and Implementation
  31. 31.
  32. 32. When to Make a Native App <ul><li>Charging for it </li></ul><ul><li>Creating a game </li></ul><ul><li>Using specific locations* </li></ul><ul><li>Using cameras </li></ul><ul><li>Using accelerometers </li></ul><ul><li>Accessing the filesystems </li></ul><ul><li>Offline users </li></ul>* Actually available to web-based applications
  33. 33. The Case for Mobile Web Apps <ul><li>“ I believe that unless your application meets one of these native application criteria, you should not create a native application, but should instead focus on building a mobile web application.” </li></ul><ul><li>— Brian Fling, “Mobile Design and Development” </li></ul>
  34. 34. WolfWalk <ul><li>Native iPhone App </li></ul><ul><li>Geolocated special collections images </li></ul><ul><li>Track the user’s current location </li></ul><ul><li>Browse historical images of sites on campus </li></ul>
  35. 35. Shoutouts <ul><li>The project team </li></ul><ul><ul><li>Tito Sierra, Jason Casden, Steven Morris, Markus Wust, Brian Dietz, Todd Kosmerick, Joseph Ryan </li></ul></ul>
  36. 36. WolfWalk, Two Ways
  37. 37.
  38. 38.
  39. 39. Distribution Channels <ul><li>Open vs. Controlled </li></ul><ul><ul><li>Administrative overhead </li></ul></ul><ul><ul><li>Bottlenecks </li></ul></ul><ul><ul><li>Technical restrictions </li></ul></ul>
  40. 40. Our tools <ul><li>Mobile website </li></ul><ul><ul><li>XHTML 1.0 transitional </li></ul></ul><ul><ul><li>CSS </li></ul></ul><ul><ul><li>non-essential JavaScript and AJAX </li></ul></ul><ul><li>MIT Mobile Web Open Source Project </li></ul><ul><li>Leaned on pre-existing web services </li></ul><ul><li>Targeted higher-end devices </li></ul>
  41. 41. No developers? <ul><li>Tools that require only HTML knowledge </li></ul><ul><ul><li>WordPress, iWebKit, iUI, jQTouch, Dashcode… </li></ul></ul><ul><ul><li>Good for static content </li></ul></ul><ul><ul><li>May lack good multi-tiered device support </li></ul></ul>
  42. 42. No developers? <ul><li>Vendors </li></ul><ul><ul><li>Boopsie, Terribly Clever… </li></ul></ul><ul><ul><li>Can manage mobile development process for you </li></ul></ul><ul><ul><li>You may lack control over the final product </li></ul></ul><ul><ul><li>May be expensive </li></ul></ul><ul><ul><li>Doesn’t develop internal expertise </li></ul></ul>
  43. 43. Data Reuse <ul><li>CatalogWS </li></ul><ul><li>Library Hours </li></ul><ul><li>Study Room Reservations </li></ul><ul><li>GroupFinder </li></ul>
  44. 44. Best practices <ul><li>Standards and official guidelines </li></ul><ul><ul><li>Useful, but slow-moving </li></ul></ul><ul><ul><li>Don’t get stuck </li></ul></ul>
  45. 45. Lots of Devices Top Level iPhones, Android phones, Palm Pre Large touch screens, sophisticated web capabilities Middle Level Blackberry, Nokia smartphones, Windows mobile, etc. May lack touch screen and some CSS and JavaScript capabilities. Low Level Web-enabled flip phones Small screens, low web functionality
  46. 46. Content Adaptation
  47. 47. Separating data from presentation
  48. 48. Testing CC BY-SA 2.0: http://www.flickr.com/photos/wfryer/3929189482/
  49. 49. Recommendations
  50. 50. Be Agile <ul><li>Rapid development cycle </li></ul><ul><li>Think iteratively </li></ul><ul><li>Adjust to change quickly </li></ul><ul><li>Avoid paralysis </li></ul>
  51. 51. Play
  52. 52. Collaborate <ul><li>Campus efforts </li></ul><ul><li>External projects </li></ul><ul><li>Steal what you like </li></ul><ul><ul><li>Improve it, so it can be stolen back </li></ul></ul>
  53. 53. In Summary… <ul><li>Mobile websites are becoming very sophisticated </li></ul><ul><li>Mobile web app development is web development </li></ul><ul><ul><li>just a little different </li></ul></ul>
  54. 54. David Woodbury Assessment
  55. 55. Assessing the site
  56. 56. Pageviews by service What’s popular at NCSU Libraries
  57. 57. Views by device What’s popular at NCSU Libraries
  58. 58. Further assessment <ul><li>Assess actual student needs </li></ul><ul><ul><li>Survey students </li></ul></ul><ul><ul><li>Study behaviors </li></ul></ul><ul><li>Invest in services that can be used in a variety of contexts </li></ul><ul><li>Get input from across library staff </li></ul>
  59. 59. Coming Soon! <ul><li>Patron account information (checkouts & renewals) </li></ul><ul><li>Access to electronic reserves for classes </li></ul><ul><li>Building wayfinding </li></ul><ul><li>Tools for staff </li></ul>
  60. 60. Questions?