Slashdot Mirror
Bluetooth Application Programming?
Comatose51 asks: "I've been desperately trying to create an application that uses Bluetooth over the last month. I've been frustrated by the lack of good books and lack of hardware compatible with readily available Bluetooth APIs. While Microsoft added Bluetooth support into Windows XP since SP1, most hardware vendors do not use the Microsoft Bluetooth Stack. Instead, they use other proprietary stacks that costs money to obtain the SDKs and APIs for. I had to buy the Microsoft Bluetooth Mouse to get their Bluetooth Stack and a compliant adapter, which is still many times cheaper than what some companies charge for their APIs and SDKs. Java is the other (potentially better, easier) option but I haven't found any hardware vendors that state that they're Java (JSR-82) compliant. Is there really no easy way of developing Bluetooth applications for Windows? It is sad because Bluetooth holds so much promise. Thanks in advance." Might Bluetooth's problems stem from the fact that there is no consistent development platform for the technology?
<sarcasm>
...which is why the market is now overflowing with WiFi-enabled mobile phones, WiFi headsets, WiFi-enabled GPS receivers etc. etc.
</sarcasm>
Bluetooth and WiFi are complementary technologies. Bluetooth headsets make perfect sense whereas a WiFi headset would have its battery life measured in minutes. Likewise, using Bluetooth for wireless networking is something you do only when you have no other alternative.
I usually carry the following devices with me:
- Ericsson R520m GSM mobile phone with Bluetooth
- Sony-Ericsson HBH-30 Bluetooth headset
- Fujitsu-Siemens Pocket Loox 600 Pocket PC with Bluetooth
- Fortuna GPSmart BT GPS receiver with Bluetooth
Yes, I can get a WiFi-enabled PDA. Show me where to get WiFi versions of the other devices.My opinion? See above.
I worked on an application for about 4 months, using Bluetooth communication for communication between two Windows PCs (as proof of concept for future devices). The experience was less than stellar. The SDK I used was discontinued while I was coding, but too late to switch to a new one (before funding ran out).
So what's my advice? Have a backup plan. Isolate your network communication procedures so you can easily switch to a new protocol/stack when one comes along. My code has been re-used, ported over to 802.11, because they found a power solution that would allow them to use the more standard protocol.
Bluetooth programming was only marginally more complicated than working with proprietary data transfer protocols I worked with in 1994. But 8 years later, it should have been easier. Call me a cynic, but the OBEX implementation of the stack I worked with caused me too many sleepless nights.
Dan