Skip to content

Most visited

Recently visited


Tablet app quality

Tablets are a significant part of the Android installed base and offer excellent opportunities for user engagement and monetization. The guidelines in this page will help you meet the expectations of tablet users by offering compelling features and an intuitive, well-designed UI.

Although the guidelines are numbered, you can approach them in any order. You should address each guideline’s recommendations to the extent that they’re appropriate for your app, but — in the interest of delivering the best product to your customers — follow them to the greatest extent possible.

Throughout the page you'll find links to resources that can help you address each recommendation.

1. Test for basic tablet app quality

The first step in delivering a great tablet app experience is making sure that it meets the core app quality criteria for all of the devices and form factors that the app is targeting. For complete information, see the Core App Quality Guidelines.

Before publishing, also ensure that your app passes the basic technical checks and launch criteria, such as:

If your app is already uploaded to the Google Play Console, you can see how it is doing against these checks by visiting the Optimization Tips page.

2. Optimize layouts for larger screens

Android makes it easy to develop an app that runs well on a wide range of device screen sizes and form factors. This broad compatibility works in your favor, since it helps you design a single app that you can distribute widely to all of your targeted devices. However, to give your users the best possible experience on each screen configuration — in particular on tablets — you need to optimize your layouts and other UI components for each targeted screen configuration. On tablets, optimizing your UI lets you take full advantage of the additional screen space available and offer new features, present new content, or enhance the experience in other ways to deepen user engagement.

If you developed your app for handsets and now want to distribute it to tablets, you can start by making minor adjustments to your layouts, fonts, and spacing. In some cases — such as for 7-inch tablets or for a game with large canvas — these adjustments may be all you need to make your app look great. In other cases, such as for larger tablets, you can redesign parts of your UI to replace a “stretched UI” with an efficient multi-pane UI, easier navigation, and additional content.

Get rid of a “stretched” UI: On tablets, single-pane layouts lead to awkward whitespace and excessive line lengths. Use padding to reduce the width of UI elements and consider using multi-pane layouts.

Here are some suggestions:

In particular, make sure that your layouts do not appear "stretched" across the screen:

3. Take advantage of extra screen area

Multi-pane layouts result in a better visual balance on tablet screens, while offering more utility and legibility.

Tablet screens provide significantly more screen real estate to your app, especially when in landscape orientation. In particular, 10-inch tablets offer a greatly expanded area, but even 7-inch tablets give you more space for displaying content and engaging users.

As you consider the UI of your app when running on tablets, make sure that it’s taking full advantage of the extra screen area available. Here are some suggestions:

4. Use assets designed for tablet screens

To ensure your app looks its best, provide icons and other bitmap assets for each density in the range commonly supported by tablets. Specifically, you should design your icons for the action bar, notifications, and launcher according to the Iconography guidelines and provide them in multiple densities, so they appear at the appropriate size on all screens without blurring or other scaling artifacts.

Table 1. Raw asset sizes for icon types.

Density Launcher Action Bar Small/Contextual Notification
mdpi 48 x 48 px 32 x 32 px 16 x 16 px 24 x 24 px
hdpi 72 x 72 px 48 x 48 px 24 x 24 px 36 x 36 px
tvdpi (use hdpi) (use hdpi) (use hdpi) (use hdpi)
xhdpi 96 x 96 px 64 x 64 px 32 x 32 px 48 x 48 px
xxhdpi 144 x 144 px 96 x 96 px 48 x 48 px 72 x 72 px

As a minimum, supply a version of each icon and bitmap asset that's optimized for at least one the following common tablet screen densities:

Other tips:

5. Adjust font sizes and touch targets

To make sure your app is easy to use on tablets, adjust the font sizes and touch targets in your tablet UI, for all of the screen configurations you’re targeting. You can adjust font sizes through styleable attributes or dimension resources, and you can adjust touch targets through layouts and bitmap drawables, as discussed above.

Here are some considerations:

6. Adjust sizes of home screen widgets

If your app includes a home screen widget, here are a few points to consider to ensure a great user experience on tablet screens:

7. Full feature set for tablet users

Tablet feature sets

Let your tablet users experience the best features of your app. Here are some recommendations:

8. Target Android versions properly

To ensure the broadest possible distribution to tablets, make sure that your app properly targets the Android versions that support tablets. Initial support for tablets was added in Android 3.0 (API level 11). Unified UI framework support for tablets, phones, and other devices was introduced in Android 4.0

You can set the app's range of targeted Android versions in the manifest file, in the <uses-sdk> element. In most cases, you can target Android versions properly by setting the element's targetSdkVersion attribute to the highest API level available.

