Problem with capabilities guideline (5.1.2)

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/.

--------------------------------------------------------
Andy West
University Libraries ... A destination for research, learning, and friends
Microcomputer/Systems/Network Analyst   v: 765 285-8032
Ball State University                   f: 765 285-1096
Muncie, IN 47306                        e: mawest2@bsu.edu 

The University Libraries provide services that
support student pursuits for academic success
and faculty endeavors for knowledge creation
and classroom instruction.

http://www.bsu.edu/library (Web Site)

Received on Monday, 24 April 2006 15:06:40 UTC