Mobile Devices: the Experience why? maturing market for devices standardised OS'
and more importantly
webkit browser Student desire driven quick access to useful info on the move
not replicating everything
task driven Greater number of Open Source solutions available to try for free Molly Project Joint Oxford Venture
Python & Django powered
Difficult to set up
UI basic MIT Mobile Web 'Original' Mobile app
Code been dumped
very MIT specific
No community input
UI looking old Kurogo Developed by original team behind MIT
LAMP PHP/CSS based
Simple framework for dealing with look/feel of site rather than bundling apps into a framework
Greater flexibility in creating bespoke apps UCLA Mobile Web webOSP used MIT as basis for developing framework
Code been standardised and improved plus new UI for webkit browsers
Graceful UI degradation based on phones abilities App or Web App? App Excellent/Fast UI Experience Offline Storage Direct access to more hardware Web App Long Life Non-device specific: targets many simultaneously Less development time No external costs mStir demo time! future developments? problems? Closed Systems library catalogue z39.50 limited renew books? My library record? Webct/Learn 9 limited access keep up to date for new phones resources Dream Library App? Full Library Catalouge access to e-books and journals directly, regardless of device my library record reserve books pay fines near field/RFID automatically take out books by swiping phone against it find books by running phone along shelf until phone beeps Internal GPS click on classmark in catalogue to be shown
exactly what shelf/floor the book is on and where you currently are plus a route to the book augmented reality use phone camera to visually locate book Discussion points Has your institution investigated apps?
Have you invested in airpac?
Ombiel CampusM integration with Millenium?
Do your students even want apps?
Cost vs payoff?
Your dream app?
What about Tablets? Students still want a
proper 'app' not a web appSee the full transcript