At a minimum, check the <uses-sdk> element to make sure that:

  1. targetSdkVersion is declared with value 11 or higher (14 or higher is recommended), OR
  2. minSdkVersion is declared with value 11 or higher.
  3. If a maxSdkVersion attribute is declared, it must have a value of 11 or higher. Note that, in general, the use of maxSdkVersion is not recommended.

9. Declare hardware feature dependencies properly

Handsets and tablets typically offer slightly different hardware support for sensors, camera, telephony, and other features. For example, many tablets are available in a Wi-Fi configuration that does not include telephony support.

So that you can distribute a single APK broadly across your full customer base of phones and tablets, make sure that your app doesn't declare requirements for hardware features that aren't commonly available on tablets. Instead, properly declare the hardware features as not required in the app manifest, as described below.

After declaring hardware features as not required, make sure to test your app on a variety of devices. The app should function normally when the hardware features it uses are not available, and it should offer "graceful degradation" and alternative functionality where appropriate.

For example, if an app normally uses GPS to set the location but GPS is not supported on the device, the app could let the user set the location manually instead. The app can check for device hardware capabilities at runtime and handle them as needed.

10. Declare support for tablet screens

To ensure that you can distribute your app to a broad range of tablets, your app should declare support for tablet screen sizes in its manifest file, as follows:

If the app declares a <compatible-screens> element in the manifest, the element should include attributes that specify all of the size and density combinations for tablet screens that the app supports. Note that, if possible, you should avoid using the <compatible-screens> element in your app.

11. Showcase your tablet UI in Google Play

After you've created a rich, optimized UI for your tablet app, make sure that you let your customers know about it! Here are some key ways to promote your tablet app to users on Google Play.

Upload screenshots of your tablet UI

Tablet users want to know what your app is like on a tablet device, not on a phone. If you developed a tablet app, make sure to upload screenshots of your tablet UI to the Google Play Console. Here are some guidelines:

Update your app description and release notes

Update your promotional video

Many users view an app's promotional video to get an idea of what the app is like and whether they'll enjoy it. For tablet users, capitalize on this interest by highlighting your app's tablet UI in your promotional video. Here are some tips and guidelines:

Feature your tablet UI in your promotional campaigns

Let tablet users know about your tablet UI in your promotional campaigns, web site, social posts, advertisements, and elsewhere. Here are some suggestions:

12. Follow best practices for publishing in Google Play

Here are some best practices for delivering a successful tablet app on Google Play.

Check out your app's Optimization Tips

The Google Play Console offers an Optimization Tips page that lets you quickly check how your app is doing against basic guidelines for tablet app distribution and quality. To visit the page, sign into the Play Console, load the app from All Applications, and click Optimization Tips in the left navigation.

The Play Console creates your app's Optimization Tips page by running a series of checks to verify basic quality criteria. If it finds any issues, it alerts you to them as "To Do" items in the Optimization Tips page.

If you've developed a tablet experience for your app, make sure to visit the Optimization Tips page to see how your app is doing against the basic checks. If there are any issues listed, we recommend addressing them in your app and uploading a new binary for distribution, if needed.

If the Optimization Tips page lists "To Do" issues that you feel don't apply to your app or affect its quality on tablets, please notify us using the Designed for Tablets Contact Form ». We will review your app and update your Optimization Tips page as appropriate.

Confirm the app's filtering

After you've uploaded the app to the Play Console, check the APK's Supported Devices list to make sure that the app is not filtered from tablet devices that you want to target.

Distribute as a single APK

It's recommended that you publish your app as a single APK for all screen sizes (phones and tablets), with a single Google Play listing. This approach has several important advantages.

If necessary, you can alternatively choose to deliver your app using Multiple APK Support, although in most cases using a single APK to reach all devices is strongly recommended.

Setting up a test environment for tablets

Assess the quality of your app on tablets — both for core app quality and tablet app quality — with a suitable hardware or emulator environment for testing.

Compared to the recommended test environment for testing against the core app quality criteria, include mid-size tablets and tablets with more or fewer hardware/software features.

Table 1. A typical tablet test environment might include one or two devices from each row in the table below, with one of the listed platform versions, screen configurations, and hardware feature configurations.

Type Size Density Version AVD Skin
7-inch tablet large or
Android 4.0+ (API level 14 and higher) WXGA800-7in
10-inch tablet xlarge or
Android 3.2+ (API level 13 and higher) WXGA800
This site uses cookies to store your preferences for site-specific language and display options.


This class requires API level or higher

This doc is hidden because your selected API level for the documentation is . You can change the documentation API level with the selector above the left navigation.

For more information about specifying the API level your app requires, read Supporting Different Platform Versions.

Take a one-minute survey?
Help us improve Android tools and documentation.