Library in your pocket
Download as PPTX, PDF1 like843 views
The document outlines Chad Haefele's presentation on developing successful mobile library services. It discusses analyzing the modern mobile landscape, designing a mobile presence through various building blocks, and hands-on development of a mobile site. The presentation covers surveying users, choosing a platform of app vs. web app, frameworks, integrating data sources, custom code, catalog options, promotion strategies, and evaluation. It provides examples from the UNC mobile site and discusses future trends like HTML5 features and geolocation.
Library in your pocket
- 1. Library in Your Pocket: Strategies for Developing Successful Mobile ServicesChad HaefeleEmerging Technologies LibrarianUNC Chapel Hillchad.haefele@gmail.com
- 2. What I’ll be showing youAn overview of the modern mobile/smartphone landscapeA tour through our development processThe building blocks you’ll need to do it yourself, and the decisions you’ll need to make along the wayA mobile site generator, with playtime!
- 3. Schedule1:00 – Welcome and introductions1:15 – Overview and class survey1:30 – The modern mobile landscape2:15 – Designing a mobile library presence3:00 – Break & chat3:15 – Building a mobile library presence3:45 – Hands-on mobile site development4:45 - Final wrapup & questions
- 5. Why now?
- 8. Even Better
- 12. iPhone 4
- 13. iOS devicesiPhone, iPad, iPod TouchAvailable only through AT&TDebuted in 2007Apps developed in Objective CMore than 250,000 apps
- 16. Android devicesToo many to listAvailable on all major carriersDebuted in 2008Apps developed in JavaMore than 80,000 apps
- 18. BlackBerry Torch
- 20. Blackberry devicesToo many to listAvailable on all major carriersDebuted in 1996 (sort of)More modern devices: 2005About 10000 apps
- 21. Which platform to support?Mobile web use(August 2010)Market share – devices sold(July 2010)Anon. 2010. August 2010 Mobile OS Share. Quantcast Blog. September 3. http://blog.quantcast.com/quantcast/2010/09/august-2010-mobile-os-share.html.Anon. 2010. comScore Reports July 2010 U.S. Mobile Subscriber Market Share -- RESTON, Va., Sept. 15 /PRNewswire/ --. http://www.prnewswire.com/news-releases/comscore-reports-july-2010-us-mobile-subscriber-market-share-102969094.html.
- 22. Source: http://blog.quantcast.com/quantcast/2010/09/august-2010-mobile-os-share.html
- 25. Other usage statsSource: http://comscore.com/Press_Events/Press_Releases/2010/12/comScore_Reports_October_2010_U.S._Mobile_Subscriber_Market_Share
- 26. Other usage statsSource: http://blog.nielsen.com/nielsenwire/online_mobile/u-s-teen-mobile-report-calling-yesterday-texting-today-using-apps-tomorrow/
- 28. VS
- 29. ?
- 30. UNC Mobile site walkthroughwww.lib.unc.edu/mwww.lib.unc.edu/m/plain+ ‘View full site link’
- 31. UNC Mobile site walkthrough
- 32. Catalog
- 33. UNC Mobile site walkthrough
- 34. UNC Mobile site walkthrough
- 36. Block #1: Survey your usersPlus 44 ‘other’ responsesData from Spring, 2009
- 37. Sample ‘Other’ responses:Cell phoneCheap free phoneBraille NoteCarrier pigeonLame old phone :(My cheap phone that always has at least 2 bars
- 39. Platform: App or Webapp?AppWebappJava, Objective CSingle platformFull hardware access(GPS, camera, etc)Can be used offlineTricky to get statsHTML, CSS, JavascriptMulti-platform (maybe)Limited hardware access (GPS only)Requires web connectionStandard webstats
- 40. Webapps play well with others
- 42. Other app development optionsPhonegapFlashSencha TouchAppceleratorOthers: http://en.wikipedia.org/wiki/Multiple_phone_web_based_application_framework
- 43. Block #3: FrameworkJason Clark’s: http://diginit.wordpress.com/2009/11/13/mobile-web-design-working-code-tips-best-practices/orhttp://bit.ly/cXlnlSwww.lib.utc.edu/m
- 44. Block #3: FrameworkiUI: code.google.com/p/iui/Mobile site generator:www.hiddenpeanuts.com/msgwww.lib.unc.edu/m
- 49. Block #4: Data sources & Outside systemsRSS feedsXMLOther systemsComputer availabilityeResourcesHoursIM / text a librarian services
- 50. Block #5: Custom code
- 53. Block #6: CatalogCatalog optionsDo it yourselfILS vendor-provided solution3rd party product
- 54. Catalog: DIYPriority 1: Get a clean data feedXML feeds from ILSYaz / Z39.50 (http://www.indexdata.com/yaz)Other solution – tap into DB directly somehowHarass your vendors!
- 55. Catalog: DIY (at UNC)Endeca makes it all possibleXML + php + Syndetics + iUI
- 56. Catalog: ILS solutionsAirpac, from Innovative
- 57. Catalog: 3rd party productLibrary Anywhere“Works with 90% of current OPACs.”http://www.librarything.com/LibraryAnywhereLinks:http://www.librarything.com/blogs/thingology/2010/10/library-anywhere-is-live-2/http://www.librarything.com/blogs/thingology/2010/01/library-anywhere-prices-public/
- 59. Rough stats: Hits, 2010Block #8: Evaluate & Iterate
- 60. Rough stats: Catalog info, 2010Block #8: Evaluate & Iterate
- 61. Blocks (review)SurveyPlatformFrameworkData sourcesCustom codeCatalogPromotionEvaluate & Iterate
- 62. HTML5 & more on the horizonAccess to camera, GPS, mic, accelerometer, play videoYoutube: m.youtube.com Flickr: m.flickr.com Google Reader: google.com/reader/i Geolocation: hiddenpeanuts.com/ala
- 63. This is not the endSlides online: http://www.slideshare.net/cHaefele
Editor's Notes
- #4: Rough guide, flexible
- #5: http://bit.ly/mobileclasspoll http://www.polleverywhere.com/multiple_choice_polls/MTE2Njc2MzE3MA
- #6: -3 major standards right now-Just in the last 3 years
- #7: -My first mobile browser – RAZR-bus stop schedule, but that’s it-WAP, etc.
- #8: -Android & iPhone (mobile Safari) browsers-Actually usable!-Regular sites on mobile browsers-Still not ideal
- #9: -Sites designed with mobile usability concerns in mind.-Large links, big fonts, simple, etc.
- #10: Smartphones to overtake regular featurephones in market penetration by late 2011
- #11: matter of UI/usability concerns more than anything else
- #12: -Explosion of options, full time job-So many minor tweaks-Slightly out of date – Droid 2, BB Torch, etc-Let’s look at the latest and greatest from iOS/Android/BB
- #13: -Released June ‘10-How many have this?
- #14: -iOS – name change – like Windows, OSX, etc-Smooth user experience is key-Prime concern: function. Advanced functionality too tricky to implement? Don’t do it.-250k apps (9/10)– what does that really mean? Vibrancy & health-Games
- #15: -Evernote-Gowalla-Pandora-U-Verse DVR control-Stanza-Dropbox-Foursquare-iLevel
- #16: Android-Evo: Sprint-Droid X: Verizon-Not just one device, no single “Android phone”-Verizon’s Droid line of phones - branding-50+, this collage is already old
- #17: -Android is an OS, not a phone-Open source OS,tweakable-fragmentation issues?
- #18: NY TimesFacebookDesktop – customizability/widgetsRdioCardiotrainerListenDropbox – some apps are on multiple platformsGoogle Maps – tight integration of Google servicesQuality improved lately, but chicken or egg?
- #19: -I know least about these-Firsthand experience is key-Newest BB attempt to compete with Android & iPhone-RIM, always been messaging-centric-Legacy of pagers/e-mail/etc.
- #20: -I don’t have one to play with, but here’s examples from website-Pandora-Facebook (who doesn’t have Facebook?)-NYT-Of course, Oregon Trail
- #22: -This is what it looked like when we started developing, different now-US stats only-Other= Palm, Windows, etc.
- #23: -Over time-iOS decreasing, but out of a larger number overall – still good-This is web. Apps are trickier to measure – what’s a pageview?This is really small overall – a few percent of all web traffic in U.S. – but easy to do!
- #24: These all differ slightly based on the surveyer
- #25: Blah blahblah, more stats. Different yet again. Useful for general trends only.
- #27: Mobile internet use is rising among teens – our future users!My anecdotal noticed difference btwn grad & undergrad students
- #29: -Main conflict to watchRIM yet to produce a truly viable competitorUsabilityInstall baseOpenness / tweakability (widgets, etc)App store guidelines-Best strategy incorporates both (& more?)Women slightly prefer iOS, Men prefer Android – ad influence?
- #30: Move on at 2:15Next:Designing a mobile library presence
- #31: Viewing design through a case study of the site we builtWebapp, works like this on iPhone, iPod touch, Android, some BlackBerries, Palm Pre, iPad (but…)Our design philosophy: nobody wants to do in-depth research via mobile-Resources to answer quick questions
- #32: <ahref="sms:1-919-442-8ASK">Text us: 919-442-8ASK</a><a href="tel:919-966-9444">919-966-9444</a>
- #33: Requested by usersInteractive, answers questions
- #36: How do you build this stuff?But first, any questions?
- #37: Do this survey informally – raise hands
- #39: App – installed program‘webapp’ – really just a webpage optimized for mobile use. Trendy term.
- #40: App: definite coolness factor, distribution via app storeiOS: $99 fee/year
- #41: As I just said,webapp can’t access hardware. But it can play nicely with apps that can, in some cases.Show video, barcode scanning exampleNot perfect, requires explanation, streamlining in the future
- #42: If you do want to go app… play with this firstTwo components – interface designer & ‘Blocks’Demo live: http://appinventor.googlelabs.com-Beta, invite only. -Limitations – no app store, etc.
- #43: App, not webappBut… we went webapp. I can’t code in Objective C, also cross-platform issuesWebapp can be purely by hand, or use framework to save work
- #44: Jason Clark: Head of Digital Access and Web Services at Montana State University Libraries-Grew out of his experimentationUTC: University of Tennessee Chattanooga, Jason Griffey
- #45: Designed to mimic iOS look & feel.-roots from original lack of apps-Open Source, active development communityView our site as live example
- #46: iUI is very simple code. So simple, can be automated!More on this later, with practical dev time
- #47: Live demoTest a framework early, test often through development
- #49: iUI’s simple HTMLcode means with a bit extra work, we got this tooNow you’ve got a framework. Just choosing at this point, no coding yet
- #50: Now, see what else you can pull in. Build an inventory.RSS: show our news feedXML: our catalogHours: just recentlyIM: Libraryh3lpeResources: not heavy usage, but why not if it’s easy?
- #51: Framework chosen, inventory built, put it together!
- #52: DCPL – first (?) lib iPhone app
- #54: -Optional, but recommended if at all possible-Adds interactivity, utility-Use case: looking up a call number / do you have X. Again, not deep research.
- #55: Other solution – like NCSU
- #57: http://m.ocls.info/
- #58: Try to demo ‘find libraries near me’, if not then go to the NY view then Hofstra – is it in test mode? ask if anybody has insight-Provides both mobile web catalog & mobile app catalog-Prices: http://www.librarything.com/blogs/thingology/2010/01/library-anywhere-prices-public/
- #59: Auto-forward vs. device-sensing link
- #60: Not giant numbers compared to site as a whole – maybe 1%-promotional value is immeasurable-loyal usersTheory re: dropoff in summer – only students have iphones? Staff have android/blackberries and stick around?At first, Android was virtually zero
- #61: The process is never done. Constantly tweaking, trying new things, updating to match tech
- #63: Youtube’s frustrations w/ built-in iPhone appOverall, greater interactivityhttp://www.hiddenpeanuts.com/ala/demo2.php