Your SlideShare is downloading. ×
0
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
"Providing Mobile Web Library Services"
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

"Providing Mobile Web Library Services"

1,093

Published on

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,093
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
22
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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

×