
Mobile Computing:
Experiences and Issues
Brenda J. Gerth
Computing User Services
University of Victoria, Canada
bgerth@uvic.ca
Abstract: Internet enabled mobile devices used by educators to support instructional, research and administrative activities have the potential to provide access to critical information anywhere and at anytime. However, to avoid incompatibility or other ensuing issues, careful consideration must be afforded to workstation, mobile device and network specifications; the interoperability with other institutionally supported applications; and the adherence to existing university strategic alliances before educators with limited resources purchase personal digital assistant (PDA) devices and associated peripheral equipment. The focus of this paper details the experiences and technical issues encountered in supporting the use of handheld mobile devices by educators and administrators at the University of Victoria and identifies the features and specifications for consideration before purchasing a mobile device.
Introduction
Educators are embracing mobile computing technologies to manage their personal information manager (PIM) components typically consisting of a calendar, address book, notes and to-do list; create and access critical documents; download e-mail; connect to the Internet; and synchronize with institutionally supported server applications. Without clear direction and guidance, limited resources will be wasted on the purchase and support of unsuitable and incompatible mobile device solutions. This paper outlines the experiences, issues and problems with implementing and supporting handheld mobile devices at the University of Victoria, and identifies the strategies employed for avoiding and resolving such problems.
Workstation OS and Device OS Compatibility
An obvious but sometimes forgotten consideration when choosing a highly rated mobile device (particularly for Macintosh users) is to verify whether the device can be synchronized to the desired Windows or Macintosh workstation or is limited to the Windows platform. The device's operating system (OS) must be compatible with the workstation OS, and Macintosh users must be particularly careful to ensure the mobile device is supported by the version of Mac OS (8.6, 9.1, X or X version 10.2.x) installed on their workstation. Although Windows CE(Pocket PC) OS devices do not typically support Macintosh OS workstations, a number of Palm OS devices also do not, including (as of this writing) any of the popular and highly rated Sony CLIÉ™ mobile devices.
Cross-vendor Interoperability
A common requirement for University educators and administrators is to synchronize their calendar, address book, notes and to-do list with the institutionally supported calendar server. Synchronizing from the Windows platform is well supported, but continues to be a significant problem from the Macintosh platform. Obtaining updated Macintosh calendaring synchronization software supporting the updated versions of Macintosh OS, Palm Desktop and Palm OS software has been a major challenge. Currently, a production version of the calendaring synchronization software supporting Macintosh OS X, Palm Desktop 4 and Palm OS 4 for the Macintosh is unavailable, other than in Beta. A timeline for the release of the most recent version of Palm OS, Palm OS 5, is unknown.
An associated cross-vendor interoperability issue is the inability to synchronize all components of the mobile device's PIM with the University calendar server. Presently, the mobile device's Notes component will not synchronize with the calendaring e-mail connector conduit on the Windows desktop, and the address book will not synchronize with the Macintosh OS X conduit. The inability to synchronize all components of the PIM is problematic for users and support providers. It is unknown whether future versions of the calendaring synchronization software will support all components of the mobile device's PIM.
Data Loss
Losing data stored on the mobile device has been a reoccurring problem. If the battery in the mobile device loses its charge, any data or applications stored in the read only memory (ROM) is lost. It is important to back up the data on the mobile device using the backup feature available from the desktop synchronization software to avoid losing critical data. When traveling, back up the data to a secondary storage card and store the backup card separately from the mobile device in the unfortunate situation that the device is lost or stolen.
Network Connectivity
Wireless Local Area Network Issues
Many educators request connectivity between their mobile device and the wireless local area network (WLAN) to access institutionally supported e-mail, Internet and calendaring services. As with wired network solutions, a number of wireless standards exist such as Infrared, Wireless Fidelity (Wi-Fi) and Bluetooth. Wi-Fi is the IEEE 802.11b network standard currently deployed by the University, by many other educational institutions, and increasingly, is used for wireless connectivity in the home. Depending on the mobile device, the network interface card (NIC) may be built-in or inserted into the mobile device.
A myriad of 802.11b wireless local area network (LAN) cards are sold by vendors. Network interface cards are sold either in the form of the Personal Computer Memory Card International Association (PCMCIA) PC Card inserted into an expansion sleeve that can serve the dual purpose of also providing wireless network connectivity to a notebook computer, or in the form of a smaller CompactFlash Card that is about one third the size of the PC Card. Erroneous assumptions have been made assuming that the PC Card currently used for connecting a notebook computer to the wired or wireless LAN can be repurposed for connectivity with the mobile device. Before purchasing a LAN card, it is critical to verify that the PC Card driver required for supporting the specific mobile device on the required Macintosh or Windows desktop platform is available and that it is enabled with the wireless network standard implemented.
Wireless Wide Area Network Issues
One issue that could not easily be resolved was the purchase of a Smartphone device enabled with a wireless wide area network (WWAN) standard that is incompatible with, and unsupported by the University telecommunications carrier. Further complicating this issue is the binding strategic alliance agreement signed by the University and the external telecommunications carrier, preventing the educator from obtaining telecommunications services by the carrier of the unsupported wireless wide area network.
PDA, Handheld, Smartphone or Phone Edition?
Before purchasing a handheld mobile device, educators should familiarize themselves with the various types available to ensure the mobile device that best suits their needs is selected. There are a number of articles that detail and contrast device features and specifications and provide other useful information such as distinguishing the hype from reality (Brown, 2001) and traversing the Pocket PC "decision tree" (Hall, 2003). The ability to read the screen outdoors as well as indoors, upgrade the device OS and built-in applications by means of flashable read only memory and extend functionality by connecting an external keyboard, a wireless network card, or an additional storage card are a few of the important features that should not be overlooked. Other features to consider include device OS and desktop synchronization support, screen resolution, colour depth, memory configuration and expansion options (Tab. 1).
| Type | Pocket-sized PDA | Large-sized Handheld | Phone Edition | Smarthphone |
| Processor CPU | StrongARM 200 MHz | XScale 300/400 MHz | 33MHz Motorola DragonBall |
| RAM Memory | 2 MB, 6 MB, 8 MB, 16 MB, 32 MB, 64 MB |
| ROM Memory | Flashable or Non-Flashable | 16MB, 24MB, 32MB, 4MB, 64 MB |
| Device OS | Windows CE Pocket PC 2000, 2002 | Palm OS 3.5, 4.x, 5.x |
| Desktop OS Synchronization |
Windows 98, ME, NT, 2000, XP | Macintosh 8.6, 9.x, X, X v 10.2.x |
| Resolution Pixels | 120x360 | 160x160 | 240x320 | 320x320 | 320x480 |
| Colour Depth | Monochrome | 12 Bit 4,000 colours | 16 Bit 65,000 colours |
| Battery Life | Replaceable Alkaline | Rechargeable Nickel | Rechargeable Lithium |
| Casing | Built-in Flip Cover | External Case | "Ruggedized" |
| Software (Preloaded ROM, CD ROM, Downloadable) | PIM, Word Processing, Spreadsheet, Presentation, Database, Web Browser and Utilities, Backup, E-mail, e-Book and PDF Reader, Media Player, Calculator, File Explorer, Voice Recorder, Terminal Emulation |
| Accessories | Keyboard, Expansion Sleeve, Wired/Wireless LAN or Modem, Camera, GPS, Battery Pack, Battery Charger, Memory and Disk Storage, Printer |
| Expansion Cards | PC Card Type I/II | Compact Flash Type I/II | Secure Digital | MultiMedia |
| Communications | USB | Serial | Infrared | Wired | Wireless |
| Data Input | Stylus, Virtual Keyboard, Thumb Keyboard, Handwriting Recognition, Voice Recorder, Infrared Beaming |
| LAN Wireless | Wi-Fi (802.11b, 802.11a, 802.1x, 802.11e, 802.11g, 802.11i) | Infrared | Bluetooth |
| WAN Wireless | CMDA (800, 1900, 1xRTT, 2000) | GSM/GPRS |
Table 1: Handheld Mobile Device Features and Specifications
If access to information stored by the PIM on a small portable device is the main criteria, a pocket-sized PDA supporting either the Palm OS or Windows CE OS will probably suffice. The large-sized handheld with its integrated keyboard is well-suited for educators with intensive data-entry requirements willing to carry a device that is larger than a PDA and smaller, less powerful and less costly than a notebook computer.
Educators requiring cellular phone and PDA functionality are now considering a convergence device, a combination cellular phone and PDA to avoid carrying two separate devices. The Pocket PC Phone Edition combines the functionality of a PDA with a cellular phone in one device and is best suited for educators requiring PDA functionality as the primary requirement of the device. The Pocket PC Smartphone combines the functionality of a cellular phone with a PDA in one device and is best suited for educators requiring cellular phone functionality as the primary requirement.
Conclusion
This paper explores a number of technical issues and problems encountered in providing technical support for handheld mobile devices to educators and administrators at the University of Victoria. Factors such as the incompatibility of various desktop and mobile device platforms and their associated operating systems; multiple networking standards; limited mobile device support by telecommunications carriers; the interoperability with existing institutionally supported server applications; and the appropriate device selection can significantly affect the successful deployment of mobile computing solutions in higher education.
References
Boerner, Gerald L. (2002). The Brave New World of Wireless Technologies: A Primer for Educators. Syllabus Magazine, October 1, 2002. Retrieved March 21, 2003, from http:www.syllabus.com/article.asp?id=6771
Brown, Bruce. (2001). Buying Guide: Handhelds. PC Magazine, June 14, 2001. Retrieved January 20, 2003, from http://www.pcmag.com/print_article/0,3048,a=3714,00.asp
Dominick, Jay. (2002). Ready or Not - PDAs in the Classroom. Syllabus Magazine, September 1, 2002. Retrieved March 21, 2003, from http://www.syllabus.com/article.asp?id=6705
Fallon, Mary A.C. (2002). Toward a Mobile Campus. Syllabus Magazine, November 1, 2002. Retrieved March 21, 2003, from http://www.syllabus.com/article.asp?id=6896
Hall, Rich. (2003). Your Quick Guide to Mobile Computing. Pocket PC 2003 Buyers Guide, 2003, 6-13.
Multisilta, Jari. (2001). Is the Future of e-Learning in Mobile Devices?. Retrieved March 10, 2003 from the Diffuse Organization, Ed-Media 2001 World Conference Web site: http://www.diffuse.org/ED-Media.html
Nadel, Brian. (2002). Waiting for the Wireless Revolution. PC Magazine, 21(10), 84-98.
Sorcinelli, Don. (2003). The Pocket PC "Decision Tree": Making the Right Device Selection for You or Your Enterprise. Pocket PC 2003 Buyers Guide, 2003, 27-32.
Copyright by AACE. Reprinted from the ED-Media 2003 Proceedings, June 2003 with permission of AACE (http://www.aace.org).