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

2. David Woodbury Project 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 7

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 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 10

11. Project timeline Enhancements added by other developers Bug fixes as needed for new devices Iterative development since launch new 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.edu12

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. Dont 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 users context 28

29. Expose hidden, useful content 29

30. Jason Casden Technical 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 users 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 36

37. 37

38. 38

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

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 40

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 41

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 –Doesnt develop internal expertise 42

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

44. Best practices Standards and official guidelines –Useful, but slow-moving –Dont get stuck 44

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 45

46. Content Adaptation 46

47. Separating data from presentation 47

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

49. Recommendations 49

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

51. Play 51

52. Collaborate Campus efforts External projects Steal what you like –Improve it, so it can be stolen back 52

53. In Summary… Mobile websites are becoming very sophisticated Mobile web app development is web development –just a little different 53

54. David Woodbury Assessment 54

55. Assessing the site 55

56. Pageviews by service Whats popular at NCSU Libraries 56

57. Views by device Whats popular at NCSU Libraries 57

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 58

59. Coming Soon! Patron account information (checkouts & renewals) Access to electronic reserves for classes Building wayfinding Tools for staff 59

60. Questions? 60