1. Mobile WebPacs John Wenzler Associate Library Dean San José State University Dr. Martin Luther King, Jr. Library San José, California USA John.wenzler@sjsu.edu NorCal IUG November 5, 2010

2. Alexis de Tocqueville and me

3. Outline Overview of the “Mobile Web” environment What does this mean for library web sites and OPACs? Current mobile web options for the III OPAC.

4. Networks -- “What does 3G mean?” 2G (Second Generation) GSM (AT&T, T-Mobile) CDMA (Verizon, Sprint) Data Transfer Speeds: 12KB-60KB/sec 3G CDMA2000, UMTS, HSDPA …. Data Transfer Speeds: 3MB-16MB/sec 4G LTE, WiMAX … ? Data Transfer Speeds: 30MB- 100MB/sec WiFi

5. Hardware Feature Phones Smart Phones Touch Screen Phones Tablets, Netbooks, ipad, ebook readers, ect.

6. Feature Phones Feature Phone Era (1998-2008) per Brian Fling, Mobile Design & Development 85% of the world-wide cell phone market as of 2010 Cameras, Text Messaging … Internet Access – “Horrible usability, enabling only minimal interaction with websites.” Jakob Nielsen’s Alertbox

7. Smart Phones The Smart Phone Era (2002-2010) per Brian Fling 10-15% of the world market (25-30% in US) QWERTY Keyboard, email, calendars, 3G and WiFi networks -- management tool Internet Access – “Bad usability, forcing users to struggle to complete website tasks” Jakob Nielsen.

8. Touch Phones Touch Phone Era (2007 - ?) iPhones, iPods, and copies such as Android Key Features: WebKit/Safari Browser, CSS & JavaScript support, Intuitive interface for data entry and surfing “The iPhone is the first mobile Internet device worth criticizing. It’s a starting point for mobile online services access, not an endpoint.” Jakob Neilsen

9. Other Stuff Tablet Computers, ebook readers, netbooks … Are they the Future? Do we have to change anything to adapt to them?

10. Software Native Apps Web Sites Web Apps

11. Native Apps Computer programs written to run on a specific phone hardware or on a mobile OS Some Mobile OSs  Mac OS X: a mobile version used in Apple Products  Android: Open Source, supported by Google  Windows Mobile: based Windows XP  Palm Web OS: based on webkit  Blackberry

12. Mobile Web Apps/Sites Written for Web Browsers -- HTML, CSS, JavaScript, AJAX You don’t need to install on your hardware If you can do everything on one page -- without browser chrome -- then you have Web App

13. Native Apps Pros Better Usability (if they are well designed) Can access more of the services provided by the phone’s OS Cons Need to create an app for many platforms if you want to give everyone access Vendors control users’ access to your App (App store) Your users have to find, download, and remember to use your App

14. Web Apps Pros Cheaper development costs, tools more familiar to libraries No need to develop for several OS or platforms Any one can access over the web Cons Device detection Displays differently on different browsers Native App usability is better

15. Three Strategies (per Nielson) Do Everything : Create two web sites (or more), and native apps for dedicated users. Rich, high use sites (i.e. Amazon, NPR, ESPN) Do One Thing: Create one version of your site optimized for mobile web browsers Do Nothing: Not many mobile users expected. Make sure that your regular site works OK for them

16. What does this mean for Libraries? What kind of mobile devices will our patrons be using? Will they use them to access library resources? What will they want to do with the library when they are on the move?

17. San Jose Library Mobile Patrons

19. Website  Mobile visits Oct 2009: 0.68%  Mobile visits Oct 2010: 2.16%  2.5 pages per visit; 1.5 minutes per visit WebPac  Mobile visits Oct 2009: 0.94%  Mobile visits Oct 2010: 2.98%  6 pages per visit; 4 minutes per visit *AirPac traditional? Browsers without JavaScript?

