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?
I just think BlueTooth could've been great, but its complexity and the lack of certain levels of standards doomed it.
I actually looked at the specs once, thinking maybe it would be interesting. After getting through the actual modulation used, which I didn't care about, I got to the part about establishing connections and stuff. It's horribly complex, and everything seems to be overdone, like someone had a grand vision, but couldn't figure out exactly how to make it work.
My other main problem with it is that it is missing a certain level of standards, which is the set of standards that would define the services a device offers. It does have a mechanism for indicating the type of device to which you are connected, but it seems only enough to pick an icon, not to decide what to actually say.
What it needs is a set of protocols, preferably XML-based, since XML is 31337, that can transfer files, send/receive photos, take pictures, record audio, dial/talk on phone calls, etcetera. These would be organized into a menu on the device, like "Files", "Pictures", "Voice Recorder", "Phone", etcetera, so devices that do some or all of these would simply show a choice (tabs, maybe) for what feature to use.
Any ideas?
Tired of free iPod sigs? Subscribe to my blacklist
It is sad because Bluetooth holds so much promise.
Ha-ha-ha, that's like so nineteen-ninety-nine. Bluetooth is dead, WiFi killed the guy. Not that there was something wrong with it, it's just that market including Intel and Taiwanese industry started making WiFi, which drove the prices through the floor.
I work for an industrial outfit that manufacturers hardware, and many times the final choice was WiFi instead of Bluetooth, Zigbee, etc. Overkill, but hey, who cares, if you just want to save a few bucks in the product costs.
Bluetooth will be sort of like Apple of the PC world - weird and somewhat exotic, better technology for some solutions, but totally handicapped in terms of price competition and market share.