LIR/AGI Mobile Technologies SymposiumRonán Kennedy, NUI Galway
Introduction Web access from mobile devices will exceed desktop access by 2015 [source] React or Prepare?
Introduction • Prepare a strategy • analyse the demand • access to resources • access to catalogue • access to Library services – room bookings, etc. • Seamless mobile access through • - responsive web design • - apps – native or hybrid?
4.2% of site usage is mobile – at least School Institute Name to go here
October 2012 • Catalogue Searches: 655,000 • 4.2% - 27,500 on mobile
Didn’t turn out that way “Plans are only good intentions unless they immediately degenerate into hard work” Peter Drucker
Native App Difficulties – for dedicated users only • Massive OS discrepancies – heavy Apple weighting • On campus access only • App only allows searching, not access (to avoid authentication issues) • Institutional email must be accessible from device • Time-limited tokens • Personal profile on site needed • Legibility issues – in design and fulltext • User would need to know the resource and its content very well • Publishers don’t make money on these – future implications
Native Apps Discovery NOT Delivery Open University Project: most users don’t want to read fulltext on their devices [source]
The Vendors’ View “We’re not going to bother with apps, we’re going concentrate on mobile site accessibility. They’re quick, they’re clean and your users don’t need to do anything different”
3. Access To Catalogue - Mobile Catalogue Well embedded ‘desktop version’
4. Access to Library Services • App or Mobile Web? • Functionality Required (Hardware needed? Offline access needed?) • Planned user interaction and activity • User preference and devices • Resources – money and time • Technical Knowledge (different programming languages for different types of app) • Timescale • [source]
Mobile Web App • Uses open web technology: HTML5, CSS, Java • Deployed through the web, hosted locally • No need to worry about many SDKs • Embraces all OSs
Thanks for listening! firstname.lastname@example.org