This document:Public document·View comments·Disposition of Comments·
Nearby:Mobile Web Best Practices Working Group Other specs in this tool Mobile Web Best Practices Working Group's Issue tracker
Quick access to LC-442 LC-443 LC-444 LC-445 LC-446 LC-447 LC-448 LC-449 LC-450 LC-451 LC-452 LC-453 LC-454 LC-455 LC-456
Previous: LC-455 Next: LC-442
I have read the current draft of the Best Practices document. Overall it is a good summation of all the guidelines (esp. OpenWave) I have been using under the Mobile Development Project at Ball State University Libraries. While I have a few minor problems with the guidelines (GIF really ought to be put on pension since most mobile Web browsers can handle PNG), I take issue with the capabilities guideline (5.1.2): "Do not take a least common denominator approach." As the mobile developer, my primary concern is to make library information and services available to the largest number of mobile users. I started with no knowledge of mobile devices; with a clunky development environment (IIS/Visual Studio/FrontPage); and with a vague idea of what devices were in use on campus. (Several attempts at an online survey of mobile devices fell flat.) Nonetheless I have created a mobile Web site for the University Libraries, that looks and works perfectly well using a strategy that the Best Practices document has labelled "least common denominator". Perhaps you can add a "How To Do It" section under the capabilities guideline, or at least explain why following a LCD approach could result in a lesser experience for mobile users. The University Libraries mobile Web site is http://www.bsu.edu/libraries/mobile/.