These are the slides used for my presentation on library mobile websites for NJLA 2010. These slides will also be the basis for a similar presentation to be done, as a webinar, in June sponsored by CJRLC, HRLC, and infolinik
19. I would have skipped my own wedding for this.. Love that Doug Baldwin #NJLAconf @govchristie
20.
21.
Hinweis der Redaktion
Ask the audience and then have 2-3 of them tell you what devices they are using Point out that different people are using different devices (if they are) Ask the audience if anyone is tweeting this presentation? If so, use next slide (if not move on)
Have fun with this one!
Go through the outline and specifically highlight with some detail “What are my options” Considering you current site Tools for creating a separate mobile site
Highlight the fact that the largest demographic with increased usage is teens and seniors (point 3)
Stats tell us that: The rise in the use of mobile devices is exponential, not incremental Mobile phone users are using these devices to seek information, and they consider it an important way of obtaining information online.
Visitors who are looking on your current website for content, if not optimized, which have a much harder time finding information (and even harder if they are not using a smartphone) – Most mobile devices will load the website and the user will be given the top left hand corner. When a mobile user has to resize to get a wider look at the entire page, the content is rendered smaller and smaller so that much of the content on the page may not be visible to them Websites are for the most part designed to be viewed on standard computers monitors, and for laptop/desktop machines with more sophisticated browsers. However, as we have seen with the statistics, the hardware being used to view and access the web is changing. We need to account for this when providing web based content. It is important to our users that we provide an easy to navigate, easy to access user experience for our web based content which is mostly provided via our websites. More and more, we are providing access to our materials, programs, and various resources through our website as a portal of information. Just as we strive to make our physical content easier to find, and our physical spaces easier to navigate, we must do the same for our web content. We need to provide a better experience to those users accessing content via a mobile device, they are our future.
Instant Mobilizer Gives you a preview of your website in a mobile environment Mobiready Tests your current website for mobile usability and gives you a grade as well as a detailed report on the aspects of the page and how they stack up for mobile readiness. There is also a link that offers suggestions on how to fix mobile issues it detects If you current site is mobile friendly and does render well on mobile devices than that is great!!! You are in the minority though. For the rest of us, once we are introduced to the sad truth about our present website, its time to thing about what we can do to fix this (Hint: it is not as hard as you think!). You do have choices!!
Choice 1 # Take steps to make your current website mobile friendly This can be as much or as little as you want to do, the more the better, but some if better than nothing at all Conditional style sheet : A stylesheet is a file that is used by your website, or webpages, to determine things like font color, size, rations for content, etc. It instructs the browser how to display the content on your site. You can have two style sheets: one for the regular browser user, and one for the mobile user. The way this works is that when someone is on a desktop browser, the site loads the regular style sheet. When on a mobile device, the browser for the mobile device is instructed to use the mobile style sheet instead. However, creating a mobile style sheet requires a fair amount of knowledge of CSS commands and styles. Also, I have heard mixed reviews on the conditional style sheet in that some mobile devices will read it and some will ignore it.
Prioritize content Mobile websites should and cannot be smaller versions of your current website in regards to depth of content. Users of mobile devices are looking for quick and precise information. Also, a lot of the content that relies on scripting, Flash, etc will not load for certain devices. When it comes to mobile websites, the more content you have, generally, the harder it is to find because there is more drilling involved. So we need to make the tough choices Think about the situations when people would be accessing the library website on a mobile device; what are they looking for, what is their user behavior? We’ll talk a bit more about some mobile services later on. 2.Deciding on a platform and hosting Vendor hosted Pro: Familiar graphical interface for easy editing and adding of content Con: If vendor closes shop, and they do not have an export feature, you lose the site Self hosted Pro: You have the code for the site so, vendor viability is not an issue Pro: You have more control over URL or subdomain name Con: Have to use an HTML editor and will need to know, or have access to someone who knows, some HTML and CSS to be able to continue to add content and/or edit the site Who is going to manage, change and edit the content for the site? Again, step number one comes into play where you don’t want to make much more extra work for staff or yourself. Think about populating the mobile site with content that is less likely to change. Provide mobile content that can be pushed to the site (more on this later). To reiterate we are not trying to duplicate your present site. We are trying to provide useful, relevant, and prioritized content to users on the go.
Mippin (cranburypl@gmail.com ; cplstaff) Insert your URL and get a mobile version of your site with a URL (you can use TinyURL to mash that URL into one that is more conducive to your current site) With free account, can gain access to some limited customization features like header colors, header logo Google Mobile Optimizer Renders you site, in a regular browser, in a mobile format so you can preview what you site looks like to mobile users. You can actually also capture the URL, setup a custom bit.ly or tinyurl, and use that for your mobile website (for free and without having to build anything!)
Twitter (http://mobile.twitter.com) Facebook (http://m.facebook.com) Ebscohost Mobile (http://tinyurl.com/ebmobile) Moodle (http://moblemoodle.org) Flickr (http://m.flickr.com) RSS (provide the links to the feeds) Podcasts/Vodcasts (http://cranburypubliclibrary.podbean.com) Blogs YouTube (http://www.youtube.com) Delicious (http://m.delicious.com/) Google Books (http://books.google.com/googlebooks/mobile) Mobile OPAC Libraries Anywhere (Librarything) – still in closed beta ($$) - http:// www.librarything.com/LibraryAnywhere WorldCat Mobile iPhone app Innovative Interfaces (Airpac) There need to be more.. And we need to let our vendors know!! AOL Hack for Free Text Reference – Create a free AOL account; Login to AIM; patrons send text msg of “Send username message” to 246246; You receive msg in AIM chat and converse via text with patron. Provide instructions on mobile site. Use with regular site too!! ( Maybe demo if you can )