In fact since the APIs for this have been in the platform since 1.6, by the simple act of saying you are targeting 1.6 or later (with android:targetSdkVersion="4" or larger), you are telling the platform you know about different screen sizes and will get the full available space. You already see this today on the Samsung Tab, and if you set up a larger screen in the emulator.
The best way to prepare for tablets is to do what is already there: say you support larger screens, and ensure you do work on them. The only thing that is really different is xlarge screens. Those were introduced in 2.3. Prior to that, we never really defined what the maximum size of a "large" screen is, so the cut-off points between these is now more formalized. Also because we never defined the limit for large, it is unlikely that we will do any kind of "compatibility" for apps that say they support large but don't support xlarge. That is, no postage stamp in the middle like we did for apps targeting prior to 1.6 that only ever thought about 480x320 mdpi screens. Once you are in the "I know screens are more than 480x320" world, you need to be sure you do something reasonable for any screen larger than the minimum size class you have said you support. On Sun, Jan 9, 2011 at 6:36 PM, Romain Guy <romain...@android.com> wrote: > It depends on how your app is setup. Depending on how applications declare > how they support multiple screens and densities the app might be boxed, > scaled or simply fill the screen and rely on layout to look correct. > > > On Sun, Jan 9, 2011 at 6:09 PM, Craig Mitchell <craig...@gmail.com> wrote: > >> And you all have done a fantastic job at that. However, I'm not a fan >> of boxing an app for large screens. I would much prefer an app to be >> expanded to the full screen size and look a little pixelated, then >> only take up a small section of the screen. >> >> ...apologies that this comment is off topic. >> >> >> On Jan 10, 9:44 am, Dianne Hackborn <hack...@android.com> wrote: >> > We try hard to not break apps in newer versions of the platform, as long >> as >> > they are written correctly. >> > >> > On Sun, Jan 9, 2011 at 2:40 PM, sblantipodi < >> perini.dav...@dpsoftware.org>wrote: >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > > I would like to know if our applications written for 2.2 and 2.3 >> > > tablets will work >> > > on honeycomb without modifications. >> > >> > > On Jan 7, 1:27 am, Dianne Hackborn <hack...@android.com> wrote: >> > > > On Thu, Jan 6, 2011 at 3:39 PM, sblantipodi < >> > > perini.dav...@dpsoftware.org>wrote: >> > >> > > > > Obviously this new android will grant compatibility to olter apps >> > > > > right? >> > >> > > > You may have seen the numerous developer blogs posts on preparing >> for >> > > larger >> > > > screens and such. :) >> > >> > > > -- >> > > > 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<android-developers%2bunsubscr...@googlegroups.com><android-developers%2Bunsubs >> cr...@googlegroups.com> >> > > For more options, visit this group at >> > >http://groups.google.com/group/android-developers?hl=en >> > >> > -- >> > 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<android-developers%2bunsubscr...@googlegroups.com> >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en >> > > > > -- > Romain Guy > Android framework engineer > romain...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support. 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<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- 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
