Bluetooth end user experience still needs tinkering

By Keith Shaw, Network World
December 16, 2002 12:04 AM ET

. What's this?

Bluetooth products finally began arriving on the shelves in 2002 - access points, printer adapters, PC cards and hands-free wireless headsets. We even saw some Bluetooth-enabled cell phones, which is what everyone says will be the catalyst in the looming Bluetooth "explosion."

We haven't tested every Bluetooth product here at Network World, but those we have tested have left us unimpressed. Some stuff works as advertised, other products have left us scratching our heads (and worse, we've wanted to throw some equipment at the wall).

If you can imagine it, Bluetooth is even harder to install than 802.11b wireless LAN equipment. That's saying a lot, considering how wireless LAN products get hammered for its user-unfriendliness all the time. From what we've seen, Bluetooth is a lot worse.

There's no such thing as plug and play in Bluetooth. It's usually plug, then configure, then pray, then, maybe, play.

Related Content

Devices that do only one thing (such as a Bluetooth printer adapter or Bluetooth headset) fare better than more complex devices (access points, PDAs with integrated Bluetooth). While the technology may be simple to understand, it's clear that many vendors have forgotten to make configuration software that is user friendly. That's not too surprising, considering the technology industry's track record - hardware is easy, software is hard.

Here's an example: We received a Bluetooth access point that promised to provide Internet access to Bluetooth-connected devices. Setting up an access point should be as easy as plugging in an Ethernet cable to the access point, letting our DHCP server assign it an IP address, then using our Web browser to configure the access point through this IP address. After configuration, our Bluetooth devices should be able to get the Internet access. (That may sound hard to you, but it really is quite simple).

With this one access point, after it received the IP address and we configured it, the access point kept asking our Bluetooth devices for a pass code. We tried all of the pass codes that the vendor suggested (there were three default ones), yet were still denied access (this happened through two different devices). We went back to the configuration software, discovered the section that listed the default pass codes, and even tried to enter a new pass code for the access point to recognize. It still didn't work. The vendor's documentation was no help - the documentation was one photocopied piece of paper. A second Bluetooth access point we tried out at least gave us connectivity, but had some issues trying to connect to one of our two Bluetooth devices.

For products that focused on one thing, our experience was better. For example, we think Jabra's FreeSpeak Bluetooth Wireless headset did an outstanding job of "cutting the cord" between a hands-free headset and a mobile phone. Our Bluetooth-enabled phone and the Jabra headset connected quickly and painlessly, and we had no further configuration issues. That's what Bluetooth was supposed to do, and in this case it worked.

Maybe Bluetooth is/was too ambitious - what started out as cable replacement morphed into a connectivity situation that is more nightmarish for end users than intended. With a majority of products being pitched as an end-user solution, it's clear that work needs to be done on the software and configuration side before we feel better. And that could be a difficult pill for vendors to swallow, that they might have to spend more time making their products easier to use.

Read more about wireless & mobile in Network World's Wireless & Mobile section.