From c6af49efc467e379e7ac56246e9c7f0e6ebddc00 Mon Sep 17 00:00:00 2001 From: Dirk Dougherty Date: Mon, 1 Apr 2013 12:10:14 -0700 Subject: [PATCH] Doc change: Add tablet basic checks. Change-Id: I9fab8f29515e086feffd45bcbcf9e7d6602a734d --- .../html/distribute/googleplay/publish/register.jd | 8 +- docs/html/distribute/googleplay/quality/tablet.jd | 867 +++++++++++++++++---- docs/html/support.jd | 2 +- 3 files changed, 703 insertions(+), 174 deletions(-) diff --git a/docs/html/distribute/googleplay/publish/register.jd b/docs/html/distribute/googleplay/publish/register.jd index dd73898e56e3..5f1f2eaccd19 100644 --- a/docs/html/distribute/googleplay/publish/register.jd +++ b/docs/html/distribute/googleplay/publish/register.jd @@ -23,7 +23,7 @@ page.title=Get Started with Publishing @@ -57,11 +57,11 @@ with the Developer Program Policies and US export law, a Google Checkout account, you can quickly set one up during the process. -

When your registration is verified, you’ll be notified at the email address you specified during registration.

+

When your registration is verified, you’ll be notified at the email address you specified during registration.

-

Set up a Google Checkout Merchant account

+

Set up a Google Wallet Merchant account

-

If you want to sell products on Google Play — priced apps, in-app products, or subscriptions — you will also need to set up a Google Checkout Merchant Account. You can do that at any time, but make sure to first review the list of merchant countries.

+

If you want to sell products on Google Play — priced apps, in-app products, or subscriptions — you will also need to set up a Google Wallet Merchant Account. You can do that at any time, but make sure to first review the list of merchant countries.

To set up a Merchant account from the Developer Console:

diff --git a/docs/html/distribute/googleplay/quality/tablet.jd b/docs/html/distribute/googleplay/quality/tablet.jd index 24a30f177b99..6d7e3e2cbb05 100644 --- a/docs/html/distribute/googleplay/quality/tablet.jd +++ b/docs/html/distribute/googleplay/quality/tablet.jd @@ -5,7 +5,7 @@ page.title=Tablet App Quality Checklist

Checklist

    -
  1. 1. Test for Core App Quality
    2. +
  2. 1. Test for Core Tablet App Quality
  3. 2. Optimize your layouts
  4. 3. Use the extra screen area
  5. 4. Use assets designed for tablets
    6. @@ -14,16 +14,17 @@ page.title=Tablet App Quality Checklist
  6. 7. Offer the app's full feature set
  7. 8. Don’t require hardware features
  8. 9. Declare tablet screen support
    9. -
  9. 10. Follow best practices for publishing in Google Play
    10. +
  10. 10. Showcase your tablet UI
    11. +
  11. 11. Follow publishing best practices

Testing

    +
  1. Basic Technical Checks for Tablets
  2. Setting Up a Test Environment
-

Before you publish an app on Google Play, it's important to make sure that the app meets the basic expectations of tablet users through compelling features and an intuitive, well-designed UI.

@@ -46,32 +47,81 @@ to the greatest extent possible.

that can help you address the topics raised in each task.

-

1. Test for Core App Quality

+

1. Test for Core Tablet App Quality

+ +

Before publishing, make sure that your app and it's store listing meet the + core quality guidlines below.

+ +
Core 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 Checklist. +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.

-

To assess the quality of your app on tablets — both for core app quality -and tablet app quality — you need to set up a suitable -hardware or emulator environment for testing. For more information, -see Setting Up a Test Environment.

+
Basic technical checks for tablets
+

+ Before publishing, you should also ensure that your app passes several basic + technical checks, such as: +

- - - - -

Related resources:

-
    -
  • Core App Quality -Guidelines — A set of core quality criteria that all Android -apps should meet on all targeted devices.
    • +
      +
    • Targeting appropriate Android versions
      • +
    • Specifying any feature dependencies properly
      • +
    • Declaring support for appropriate screens
    -
