Google spills Satan Phone dev kit
(Belated) coder love
Magic Quadrant for Enterprise Backup/Recovery
As it tells the world that unnamed developers will fill the gaping holes in its inaugural Android phone, Google has released version 1.0 of the Android SDK.
Applications developed using this version of the kit, Google says, will be compatible with mobile devices running version 1.0 of Android platform. This includes the T-Mobile G1, due October 22.
That said, Google Oompah Loompahs will continue tweaking the kit. "The SDK won't remain static - we'll keep improving the tools by adding features and fixing bugs," says Android 'developer advocate' Dan Morrill. "But now developers can rely on the APIs in the SDK and can update their applications to run on Android 1.0-compatible devices."
But Google has yet to release the actual platform code. Its open mobile platform is still closed - though it says the source code will be set free as the first Googlephone goes on sale.
The company didn't respond to questions about the particulars, but it has long said the source code will be opened under a non-reciprocal Apache license - meaning anyone can borrow and tweak it without giving back to the community. Dan Morrill nemesis David "Lefty" Schlesinger - an open source guru with Access, the Japan-based mobile software outfit - has little doubt that countless developers will raid the code for their own selfish reasons. But he wonders how many will help shape the platform as a whole.
"There will be a certain amount of poking through things on the part of the mainstream open source world - say, people who want a Java machine but don't want to pay Sun will use Dalvik [Android's Java virtual machine]," Lefty tells The Reg. "But do I see a large platform community - as opposed to an application developer community - spring up around Android anytime soon? No. Not really.
"I see the same problem with Symbian when they go open source. There's just too much code for anyone to be able to digest in a reasonable amount of time...Plus, people are going to ask themselves 'Why would I volunteer my efforts to Google anyway?'"
He also wonders how many app developers will actually build tools that run atop the platform. "It depends on how fast they actually move the phones," he says. "At this point, the [Android developer] mailing list is obviously just a bunch of students and the like. When it comes to real professional developers, we'll have to wait and see."
At yesterday's G1 press conference in New York, when Google was asked why the phone lacked Exchange support and so many other standard tools, it kept saying that such missing pieces could always be added by third-party developers.
This comes after Google spent months playing hide and seek with earlier versions of the Android SDK. Between early March and late August, the kit was unavailable to all but a handful of developers. But if the phone sells, all will be forgotten.
The question is whether the phone will sell. ®
COMMENTS
Hopefully...
it should be pretty darned good, linux on a mobile - and engineered mostly by google. My only concern is the recent quality of some of their applications... the main one I'm thinking of is Chrome.... if the phone is as flakey and resource heavy as that device, then maybe the Symbian guys are right, and linux (albeit this version of linux) isn't quite ready as a mobile phone platform. God I hope they are wrong though...
It would be pretty darned sweet to have a decent looking mobile (not the G1 attempt obviously) that I could develop for without being crushed by Apple (AppStore NDA hell) or Symbian (only allowing 1 year max for signed application certificates is disgusting, and causes massive confusion to end users).
Pay Sun for Java ?
"people who want a Java machine but don't want to pay Sun will use Dalvik"
Err, or use the OpenJDK...
@DZ-Jay
Yes, you are correct, I hadn't thought about the firmware. Still, if the firmware interacts with the outside world via the software then the firmwares actions are open to subversion.

IT infrastructure monitoring strategies
What you need to know about cloud backup
Agentless Backup is Not a Myth
Top 10 SIEM Implementer’s Checklist
Steps to Take Before Choosing a Business Continuity Partner