Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

“Mobile Choices” and Library Anywhere (CILIP)


Published on

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

“Mobile Choices” and Library Anywhere (CILIP)

  1. 1. “Mobile Choices” andLibrary AnywhereTim SpaldingFounder, LibraryThing
  2. 2. Goals• Explore the key “mobile decisions”• Show Library Anywhere ( )
  3. 3. What is LibraryThing?• Personal cataloging• Social network for book lovers• 1.6 million members
  4. 4. What is LibraryThing for Libraries?• A way to enhance your existing catalog
  5. 5. What is Library Anywhere?• A mobile version of your catalog – Available for most OPACs • New: Axiell • Talis: Looking for a first library – Available on web and native apps. – Works just like your catalog – Cheap Quick demo
  6. 6. Tims Principles of Library Technology• Don’t go mad – QR codes• Develop if you can• Buy as if you could develop• Favor off-the-shelf solutions• Favor open source However…
  7. 7. But… Mobile is Hard• Apps are hard• Mobile web isn’t easy• Multiple devices, fragmentation• Hoops• Open Source is limited
  8. 8. Key Mobile Decisions• Native app or mobile web• Branded to you or shared/common• Duplicate back-end system or use existing
  9. 9. Native App or Mobile Web: Upsides of a Native App• Sexy• Spot in the app stores• Take advantage of device features (eg., scanning, offline storage)• Can be faster
  10. 10. Native App or Mobile Web: Downsides of a Native App• The ”bad old day" way of doing software• Multiple devices, fragmented devices• Approval and re-approval• Expensive!
  11. 11. Native App or Mobile HTML: Upsides of Mobile Web• No need to download app.• Less buggy• MUCH cheaper to build• MUCH cheaper to maintain Which approach did we take?
  12. 12. The Hybrid Approach• Core is mobile web, with optional app shell• Works from the web• Develops like the web, mostly• Available in app stores• Native features available in native apps.
  13. 13. Branded to You or Shared/Common?• Your app vs. a shared solution – Branding – Customization – Extra development effort – Possible network effects Again, we do both!
  14. 14. Branded to You or Common?
  15. 15. Duplicate Back-end System or Use Existing?• The duplicate approach – Strengths – Weaknesses• Use existing – APIs – “Screen scraping”
  16. 16. Enter “The Matrix”
  17. 17. What this means…• Abstraction avoids the perils of “screen scraping”• Abstraction is powerful – Two examples…
  18. 18. And• A quick overview…
  19. 19. Thank you.Tim QuickTimeª and a@LibraryThingTim decompressor are needed to see this all afternoon.