August 26th, 2008
Google Android loses Bluetooth API, Bluetooth still lives
Google has dropped both the Bluetooth and GTalkService IM APIs from the Android 0.9 beta SDK.
Here’s the skinny on why the GTalkService API bit the dust:
We decided to postpone GTalkService’s data-messaging functionality for the following reasons:
1 - “Repurposing” Google Talk Friends
2 - Verifying Remote Intent Senders
3 - Placing Too Much Security Burden on Developers
Note: The removal of the Bluetooth API DOES NOT AFFECT Android’s ability to connect to Bluetooth headsets or other Bluetooth devices. All it means is that programmers won’t have access to Bluetooth APIs.
The reason the Bluetooth API was dropped is pretty straightforward:
The reason is that we plain ran out of time. The Android Bluetooth API was pretty far along, but needs some clean-up before we can commit to it for the SDK. Keep in mind that putting it in the 1.0 SDK would have locked us into that API for years to come.
Both of these reasons are absolutely valid and be removing these APIs I believe that Google has made Android better since nothing harms a product more than poorly implemented ideas and serious security issues.
Want to get in touch? Feel free to drop me a note!
Right to Reply: Should any industry representatives wish to comment on any posts on Hardware 2.0, I will be happy to publish their reply verbatim on this blog.
Adrian is a technology journalist and author who has devoted over a decade to helping users get the most from technology. He also runs a popular blog called The PC Doctor. See his full profile and disclosure of his industry affiliations.
