1 / 60

The Education Institute Providing Mobile Web Library Services

The Education Institute Providing Mobile Web Library Services. David Woodbury, NCSU Libraries Fellow Jason Casden , Digital Technologies Development Librarian. NCSU Libraries. David Woodbury Project Planning and Design. 2. Why invest in mobile development?. 5 billion reasons. 3.

arnie
Download Presentation

The Education Institute Providing Mobile Web Library Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Education InstituteProviding Mobile Web Library Services David Woodbury, NCSU Libraries Fellow Jason Casden, Digital Technologies Development Librarian NCSU Libraries

  2. David WoodburyProject Planning and Design 2

  3. Why invest in mobile development? 5 billion reasons 3

  4. “People expect to be able to work, learn, and study whenever and wherever they want to.” 4

  5. Our motivation 5

  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) 6

  7. Our mobile services

  8. NCSU Mobile Web (Campus Site) 8

  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 9

  10. Project timeline Three months from planning to launch • 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 10

  11. Project timeline new new new Iterative development since launch • Enhancements added by other developers • Bug fixes as needed for new devices 11

  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 12

  13. Locations & Hours 13

  14. Computer Availability 14

  15. Catalog Search 15

  16. Catalog Search 16

  17. Reference Services 17

  18. GroupFinder (message service) 18

  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? 19

  20. Don’t mobilize everything • Nearly 100 links! • Always can link back to home page, if needed 20

  21. “Mobile” is not just shrinking the page 21

  22. Use only essential, relevant content 22

  23. Use only essential, relevant content 23

  24. Reduce options, simplify 24

  25. Limit data to mobile context 25

  26. Limit data to mobile context • For time oriented data, we assume current day & time • We assume action oriented 26

  27. Use the mobile interface 27

  28. Provide appropriate tools for the user’s context 28

  29. Expose hidden, useful content 29

  30. Jason CasdenTechnical Planning and Implementation 30

  31. 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 32

  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” 33

  34. WolfWalk • Native iPhone App • Geolocated special collections images • Track the user’s current location • Browse historical images of sites on campus 34

  35. Shoutouts • The project team • Tito Sierra, Jason Casden, Steven Morris, Markus Wust, Brian Dietz, Todd Kosmerick, Joseph Ryan 35

  36. WolfWalk, Two Ways

  37. 37

  38. Distribution Channels • Open vs. Controlled • Administrative overhead • Bottlenecks • Technical restrictions 39

  39. 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 40

  40. No developers? • Tools that require only HTML knowledge • WordPress, iWebKit, iUI, jQTouch, Dashcode… • Good for static content • May lack good multi-tiered device support 41

  41. 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 42

  42. Data Reuse • CatalogWS • Library Hours • Study Room Reservations • GroupFinder 43

  43. Best practices • Standards and official guidelines • Useful, but slow-moving • Don’t get stuck 44

  44. Lots of Devices 45

  45. Content Adaptation 46

  46. Separating data from presentation 47

  47. Testing CC BY-SA 2.0: http://www.flickr.com/photos/wfryer/3929189482/ 48

  48. Recommendations 49

  49. Be Agile • Rapid development cycle • Think iteratively • Adjust to change quickly • Avoid paralysis 50

More Related