On Sat, Nov 14, 2009 at 9:14 PM, Kieran <kieran.flem...@gmail.com> wrote:
> Android 2 SDK released: 27th Oct > Droid released: 6th Nov > So that's 9 days (with a weekend) to test our apps at the new > resolution, make any necessary fixes, then deploy to the Market. I > don't think that's enough, and ultimately it's the Droid users that > suffer. > Android 1.6 was released earlier with multiple screen support being one of the big new features. This is not a new feature in 2.0, and in fact there will be devices shipping on 1.6 with different screens (I believe the Tattoo QVGA device is an example). We also started beating the drum as soon as 1.6 was available for people to update their apps, telling developers that there would soon be devices appearing with different screens. For example: http://android-developers.blogspot.com/2009/10/support-for-additional-screen.html Not that I think it is okay to have so little time between the SDK and devices shipping, but this particular case of supporting different screen sizes is a bad example of the issue. The new contacts API would be better if you want to point at something. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
