X

Google releases near-final Android programming tool

With version 0.9 of the software development kit, programmers get better compatibility with real Android phones due next quarter--but no Bluetooth interface.

Stephen Shankland Former Principal Writer
Stephen Shankland worked at CNET from 1998 to 2024 and wrote about processors, digital photography, AI, quantum computing, computer science, materials science, supercomputers, drones, browsers, 3D printing, USB, and new computing technology in general. He has a soft spot in his heart for standards groups and I/O interfaces. His first big scoop was about radioactive cat poop.
Expertise Processors, semiconductors, web browsers, quantum computing, supercomputers, AI, 3D printing, drones, computer science, physics, programming, materials science, USB, UWB, Android, digital photography, science. Credentials
  • Shankland covered the tech industry for more than 25 years and was a science writer for five years before that. He has deep expertise in microprocessors, digital photography, computer hardware and software, internet standards, web technology, and more.
Stephen Shankland
3 min read

Google on Monday released the first beta version of its software developer kit (SDK) for Android phones, a significant step in the company's hope for "open" phone technology.

Google, which is leading the 34-company Open Handset Alliance to create the largely open-source Android software stack for mobile devices, already had released an "early look" SDK in November 2007. With the new beta SDK, though, the company is telling programmers they can get started in earnest creating software that will work on Android phones due to start shipping later this year, though stopping short of promising full compatibility.

"Since this is a beta release, applications developed with it may not quite be compatible with devices running the final Android 1.0," Google developer advocate Dan Morrill said in a blog post.

Google's promised advantages of Android.
Google's promised advantages of Android. Google

Among changes in the new SDK are the addition of the phone's new home screen as well as some new applications for controlling the camera, playing music, setting alarms, viewing pictures, and dealing with SMS and MMS messages.

Android phones, notably HTC's Dream, are due to ship in the fourth quarter.

Google had hinted in May that the new Android SDK was imminent, but the company ended up sharing it only with finalists in an Android programming contest until Monday. The Android Developer Challenge is awarding $10 million to coders to try to jump-start development efforts; on Monday, Google said a second challenge will be announced later this year that "will give developers a chance to build polished applications once hardware is available."

Google hopes Android phones will be open to run innumerable applications, not just locked down to handle a relatively small number of authorized packages. To achieve this promise though, one key step is helping programmers to write that code. And SDK does just that, for example, by providing a software emulator that can run Android applications without an actual Android phone.

When it comes to Android's APIs (application programming interface), though, some significant features were removed in the new API. "Due to significant API changes in the upstream open-source project and due to the timeline of getting certain Bluetooth profile implementations certified, a comprehensive Bluetooth API will not be possible or present in Android 1.0," Google said.

Also removed is GTalkService, an API for instant messaging. "Due to the security risks inherent in accepting arbitrary data from 'outside' the device, the data messaging facility of the GTalkService will not be present in Android 1.0," though the phone can use Google's servers for Google Talk IM, Google said.

"We know that these changes will affect many developers who have worked with the prior early looks at the SDK, and we are very sorry for the resulting inconvenience," Google said in the release notes. "We look forward to the possibility of restoring some or all of this functionality in a later version of the Android platform."

For further details, see Google's not terribly illuminating Android developer road map, SDK change list, discussion group, and some porting tips for programmers moving their code to the new SDK.