Speaker – Jeff Wisniewski, Web Services Librarian, University of Pittsburgh
Notes from this session …
mobile will surpass desktop web access in the next couple years
if you can write html, css, and javascripting … you can write for the mobile web.
me – mobile apps are great …. but we even moreso need to be building for the mobile web.
context is important:
- not interested in your lending policy
- want to satisfy immediate info needs
- usually we’re in busy places, doing multiple things when we are accessing mobile web
Mobile usability – oxymoron (not sure I agree …)
- minimize the need to input text when you can.
remember you’re designing fro a small screen and will have speed and latency issues.
Two important points to remember:
- don’t make me think!
- don’t make me type!
content – ask your users what they would find useful
Cake and icing:
cake – directions, hours, contact info, ask a question, etc.
icing – (do these if you can, later on, etc) – catalog search, article search…
be selective – everything is on a need to know basis
repurpose existing content – podcasts, video, alerts, rss type stuff
content we buy:
some have mobile friendly sites already, like EBSCO, PubMed, westlaw, etc.
Catalog: look for accessible version if possible – it will probably be mobile friendly
me – mobile – make sure our site and services work on a 3g network – m.tscpl.org
m.home – make a new mobile homepage:
single column
single lines
flattened hierarchy
short titles
simple standard html and css
include a mobile dtd type
ignore handheld css stylesheets. most new mobile browsers ignore handheld stylesheet statement
media query – the link media thing – tells browser to use this stylesheet if screen is smaller than a certain size
include action links like a href tel:phone# stuff – sms: – same thing – this allows people to click and call or click and text, rather than having to type
optimizing for mobile:
combine dependent files, minify your javascript and css, tell google – register mobile site with them.
Google small business center – register library website with google local
use validation services
drupal has a mobile template
usability testing – do paper tests
analytics – google analytics has mobile tracking, or you can filter by user agents
Tagged as:
cil2010,
mobile,
mobile design,
mobile web,
websites
Inviting Comments
by David Lee King on December 17, 2009
Sometimes, a blog post or article on a library website doesn’t get any comments. And that’s fine – not every post is comment-worthy, right? But there are ways to prompt, or “invite” visitors to comment … even by using the website’s built-in comment functionality. Let me show you what I mean.
Here are two examples – the first from my library’s website, and the second one from Atchison Public Library. Both of these examples are screenshots taken from the main page of both websites – each a teaser for an article.
Mine first (screenshot below):
We let the comment functionality simply announce that no one has left a comment on this post (and darn it – it’s MY post!). We do that via the text “0 Comments.” This works fine – it’s what that functionality is supposed to do.
But check this out – here’s what Atchison Public Library does (screenshot below):
See the difference? Atchison uses their lack of comments to … invite people to comment. They do this by prompting their website visitors to “be the first to comment.”
I know – it’s one of those little detail-y things. But it’s that type of detail, that focus on inviting patrons to participate, that just might prompt them … to participate. It might just convert that lurker into a more active participant.
Nothing wrong with that – good job, Atchison!
Tagged as: comments, conversion, digital experience, invitation, participation, website design, websites
1 comment