Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8165541
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 6, 20262026-06-06T19:34:00+00:00 2026-06-06T19:34:00+00:00

I understand there is plenty of documentation about designing for multiple screen support in

  • 0

I understand there is plenty of documentation about designing for multiple screen support in Android. and I have read the Android guide here as well as a number of similar questions such as this

However I’m still a little confused as to how I should implement it for my application. I plan to target the following device configurations

enter image description here

Am I correct in thinking I will need to structure the project layouts as follows:

  • Medium density Normal screens HVGA 320×480 (160dpi):

    res/layout-mdpi (320 x 480 )
    res/layout-land-mdpi (480 x 320 )
    
  • High density Normal screens WVGA800 480×800 (x854) (240 dpi)

    res/layout-hdpi (480 x 800)
    res/layout-land-hdpi (800 x 480)
    

But what about the Medium density, large screen devices?

I plan to use sets of both high and medium density drawables too. My primary concern at this early stage is using suitable background images for each layout. For example, to support both the 480×800 and 480×854 sizes, I plan to simply use an ImageView as the background such as:

<ImageView
    android:id="@+id/imageView1"
    android:layout_width="wrap_content"
    android:layout_height="wrap_content"
    android:src="@drawable/bg"
    android:scaleType="center"/>

The ‘bg’ drawable will always be 480×854 and by using:

android:scaleType="center"

I’m hoping this will take care of those two screen sizes. Whereby the image keeps its original appearance but is centred on the 480×800 screens. I will lose some pixels off the image but as long as the image isn’t scaled then that suits my needs.

I plan to have a set of 320×480 assets for the normal screens.

I’m just hoping I’m following the correct procedure here so I appreciate any info/tips from you guys. Thanks in advance

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-06T19:34:02+00:00Added an answer on June 6, 2026 at 7:34 pm

    In my experience you don’t really need to customize your layout for the small/medium/large/etc screens, as long as you have your drawables for the different densities. Like the documentation says, Android will attempt to render your layout properly on different screen sizes.

    By default, Android resizes your application layout to fit the current device screen. In most cases, this works fine. In other cases, your UI might not look as good and might need adjustments for different screen sizes.

    The ‘other cases’ applies only if you really want to change your layout on larger screens.

    Using android:scaleType="center" works for me, but it will, like you said, leave empty space around your layout on larger screens if it should fit on smaller screens as well. If you have a fully customized view with ‘widgets’ that should be placed exactly right, and you don’t want to be programmatically determining the scaling and applying the same scaling to your widgets, this is definitely the way to go.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I understand there are multiple questions about this on SO, but I have yet
I understand that floating point calculations have accuracy issues and there are plenty of
Just to preface my question, I understand that there is no direct support for
There is something I dont understand in core data. I have created a NSManagedDocument,
There is something I don't understand in Java's regular expressions. I have the following
I understand there are many threads like mine but I have been trying to
I read about NSAutoReleasePool and understand that it makes memory management easier on iPhone.
I read plenty of articles about Azure and .NET Service Bus. I think I
I understand there is a limit to the number of requests per day using
I understand that there is a setting in Sun JVM for dumping the heap

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.