On this page
- Support multiple screen sizes
- Provide backward compatibility
- Use memory efficiently
Reaching new users means supporting an increasing variety of Android platform versions and device specifications. To improve the user experience, optimize for common RAM configurations, and screen sizes and resolutions.
Support multiple screen sizes
Your app can provide a better user experience for billions of users if it supports screens of various sizes and resolutions. This section describes a few ways you can do this.
Use density-independent pixels (dp)
- Defining layout dimensions with pixels doesn’t work well because different screens have different pixel densities, so the same number of pixels may correspond to different physical sizes on different devices.
- To overcome this Android supports the density-independent pixel (dp), which corresponds to the physical size of a pixel at 160 dots per inch (mdpi density).
- Defining layouts with dp ensures that the physical size of your user interface is consistent regardless of device. Visit the Android guide on Supporting Multiple Screens for best practices on using density-independent pixels.
Test text and graphics on ldpi and mdpi screen densities
- Test to ensure that your text and graphics work well on low- and medium-density (ldpi and mdpi) screens because these are common densities, especially in lower-cost devices. Look out for text that may be unclear on lower-density screens, where fine details aren't visible.
- Devices with lower-density screens tend to have lower hardware specifications. To ensure that your app performs well on these devices, consider reducing or eliminating heavy graphics processing loads, such as animations and transitions.
- For more information on supporting different densities, see the Android training on Supporting Different Densities.
Test layouts on small and medium screen sizes
- Validate that your layouts scale down by testing on smaller screens. As screen sizes shrink, be very selective about visible UI elements, because there is limited space for them.
- The Material Design guidelines describe metrics and keylines to ensure that your layouts can scale across screen densities.
- For more information on supporting different screen sizes, see the Android training on Supporting Different Screen Sizes.
Provide backward compatibility
Not all of your users may be using devices powered by the latest, greatest version of the Android platform. Here are some ways you can improve backward compatibility, helping make your app available to as many people as possible.
- Apps should build and target a recent version of Android to ensure they offer the most
current behavior across a broad range of devices; this still provides
backward compatibility to older versions. Here are the best practices for
targeting API levels appropriately:
targetSdkVersionshould be the latest version of Android. Targeting the most recent version ensures that your app inherits newer runtime behaviors when running newer versions of Android. Be sure to test your app on newer Android versions when updating the
targetSdkVersionas it can affect app behavior.
minSdkVersionsets the minimum supported Android version. Use Android 4.0 (API level 14: Ice Cream Sandwich) or Android 4.1 (API level 16: Jelly Bean)—these versions give maximum coverage for modern devices. Setting
minSdkVersionalso results in the Android build tools reporting incorrect use of new APIs that might not be available in older versions of the platform. By doing so, you are protected from inadvertently breaking backward compatibility.
- Consult the Android dashboards, the Google Play Developer Console for your app, and industry research in your target markets to gauge which versions of Android to target, based on your target users.
Use the Android Support libraries
Ensure your app provides a consistent experience across OS versions by using the
Android Support Library.
This library provides backward-compatible versions of Android framework APIs
as well as features that are only available through the library APIs
AppCompatActivityand the Material Design Support Library.
- Some of the highlights include:
- v4 and v7 support library: Many framework APIs for older versions of
Android such as
- Material Design support library: APIs to support adding Material Design components and patterns to your apps.
- Multidex support library: provides support for large apps that have more than 65K methods. This can happen if your app is using many libraries.
- v4 and v7 support library: Many framework APIs for older versions of Android such as
- For more information on the available support libraries, see the Support Libraries Features section of the Android Developer site.
Use Google Play services
- Google Play services brings the best of Google APIs independent of Android platform version. Consider using features from Google Play services to offer the most streamlined Google experience on Android devices.
- Google Play services also include useful APIs such as
GcmNetworkManager, which provides much of Android 5.0’s
JobSchedulerAPI for older versions of Android.
- Updates to Google Play services are distributed automatically by the Google Play store, and new versions of the client library are delivered through the Android SDK Manager.
Use memory efficiently
Memory is an unsung hero of the user experience. Good memory management can make your app more stable and more performant; in some cases, its effective use may be the only thing making your app usable at all. Here are some ways you can help your app use memory wisely.
Reduce memory footprint on low-cost devices
- Adjust your memory footprint dynamically to ensure compatibility across devices with different RAM configurations.
- Methods such as
getMemoryClass()help determine memory constraints at runtime. Based on this information, you can scale down your memory use. As an example, you can use lower resolution images on low memory devices.
- For more information on managing your app’s memory, see the Android training on Managing Your App’s Memory.
Avoid long-running processes
- Long-running processes stay resident in memory and can slow
down the device. In most situations, your app should wake up for a given
event, process data, and shut down. You should use Firebase Cloud Messaging
GcmNetworkManagerto avoid long running background services and reduce memory pressure on the user’s device.
Benchmark memory use
- Android Studio provides memory benchmarking and profiling tools, enabling
you to measure memory use at run time. Benchmarking your app’s memory
footprint enables you to monitor memory use over multiple versions of
the app. This can help catch unintentional memory footprint growth. These
tools can be used in the following ways:
- Use the Memory Monitor tool to find out whether undesirable garbage collection (GC) event patterns might be causing performance problems.
- Run Heap Viewer to identify object types that get or stay allocated unexpectedly or unnecessarily.
- Use Allocation Tracker to identify where in your code the problem might be.
- For more information on benchmarking memory use, see the Android Monitor pages on the Android Developers site.