From 71f8127165b64fad96e1d1c5f2ffc11721427882 Mon Sep 17 00:00:00 2001 From: Dirk Dougherty Date: Mon, 22 Apr 2013 12:12:44 -0700 Subject: Doc change: Add tablet optimization tips info/link. Change-Id: Iee793b5fbb39e551c0df39ba4aeac40b55fb16d6 --- docs/html/distribute/googleplay/quality/tablet.jd | 213 ++++++++++++++++------ 1 file changed, 153 insertions(+), 60 deletions(-) diff --git a/docs/html/distribute/googleplay/quality/tablet.jd b/docs/html/distribute/googleplay/quality/tablet.jd index a54348b..9c713de 100644 --- a/docs/html/distribute/googleplay/quality/tablet.jd +++ b/docs/html/distribute/googleplay/quality/tablet.jd @@ -16,7 +16,7 @@ page.title=Tablet App Quality Checklist
  • 9. Declare dependencies properly
  • 10. Declare tablet screens support
  • 11. Showcase your tablet UI
    • -
  • 12. Follow publishing best practices
    • +
  • 12. Follow publishing best practices

    • Testing

    @@ -68,8 +68,10 @@ href="{@docRoot}distribute/googleplay/quality/core.html">Core App Quality Guidel
  • Screenshots are uploaded to Google Play
    • -

    The sections that follow provide more information about these and other -quality guidelines for tablet apps.

    +

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

    2. Optimize your layouts for larger screens

    @@ -312,7 +314,15 @@ resource qualifiers to ensure that the proper set of alternative resources gets loaded. -

    At a minimum, your app should supply custom drawables and assets for common tablet screen densities, tagged with the qualifiers hdpi, xhdpi, or xxhdpi.

    +

    At a minimum, your app should supply sets of + custom drawables and assets for common tablet screen densities, + tagged with these qualifiers as appropriate:

    + +

    @@ -482,62 +492,103 @@ to a replacement feature (also see the section below on hardware features).

    8. Target Android versions properly

    To ensure the broadest possible distribution to tablets, make sure that your -app is targeting the Android versions that support tablets. You can declare -the targeted range of Android versions in the -<uses-sdk> -element in the app manifest.

    +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 (API level 14) and is supported in later versions. -

    At a minimum, your app's -<uses-sdk> -should declare support for Android versions as follows:

    +

    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.

    - -

    In all cases, the app must function normally when the hardware features it -uses are not available and should offer "graceful degradation" and alternative -functionality where appropriate. For example, if GPS is not supported on the device, -your app could let the user set their location manually. The app should do -run-time checking for the hardware capability that it needs and handle as needed.

    + +

    + 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 + as needed. +

    @@ -570,9 +621,7 @@ run-time checking for the hardware capability that it needs and handle 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 the -<supports-screens> -element in the app manifest, as follows:

    +declare support for tablet screen sizes in its manifest file, as follows:

    • A @@ -617,14 +666,14 @@ element in your app.

      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 Developer Console. Here are some guidelines: + of your tablet UI to the Google Play Developer Console. Here are some guidelines:

        @@ -652,9 +701,9 @@ element in your app.

      -
      +

      Update your app description and release notes -

      +
      • In your app description, make sure to highlight that your app offers @@ -667,9 +716,9 @@ element in your app.

      -
      +

      Update your promotional video -

      +

      Many users view an app's promotional video to get an idea of what the app is @@ -698,9 +747,9 @@ element in your app.

    -
    +

    Feature your tablet UI in your promotional campaigns -

    +

    Make sure to let tablet users know about your tablet UI in your promotional @@ -759,15 +808,59 @@ element in your app.

    -

    12. Follow best practices for publishing in Google Play

    +

    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 Developer Console now 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 Developer Console, +load the app from All Applications, and click Optimization Tips in +the left navigation.

    + +
    +
    +

    How to Send Feedback

    + +

    Please use the link below to send +feedback or request a manual review of your Optimization Tips.

    + +

    Make sure to read the relevant sections of the Tablet App Quality +Guidelines prior to sending feedback.

    + +

    Tablet Optimization +Tips Feedback Form »

    +
    +
    + +

    The Developer 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 Tablet Optimization +Tips Feedback Form. We +will review your app and update your Optimization Tips page as +appropriate.

    -Here are some best practices to consider when publishing a tablet app on Google Play.

    -
    Check the app's filtering
    +

    Confirm the app's filtering

    After you've uploaded the app to the Developer 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
    +

    Distribute as a single APK

    It's recommended that you publish your app as a single APK for all screen -- cgit v1.1