Linked by Adam S on Tue 26th Aug 2008 17:43 UTC, submitted by stonyandcher
Google has dropped the Bluetooth and GTalkService instant messaging APIs (application program interfaces) from the set of tools for the first version of the mobile phone OS, Android 1.0, according to the Android Developers Blog. The company opted to drop the Bluetooth API because "we plain ran out of time," said Nick Pelly, one of the Android engineers responsible for the Bluetooth API, on the blog posting. But the company made clear that handsets using the Android OS will work with other Bluetooth devices such as headsets, for example. Ed note: To be clear, only the APIs are delayed, not the features. This suggests third party apps will not be able to access these frameworks.
Thread beginning with comment 328129
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:
2005-11-10
My point is that on a mobile phone, just because something is there people won't necessarily use it. It's not the same as a Desktop.
My phone has a ton of stuff I'll never use and don't want to use. I immediately replaced the built in browser with Opera mini, and I sure won't ever use all the "this icon connects you to our WAP site without asking for permission" icons placed in my way. They even have hardware buttons on some phones that connect you to their internet portal full of overpriced crappy ringtones and I wouldn't buy a phone with one of those.
The difference on a phone is that the built in stuff == money wasted.