On Aug 20, 2:15 pm, "Casey Borders" <[EMAIL PROTECTED]> wrote: > But if Android is meant to run on multiple different devices shouldn't > developers be concerned with how their apps look on multiple > resolutions, not just the resolution for the launch hardware?
One thing at a time. :) One could come up with an infinite number of screen configurations to support. Which of these are important? Right now, HVGA is the one to target. There's no guarantee the next interesting resolution is QVGA over something else, so I wouldn't suggest spending time on it. This configuration is the baseline for app development in the 1.0 platform. Introducing new screen configurations in the future will be just as much about modifying the platform to support applications that were written against this baseline, as it is modifying applications to specifically target the new configuration. In fact, hopefully it is far more the former rather than the latter. At a practical level, the current UI in the platform is designed specifically for a touchable screen. Doing a QVGA touchable screen at the same density as the current one is... questionable at best, considering how much available screen space that gives. So I definitely wouldn't spend any time trying to get my app running well on this emulator, with this UI, on a QVGA screen. --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new Android 0.9 SDK beta! http://android-developers.blogspot.com/2008/08/announcing-beta-release-of-android-sdk.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