20. Mobile Library User Surveys California Digital Library (CDL): “Mobile Strategy Report” (8/18/2010)“Mobile Strategy Report Ryerson University Library, Toronto: “The mobile university: from the library to the campus” Reference Services Review (2/2010) Washington State University: “The use of handheld mobile devices: their impact and implications for library services” Library Hi Tech (1/2010) -- Specifically asks about OPAC usage

21. What Mobile Patrons want to do Find Hours, Location, and Contact info Reserve study rooms and computers Quick searches Renew books, place holds, pay fines Transfer information (citations, ect) to other devices. Read news and blogs Social Networking, music and video …

22. What Mobile Patrons want to do “Often mobile users seek information that is particularly relevant in a mobile context, such as directions or hours. Others seek information that is relevant in the moment … finding information on mobile devices is like snorkeling, where ‘shallow dipping in and dipping out of content’ … is desired” (CDL)

23. What Mobile Patrons don’t want to do Academic research or reading Log in to Campus Wifi, Proxy Servers, or VPN Study Collection Development Polices or Library Mission Statements

24. What Mobile Patrons don’t want to do “Most interviewees …see research as a difficult activity that would only be more difficult on a mobile device.” (CDL) “Only 1% of mobile EBSCO users actually viewed the full text (as opposed to 77% who typically view full-text on a regular device)” (CDL)

25. Mobile Library Sites

26. Mobile WebPacs AirPac Boopsie Library Anywhere MobileCat Others ( Xerxes, Discovery Systems)

27. AirPac Home

28. AirPac Search

29. AirPac Record Display

30. AirPac Patron Features

31. AirPac Other Views

32. AirPac Pros/Cons Pros Relatively easy to set up On the III server with direct access to bib and patron database Two web versions – with native app on the way Potentially, a full solution to for a mobile library site Cons Extra cost -- not included with webpac subscription Library has limited ability to control look and feel No easy way to save and export records Can’t pay fines No author searching

33. Boopsie Home

34. Boopsie Search/Record

35. Boopsie Account

36. Boopsie Other Features

37. Comments from the App Store “Very easy to use. Much better than their website. My account log in is very simple. Events, phone number and locations are all accessible on one page. No need to look all over the dang place like on their website.” “This app might be easier than the website.”

38. Boopsie Pros/Cons Pros Only vendor supplied Native App for several mobile OS Good usability Library has a lot of control over the content Auto-complete feature for catalog searching Relatively easy for library staff to implement Cons No Web App Some cost and some set up time for library staff No access to electronic resources –856 links No author searching, relevance ranking ? No way to export records

39. Library AnyWhere

40. Library Anywhere Search/Record

41. Library Anywhere Patron

42. Library Anywhere admin

43. Library AnyWhere Prices Schools: $150 + $50 per additional location Public Libraries: $350 for main facility + $50 per branch Two and four-year colleges: $750 + $150 per additional building Universities: $1,000 + $150 per additional building

44. Library AnyWhere Pros/Cons Cons Slow searching (screen-scraping) and page loads Bland look and feel of home page Interesting Iphone App (pro or con?) Some Cost Pros Very easy to get set up – relatively easy to edit and customize Inexpensive Two web versions Author searching Saved records feature LibraryThing for Libraries feaatures (if you have LTFL)

45. MobileCat

46. MobileCat Search

47. MobileCat Save and Export

48. MobileCat How To

49. MobileCat Pros/Cons Pros Open Source – no upfront costs Library has full control over interface Basic look and feel is simple and direct Easy options for saving and exporting Provides direct access to Electronic Resources Cons Somewhat slow searching Tech skills required for set up (PHP sysadmin for basic set up; PHP coding for more extensive customization)

50. Other Options?

51. References Mobile Design and Development (2009) Brian Fling The Anywhere Library: Primer for the Mobile Web (2010) Courtney Greene, Missy Roser, and Elizabeth Ruane Mobile Technology and Libraries (2010) Jason Griffey

52. Copyright John Wenzler, 2010 This work is the intellectual property of the author. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials.