They did that for 1.6 (or 1.5?) - the community built SDKs from source (sans google bits) and later google released a couple of RC SDKs, I think starting 2 weeks before the final version.
That implies that the framework code is open source, and not tied to exclusive contracts with verizon and motorola (er, sorry.. with VENDORS. I meant with VENDORS.) Right now the only people with 2.0 sdks are in google and some VENDORS. Not even other OHA members have it. (And there are rumours that some devs will get it when the device is unveiled.) But lets wait a bit, and see if they can successfully convince everyone they're somehow more open than their competitors (which do in fact offer all those betas, etc.) On Mon, Oct 26, 2009 at 7:29 PM, Frank <[email protected]> wrote: > > Why is the SDK for all android releases always so late on arrival? > Developers usually have barely 1-2 weeks to prepare before the release > is dropped into consumer's hands. With Android 2.0 coming out soon on > the Droid, set to be announced in October 28th and then possibly > releasing in November, the developers are once again VERY late in the > game. > > I know it takes a lot of work in getting an SDK with all the > documentation out. But maybe release a beta SDK just for developers > first? As changes are implemented, newer beta SDKs are provided? At > least now developers are given MORE time to optimize and verify that > their apps still work on the new version release. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