+ +

+ For details, see Basic Technical + Checks. +

+ +
Tablet screenshots and other promotional tools
+ +

Make sure that you upload screenshots of your tablet UI to the + Developer Console and highlight your tablet experience in your app description, + video, and promotional campaigns. For details, see Showcase your + tablet UI in Google Play.

+ +
Test environment
+ +

+ To assess the quality of your app on tablets, you need to set up a suitable + hardware or emulator environment for testing. For more information, see + Setting Up a Test Environment. +

+

+ Note that a successful tablet app will go well beyond the core and tablet + app quality criteria to offer a custom tablet experience to users. Read + the sections below for ideas on how to plan and develop a great tablet UI for + your app. +

+ + +
+

+ Related resources +

+ + +

2. Optimize your layouts for larger screens

@@ -97,9 +147,12 @@ efficient multipane UI, easier navigation, and additional content.

Here are some suggestions:

- +

Get rid of "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.

+style="font-weight:500;">Get rid of "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.

- - - - -

Related resources:

- -
+
+

+ Related resources +

+ + +

3. Take advantage of extra screen area available on tablets

- +

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

+style="font-weight:500;">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, @@ -175,39 +250,58 @@ users to navigate your app.

  • Plan how you want the panels of your compound views to reorganize when screen orientation changes.
    • - -
    -
    - +

    Compound views combine several single views from a handset UI (above) into a richer, more efficient UI for tablets (below).

    +style="font-weight:500;">Compound views combine several single views from a +handset UI (above) into a richer, more efficient UI for tablets +(below).

  • While a single screen is implemented as an {@link android.app.Activity} subclass, consider implementing individual content panels as {@link -android.app.Fragment} subclasses. This lets you maximize code reuse across -different form factors and across screens that share content.
    • +android.app.Fragment} subclasses. This lets you +maximize code reuse across different form factors and across screens that +share content.
  • Decide on which screen sizes you'll use a multi-pane UI, then provide the different layouts in the appropriate screen size buckets (such as large/xlarge) or minimum screen widths (such as sw600dp/sw720).
    • - - - - -

    Related resources:

    -
      -
    • Multi-pane Layouts — Android Design guide for using multi-pane UI, including examples of how to flatten navigation and integrate more content into your tablet UI.
      • -
    • Planning for Multiple Touchscreen Sizes — Android Training class that walks you through the essentials of planning an intuitive, effective navigation for tablets and other devices.
      • -
    • Designing for Multiple Screens — Android Training class that walks you through the essentials of planning an intuitive, effective navigation for tablets and other devices.
      • -
    -
    +
    +

    + Related resources +

    + + +

    4. Use Icons and other assets that are designed for tablet screens

    @@ -268,18 +362,41 @@ resource qualifiers to ensure that the proper set of alternative resources gets loaded. - - - - -

    Related resources:

    -
      -
    • Iconography — Android Design document that shows how to use various types of icons.
      • -
    • Providing Resources — Developer documentation on how to provide sets of layouts and drawable resources for specific ranges of device screens.
      • -
    • Supporting Multiple Screens — API Guide documentation that explains the details of managing UI for best display on multiple screen sizes.
      • -
    • Supporting Different Screens — Android Training class that takes you through the process of optimizing the user experience for different screen sizes and densities.
      • -
    -
    +
    +

    + Related resources +

    + + +

    5. Adjust font sizes and touch targets for tablet screens

    @@ -300,29 +417,49 @@ correspond to, and ensure that there are no improper line breaks in labels, titles, and other elements.
  • The recommended touch-target size for onscreen elements is 48dp (32dp minimum) — some adjustments may be needed in your tablet UI. Read Metrics and +href="{@docRoot}design/style/metrics-grids.html">Metrics and Grids to learn about implementation strategies to help most of your users. To meet the accessibility needs of certain users, it may be appropriate to use larger touch targets.
  • When possible, for smaller icons, expand the touchable area to more than -48dp using {@link android.view.TouchDelegate} or just centering the icon within -the transparent button.
    • +48dp using {@link android.view.TouchDelegate} +or just centering the icon within the transparent button. - - - - -

    Related resources:

    -
      -
    • Metrics and Grids - — Android Design document that explains how to arrange and size touch targets and other UI elements on the screen.
      • -
    • Typography — Android Design document that gives an overview of how to use typography in your apps.
      • -
    • Supporting Multiple Screens — Developer documentation that explains the details of managing UI for best display on multiple screen sizes.
      • -
    • Supporting Different Densities — Android Training class that shows you how to provide sets of layouts and drawable resources for specific ranges of device screens.
      • -
    -
    +
    +

    + Related resources +

    + + +

    6. Adjust sizes of home screen widgets for tablet screens

    @@ -343,17 +480,25 @@ horizontal or square widget). possible. - - - - -

    Related resources:

    - -
    +
    +

    + Related resources +

    + + +

    7. Offer the app's full feature set to tablet users

    @@ -383,7 +528,8 @@ to a replacement feature (also see the section below on hardware features). -

    8. Don’t require hardware features that might not be available on tablets

    +

    8. Don’t require hardware features that might not be + available on tablets

    Handsets and tablets typically offer slightly different hardware support for sensors, camera, telephony, and other features. For example, many tablets are @@ -412,27 +558,46 @@ href="{@docRoot}guide/topics/manifest/permission-element.html"><permiss href="{@docRoot}guide/topics/manifest/uses-feature-element.html#permissions">imply feature requirements that might not be appropriate for tablets, except when accompanied by a corresponding <uses-feature> element -declared with the android:required=”false” attribute. +declared with the android:required=”false” attribute. +

    Here's an example of a dependency that's properly declared as "not required", so that +it does not limit distribution to devices that do not support the dependency:

    +

    <uses-feature android:name="android.hardware.telephony" +android:required="false" />

    In all cases, the app must function normally when the hardware features it -uses are not available and should offer “graceful degradation” and alternative +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.

    - - - - -

    Related resources:

    - -
    +
    +

    + Related resources +

    + +

    9. Declare support for tablet screen configurations

    @@ -442,77 +607,441 @@ declare all the screen sizes that your app supports in its manifest:

    - - - - -

    Related resources:

    -
      -
    • <supports-screens> -— Description and reference documentation for the <supports-screens> -manifest element.
      • -
    • Declaring Screen Size -Support — Developer documentation that explains the details of managing UI -for best display on multiple screen sizes.
      • +
      +

      + Related resources +

      + +
        +
      • + Basic Technical + Checks—Includes details (see TB-R4) on how + to properly declare screens support for tablet screen sizes. +
        • + +
      • + <supports-screens>—Description + and reference documentation for the <supports-screens> + manifest element. +
        • + +
      • + Declaring + Screen Size Support—Developer documentation that explains the + details of managing UI for best display on multiple screen sizes. +
        • +
      +
      + + +

      10. Showcase your tablet UI in Google Play

      + +

      + After you've done the work to create an 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. Capitalize on their interest by showing them screenshots of your + tablet UI on your app's store listing page. You can upload tablet screenshots + from the Developer Console. Here are some tips and guidelines: +

      + +
        +
      • Your screenshots should show the core functionality of your app, not a + startup or sign-in page. Wherever users will spend most of their time, that's + what you should show in your screenshots. +
        • + +
      • Add screenshots taken on both 7-inch and 10-inch tablets, if possible. +
        • + +
      • It's recommended that you add screenshots taken in both landscape and + portrait orientations, if possible. +
        • + +
      • Use screen captures if possible. Avoid showing actual device hardware in your + screenshots.
        • + +
      • The recommended resolution of your tablet screenshots is 1280 x 720 + or higher in each orientation. +
        • + +
      • You can upload as many as 8 screenshots of your tablet UI for 7-inch tablets + and an additional 8 for 10-inch tablets. +
      -
    +
    + Update your app description and release notes +
    + + -

    10. Follow best practices for publishing in Google Play

    +
    + 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: +