{"id":325984,"date":"2010-02-16T08:30:08","date_gmt":"2010-02-16T13:30:08","guid":{"rendered":"http:\/\/www.androidguys.com\/?p=13405"},"modified":"2010-02-16T08:30:08","modified_gmt":"2010-02-16T13:30:08","slug":"handling-multiple-screen-sizes-part-one","status":"publish","type":"post","link":"https:\/\/mereja.media\/index\/325984","title":{"rendered":"Handling Multiple Screen Sizes, Part One"},"content":{"rendered":"
\n

\"\"<\/a>This is the first part of a several part series on handling multiple screen sizes in your Android projects. This material is adapted from a chapter in The Busy Coder’s Guide to Android Development, Version 3.0<\/a>.<\/em><\/p>\n

For the first year or so since Android 1.0 was released, all production Android devices had the same screen resolution (HVGA, 320×480) and size (around 3.5″ \/ 9cm). Starting in the fall of 2009, though, devices have been arriving with widely disparate screen sizes and resolutions, from tiny QVGA (240×320) screens to much larger WVGA (480×800) screens.<\/p>\n

Of course, users will be expecting your application to be functional on all of these, and perhaps take advantage of larger screen sizes to add greater value. To that end, Android 1.6 added new capabilities to help better support these differing screen sizes and resolutions.<\/p>\n

The Android documentation has extensive coverage<\/a> of the mechanics of handling multiple screen sizes. These blog posts are designed to complement that coverage.<\/p>\n

Let’s suppose, though, that you start off by totally ignoring the issue of screen sizes and resolutions. What happens?<\/p>\n

If your application is compiled for Android 1.5 or lower, Android will assume your application was designed to look good on the classic screen size and resolution. Android will then automatically do the following:<\/p>\n