Download Providing Mobile Web Library Services - NCSU Libraries

The Education Institute
Providing Mobile Web Library Services
NCSU Libraries
David Woodbury, NCSU Libraries Fellow
Jason Casden, Digital Technologies Development Librarian
1
David Woodbury
Project Planning and Design
2
Why invest in mobile development?
5 billion
reasons
3
“People expect to be able to work, learn, and
study whenever and wherever they want to.”
4
Our motivation
5
About NC State University Libraries
• We serve the largest higher education institution
in the state
– 31,000 students & 8,000 faculty members
– Large focus on science, technology, engineering &
mathematics
• History of innovation & collaboration
– Endeca discovery layer on our catalog
– Early mobile library site (MobiLIB)
6
Our mobile services
7
NCSU Mobile Web (Campus Site)
8
NCSU Libraries Mobile Team
• Jason Casden, Digital Technologies Development Librarian
– Developer
• David Woodbury, NCSU Libraries Fellow
– Project manager
• Markus Wust, Digital Collections and Preservation Librarian
– Developer & co-creator of MobiLIB
9
Project timeline
Three months from planning to launch
• Project planning, site
wireframes in September (one
project manager)
• Development and testing in
October (two developers)
• Formal launch & promotion in
November
• Main website redirect in
December
10
Project timeline
Iterative development since launch
• Enhancements added by other
developers
• Bug fixes as needed for new
devices
new
new
new
11
Our mobile services
•
•
•
•
•
•
•
•
•
Locations & Hours
Computer Availability
Book & Article Search
Room Reservations
GroupFinder message board
Reference Services
News & Events
Webcam Feeds
Link to campus mobile site http://m.lib.ncsu.edu
1
Locations & Hours
13
Computer Availability
14
Catalog Search
15
Catalog Search
16
Reference Services
17
GroupFinder (message service)
18
What to mobilize?
• What services are currently available?
• What services are applicable on a mobile
device?
• What services translate well to the mobile
environment?
• What tools can be created easily?
• What would be fun to see?
19
Don’t mobilize everything
• Nearly 100 links!
• Always can link back
to home page, if needed
20
“Mobile” is not just shrinking the page
21
Use only essential, relevant content
22
Use only essential, relevant content
23
Reduce options, simplify
24
Limit data to mobile context
25
25
Limit data to mobile context
• For time oriented
data, we assume
current day & time
• We assume action
oriented
26
Use the mobile interface
27
Provide appropriate tools for the
user’s context
28
Expose hidden, useful content
29
Jason Casden
Technical Planning and Implementation
30
31
When to Make a Native App
• Charging for it
• Creating a game
• Using specific
locations*
• Using cameras
• Using accelerometers
• Accessing the
filesystems
• Offline users
* Actually available to web-based applications
32
The Case for Mobile Web Apps
“I believe that unless your application meets one
of these native application criteria, you should
not create a native application, but should
instead focus on building a mobile web
application.”
— Brian Fling, “Mobile Design and Development”
33
WolfWalk
•
•
•
•
Native iPhone App
Geolocated special collections images
Track the user’s current location
Browse historical images of sites on campus
34
Shoutouts
• The project team
– Tito Sierra, Jason Casden, Steven Morris, Markus
Wust, Brian Dietz, Todd Kosmerick, Joseph Ryan
35
WolfWalk, Two Ways
36
37
38
Distribution Channels
• Open vs. Controlled
– Administrative overhead
– Bottlenecks
– Technical restrictions
39
Our tools
• Mobile website
– XHTML 1.0 transitional
– CSS
– non-essential JavaScript and AJAX
• MIT Mobile Web Open Source Project
• Leaned on pre-existing web services
• Targeted higher-end devices
40
No developers?
• Tools that require only HTML knowledge
– WordPress, iWebKit, iUI, jQTouch, Dashcode…
– Good for static content
– May lack good multi-tiered device support
41
No developers?
• Vendors
–
–
–
–
–
Boopsie, Terribly Clever…
Can manage mobile development process for you
You may lack control over the final product
May be expensive
Doesn’t develop internal expertise
42
Data Reuse
•
•
•
•
CatalogWS
Library Hours
Study Room Reservations
GroupFinder
43
Best practices
• Standards and official guidelines
– Useful, but slow-moving
– Don’t get stuck
44
Lots of Devices
Top Level
iPhones, Android
phones, Palm Pre
Large touch
screens,
sophisticated web
capabilities
Middle Level
Blackberry, Nokia
smartphones,
Windows mobile,
etc.
May lack touch
screen and some
CSS and
JavaScript
capabilities.
Low Level
Web-enabled flip
phones
Small screens, low
web functionality
45
Content Adaptation
46
Separating data from presentation
47
Testing
CC BY-SA 2.0:
http://www.flickr.com/photos/wfryer/392918
9482/
48
Recommendations
49
Be Agile
•
•
•
•
Rapid development cycle
Think iteratively
Adjust to change quickly
Avoid paralysis
50
Play
51
Collaborate
• Campus efforts
• External projects
• Steal what you like
– Improve it, so it can be stolen back
52
In Summary…
• Mobile websites are becoming very
sophisticated
• Mobile web app development is web
development
– just a little different
53
David Woodbury
Assessment
54
Assessing the site
55
What’s popular at NCSU Libraries
Pageviews by service
56
What’s popular at NCSU Libraries
Views by device
57
Further assessment
• Assess actual student needs
– Survey students
– Study behaviors
• Invest in services that can be used in a variety
of contexts
• Get input from across library staff
58
Coming Soon!
• Patron account information (checkouts &
renewals)
• Access to electronic reserves for classes
• Building wayfinding
• Tools for staff
59
Questions?
60