We’re in the penultimate week of #23Mobilethings. It’s gone much quicker than I thought it might, and I’ve discovered lots of new things along the way. This is my final post, and Sally has asked me about vendor apps to access library content.
As a library customer, I use a range vendor apps depending on which library system I am using to access content (yes I do have multiple library cards!). Some apps are great, seamlessly allowing me to access content without endless clicking & navigating. Others are … well … downright frustrating & I only persevere if I *really* need the content. It’s almost as though no-one ever actually tested the app before they released it to the market!
So I turned my thinking to what kind of testing we, as libraries, do when considering vendor apps. How much time & energy do we actually dedicate to breaking, testing, tweaking, evaluating a so-called “fabulous new spangly app” from our vendors? And how many of us actually ask our customers to test & rate these apps? Not many, if any, is my gut reaction, but I would love to be proven wrong on that front. Getting testing done is hard enough in-house, let alone with non-employees. I know, it’s hard.
Could we develop better partnerships with vendors to make things better? Could we ask our customers to suggest which content they would like to see apps, or improved apps, for and work with our vendors to make that happen? I’d certainly like to try.
So to wrap up our #23MobileThings conversation, I am going to ask Sally to tell me a story.