title: Best practices to use when targeting multiple screen resolutions on Android
body: <p>When designing an UI, we need to target many android mutations and various screen resolutions.</p>
  <ul>
  <li><a href="https://stackoverflow.com/questions/5499863/how-to-differentiate-layout-for-480-800-and-480-854-screen-resolutions-in-an">How to differentiate layout for 480 * 800 and 480 * 854 screen resolutions in android?</a></li>
  <li><a href="https://stackoverflow.com/questions/3786214/how-to-layout-support-for-various-screen-in-android">how to layout support for various screen in android?</a></li>
  </ul>
  <p>Both questions above recommend to use different Layout code for different screens. Is it really necessary?</p>
  <ul>
  <li><a href="http://developer.android.com/guide/practices/screens_support.html" rel="nofollow noreferrer">http://developer.android.com/guide/practices/screens_support.html</a></li>
  </ul>
  <p>recommends to</p>
  <blockquote>
  <p><strong>Provide different layouts for different screen sizes</strong></p>
  <p><strong>Provide different bitmap drawables for different screen densities</strong></p>
  </blockquote>
  <p>But I still think, we can support multiple screens without creating standalone layout for each screen resolution. Or am I wrong?</p>
  <p>I know, and I do use, 9-patch for scalable background images (or form inputs, and so on)<br />
  and I do use dp (density pixel) to declare sizes relatively to screen density</p>
  <p>But <strong>what are next best practices</strong> ?</p>