The SDK docs in the open source repo say; "Based on the target device screen density, the Android framework will scale down assets by a factor of 0.75 (low dpi screens)..."
And the default QVGA skin is a low density one. Just to be clear; are you saying that the device won't show in market because it's a standard DPI and low resolution screen, or are you saying they'll be blocked just because apps don't explicityly say they support QVGA? >From the docs in the open repo SDK I would have expected apps to be available and scaled down using the 0.75 factor. Al. On Sep 8, 8:34 pm, Dianne Hackborn <hack...@android.com> wrote: > On Tue, Sep 8, 2009 at 11:33 AM, Dianne Hackborn <hack...@android.com>wrote: > > > And this all ignores what is to me probably likely to be an even bigger > > part of the market, lower density QVGA and WQVGA screens. > > And speaking of... http://www.htc.com/www/product/tattoo/overview.html > > One of the important things to know about the QVGA devices like this is that > none of the existing apps will show up on the market there, because until > 1.6 developers have had no requirement to design for a smaller screen, and > there is little the platform can do to make existing apps work on a smaller > screen with a good experience. (Note that this is different for WQVGA > screens, which are actually larger than the G1, just lower density, which is > something the platform can easily account for with reasonable results.) > > Anyway, as an app developer, I think it would be worth considering getting > my applications to work on QVGA as the first priority. At the minimum this > means either <uses-sdk android:targetSdkVersion="4" /> or <supports-screen > android:smallScreens="true" android:anyDensity="true" /> in the manifest, > and then doing whatever fiddling of the UI is required to make it fit on the > smaller QVGA screen. (Note you can also supply alternative layouts in the > layout-small directory.) You'll also probably want to create low density > graphics and place those in drawable-ldpi. > > Again, there should be a blog post soon that goes into much more detail on > this topic. > > -- > 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 -~----------~----~----~----~------~----~------~--~---
