3. Test for Core App Quality
- -Before you publish an app on Google Play, it's important to make sure that -it meets the basic quality expectations for all Android apps, on all of the devices that you -are targeting. You can check your app's quality by setting up a test -environment and testing the app against a short set of core app quality criteria. -For complete information, see the Core App Quality Guidelines. -
- -If your app is targeting tablet devices, make sure that it delivers a rich, compelling -experience to your tablet customers. See the Tablet App Quality Checklist -for recommendations on ways to optimize your app for tablets.
- -Related resources: -
|
-
4. Determine your app's content rating
+3. Determine your app's content rating
Google Play requires you to set a content rating for your app, which informs Google Play users of its maturity level. Before you publish, you should confirm @@ -148,7 +115,7 @@ are required in your app binary.
-5. Determine country distribution
+4. Determine country distribution
Google Play lets you control what countries and territories your app is distributed to. For widest reach and the largest potential customer base, you @@ -182,7 +149,7 @@ launch target date.
-6. Confirm the app's overall size
+5. Confirm the app's overall size
The overall size of your app can affect its design and how you publish it on Google Play. Currently, the maximum size for an APK published on Google Play is @@ -213,7 +180,7 @@ creating your release-ready APK.
-7. Confirm the app's platform and screen compatibility ranges
+6. Confirm the app's platform and screen compatibility ranges
Before publishing, it's important to make sure that your app is designed to run properly on the Android platform versions and device screen sizes that you @@ -250,7 +217,7 @@ charts.
-8. Decide whether your app will be free or priced
+7. Decide whether your app will be free or priced
On Google Play, you can publish apps as free to download or priced. Free apps can be downloaded by any Android user in Google Play. @@ -282,7 +249,7 @@ you need set up a Checkout Merchant Account before you can publish.
-9. Consider using In-app Billing
+8. Consider using In-app Billing
Google Play In-app Billing lets you sell digital content in your applications. You can use the @@ -308,7 +275,7 @@ before creating your release-ready APK.
-10. Set prices for your products
+9. Set prices for your products
If your app is priced or you will sell in-app products, Google Play lets you set prices for your products in a variety of currencies, for users in markets @@ -341,7 +308,7 @@ in all available currencies through the Developer Console.
-11. Start localization
+10. Start localization
With your country targeting in mind, it's a good idea to assess your localization needs and start the work of localizing well in advance of your target @@ -377,7 +344,7 @@ when you upload assets and configure your product details.
-12. Prepare promotional graphics
+11. Prepare promotional graphics
When you publish on Google Play, you can supply a variety of high-quality graphic assets to showcase your app or brand. After you publish, these appear on @@ -408,7 +375,7 @@ advance of your target publishing date.
-13. Build and upload the release-ready APK
+12. Build and upload the release-ready APK
When you are satisfied that your app meets your UI, compatibility, and quality requirements, you can build the release-ready version of the app. The @@ -440,7 +407,7 @@ recent version before publishing.
-14. Complete the app's product details
+13. Complete the app's product details
On Google Play, your app's product information is shown to users on its product details page, the page that users visit to learn more about your app and @@ -464,10 +431,6 @@ page in the Developer Console. As you collect the information and assets for the page, make sure that you can enter or upload it to the Developer Console, until the page is complete and ready for publishing.
-If your app is targeting tablet devices, make sure to include at least one screen -shot of the app running on a tablet, and highlight your app's support for tablets -in the app description, release notes, promotional campaigns, and elsewhere.
-Related resources: @@ -481,7 +444,7 @@ in the app description, release notes, promotional campaigns, and elsewhere. |
15. Use Google Play badges and links in your promotional
+14. Use Google Play badges and links in your promotional
campaigns
Google Play badges give you an officially branded way of promoting your app @@ -510,7 +473,7 @@ and reviews, or any other channel available.
-16. Final checks and publishing
+15. Final checks and publishing
When you think you are ready to publish, sign in to the Developer Console and take a few moments for a few final checks:
@@ -548,7 +511,7 @@ final checks: -17. Support users after launch
+16. Support users after launch
After you publish an app or an app update, it's crucial for you to support your customers. Prompt and courteous support can provide a better experience for diff --git a/docs/html/distribute/googleplay/quality/core.jd b/docs/html/distribute/googleplay/quality/core.jd deleted file mode 100644 index 3d017e64b9a5a..0000000000000 --- a/docs/html/distribute/googleplay/quality/core.jd +++ /dev/null @@ -1,783 +0,0 @@ -page.title=Core App Quality Guidelines -@jd:body - -
Quality Criteria
- - -Testing
- - -You Should Also Read
- - - -App quality directly influences the long-term success of your app -— in terms of installs, user rating and reviews, engagement, and user -retention. Android users expect high quality design and performance from apps, -even more so if they puchased the apps or purchased their in-app products.
- -This document helps you assess basic aspects of quality in your app through a -compact set of core app quality criteria and associated tests. All -Android apps should meet these criteria.
- -Before launching your app, make sure to test it against these criteria to -ensure that it functions well on many devices, meets Android standards for -navigation and design, and is prepared for promotional opportunities in the -Google Play Store. Your testing will go well beyond what's described here -— the purpose of this document is to specify the essential characteristics -of basic quality so that you can include them in your test plans.
- -If your app is targeting tablet devices, make sure that it delivers a rich, -compelling experience to your tablet customers. See the Tablet App Quality -Checklist for recommendations on ways to optimize your app for tablets.
- - -Visual Design and User Interaction
- -These criteria ensure that your app provides standard Android visual design -and interaction patterns where appropriate, for a consistent and intuitive -user experience.
- -| - Area - | -- ID - | - - -- Description - | -- Tests - | -
|---|---|---|---|
| Standard design | -- UX-B1 - | -
- App follows Android Design guidelines and uses common UI patterns and icons: -
|
- CR-all | -
| Navigation | -- UX-N1 - | - -
- App supports standard system Back button navigation and does not make use of any custom, on-screen "Back button" prompts. - |
- CR-3 | -
| - UX-N2 - | -
- All dialogs are dismissable using the Back button. - |
- CR-3 | -|
| - UX-N3 - | -- Pressing the Home button at any point navigates to the Home screen of the device. - | -CR-1 | -
Related resources: -
|
-
Functionality
- -These criteria ensure that your app provides expected functional behavior with the appropriate level of permissions.
- -| - Area - | -- ID - | - - -- Description - | -- Tests - | -
|---|---|---|---|
| Permissions | -- FN-P1 - | -App requests only the absolute minimum permissions that it needs to support core functionality. - | -CR-11 | -
| - FN-P2 - | -App does not request permissions to access sensitive data (such as Contacts or the System Log) or services that can cost the user money (such as the Dialer or SMS), unless related to a core capability of the app. - |
- ||
| Install location | -- FN-L1 - | -
- App functions normally when installed on SD card (if supported by app). - -Supporting installation to SD card is recommended for most large apps (10MB+). See the App Install Location developer guide for information about which types of apps should support installation to SD card. - |
-
- SD-1 - | -
| Audio | -- FN-A1 - | - -- Audio does not play when the screen is off, unless this is a core feature (for example, the app is a music player). - | -CR-7 | -
| - FN-A2 - | -- Audio does not play behind the lock screen, unless this is a core feature. - | -CR-8 | -|
| - FN-A3 - | -- Audio does not play on the home screen or over another app, unless this is a core feature. - | -CR-1, CR-2 |
- |
| - FN-A4 - | -- Audio resumes when the app returns to the foreground, or indicates to the user that playback is in a paused state. - | -CR-1, CR-8 | -|
| UI and Graphics | -- FN-U1 - | - -
- App supports both landscape and portrait orientations (if possible). - -Orientations expose largely the same features and actions and preserve functional parity. - Minor changes in content or views are acceptable. - |
- CR-5 | -
| - FN-U2 - | - -
- App uses the whole screen in both orientations and does not letterbox to account for orientation changes. -Minor letterboxing to compensate for small variations in screen geometry is acceptable. - |
- CR-5 | -|
| - FN-U3 - | -
- App correctly handles rapid transitions between display orientations without rendering problems. - |
- CR-5 | -|
| User/app state | -- FN-S1 - | -
- App should not leave any services running when the app is in the background, unless related to a core capability of the app. -For example, the app should not leave services running to maintain a network connection for notifications, to maintain a Bluetooth connection, or to keep the GPS powered-on. - |
- CR-6 | -
| - FN-S2 - | -
- App correctly preserves and restores user or app state. -App preserves user or app state when leaving the foreground and prevents accidental data loss due to back-navigation and other state changes. When returning to the foreground, the app must restore the preserved state and any significant stateful transaction that was pending, such as changes to editable fields, game progress, menus, videos, and other sections of the app or game. -
|
- CR-1, CR-3, CR-5 | -
Related resources: -
|
-
Performance and Stability
- -To ensure a high user rating, your app needs to perform well and stay -responsive on all of the devices and form factors and screens that it is -targeting. These criteria ensure that the app provides the basic performance, -stability, and responsiveness expected by users.
- -| - Area - | -- ID - | -- Description - | -- Tests - | -
|---|---|---|---|
| Stability | -- PS-S1 - | -- App does not crash, force close, freeze, or otherwise function abnormally on any targeted device. - | -CR-all, SD-1, HA-1 | -
| Performance | -- PS-P1 - | -- App loads quickly or provides onscreen feedback to the user (a progress indicator or similar cue) if the app - takes longer than two seconds to load. - | -- CR-all, SD-1 - | -
| - PS-P2 - | -- With StrictMode enabled (see StrictMode Testing, below), no red flashes (performance warnings from StrictMode) are visible when exercising the app, including - during game play, animations and UI transitions, and any other part of the app. - | -- PM-1 - | -|
| Media | -- PS-M1 - | -- Music and video playback is smooth, without crackle, stutter, or other artifacts, during normal app usage and load. - | -- CR-all, SD-1, HA-1 - | -
| Visual quality | -- PS-V1 - | -
- App displays graphics, text, images, and other UI elements without noticeable distortion, blurring, or pixelation. - -
|
- CR-all | -
| - PS-V2 - | -
- App displays text and text blocks in an acceptable manner. - -
|
-
-
Related resources: -
|
-
Google Play
- -To launch your app successfully on Google Play, raise its ratings, and make -sure that it is ready for promotional activities in the store, follow the -criteria below.
- -| - Area - | -- ID - | -- Description - | -- Tests - | -
|---|---|---|---|
| Policies | -- GP-P1 - | -- App strictly adheres to the terms of the Google Play Developer Content Policy and does not offer inappropriate content, does not use intellectual property or brand of others, and so on. - | -- GP-all - | -
| - GP-P2 - | -
- App maturity level is set appropriately, based on the - Content Rating Guidelines. - -Especially, note that apps that request permission to use the device location cannot be given the maturity level "Everyone". - |
- - GP-1 - | -|
| App Details Page | -- GP-D1 - | -
- App feature graphic follows the guidelines outlined in this - blog post. Make sure that: - -
|
-
- - GP-1, GP-2 - | - - -
| - GP-D2 - | -- App screenshots and videos do not show or reference non-Android devices. - | -GP-1 | -|
| - GP-D3 - | -- App screenshots or videos do not - represent the content and experience of your app in a misleading way. - | -||
| User Support | -- GP-X1 - | -Common user-reported bugs in the Reviews tab of the Google Play page are addressed if they are - reproducible and occur on many different devices. If a bug occurs on only a few devices, - you should still address it if those devices are particularly popular or new. - | - -- GP-1 - | - -
Related resources: -
|
Setting Up a Test Environment
- -To assess the quality of your app, you need to set up a suitable -hardware or emulator environment for testing.
- -The ideal test environment would -include a small number of actual hardware devices that represent key form -factors and hardware/software combinations currently available to consumers. -It's not necessary to test on every device that's on the market — -rather, you should focus on a small number of representative devices, even using -one or two devices per form factor.
- -If you are not able to obtain actual hardware devices for testing, you should -set up emulated devices (AVDs) to represent the most common form factors and -hardware/software combinations.
- -To go beyond basic testing, you can add more devices, more form factors, or -new hardware/software combinations to your test environment. You can also -increase the number or complexity of tests and quality criteria.
- - -- Test Procedures -
- -These test procedures help you discover various types of quality issues in your app. You can combine the tests or integrate groups of tests together in your own test plans. See the sections above for references that associate specific criteria with specific tests.
- -| - Type - | -- Test - | -- Description - | -
|---|---|---|
| Core Suite | -- CR-0 - | -Navigate to all parts of the app — all screens, dialogs, settings, and all user flows. - -
|
-
| - CR-1 - | -From each app screen, press the device's Home key, then re-launch the app from the All Apps screen. - | -|
| - CR-2 - | -From each app screen, switch to another running app and then return to the app under test using the Recents app switcher. - | -|
| - CR-3 - | -From each app screen (and dialogs), press the Back button. - | -|
| - CR-5 - | -From each app screen, rotate the device between landscape and portrait orientation at least three times. - | -|
| - CR-6 - | -Switch to another app to send the test app into the background. Go to Settings and check whether the test app has any services running while in the background. In Android 4.0 and higher, go to the Apps screen and find the app in the "Running" tab. In earlier versions, use "Manage Applications" to check for running services. - | -|
| - CR-7 - | -- Press the power button to put the device to sleep, then press the power button again to - awaken the screen. - | -|
| - CR-8 - | -- Set the device to lock when the power button is pressed. Press the power button to put the device to sleep, then press the power button again to - awaken the screen, then unlock the device. - | -|
| - CR-9 - | -- For devices that have slide-out keyboards, slide the keyboard in and out at least once. For devices that have keyboard docks, attach the device to the keyboard dock. - | -|
| - CR-10 - | -- For devices that have an external display port, plug-in the external display. - | -|
| - CR-11 - | -Examine the permissions requested by the app by going to Settings > App Info. - | -|
| Install on SD Card | -- SD-1 - | -
- Repeat Core Suite with app installed to device SD card (if supported by app). - -To move the app to SD card, you can use Settings > App Info > Move to SD Card. - |
-
| Hardware acceleration | -- HA-1 - | -
- Repeat Core Suite with hardware acceleration enabled. - -To force-enable hardware acceleration (where supported by device), add |
-
| Performance Monitoring | -- PM-1 - | -
- Repeat Core Suite with StrictMode profiling enabled as described below. Pay close attention to garbage collection and its impact on the user experience. - |
-
| Google Play | -- GP-1 - | -- Sign into the Developer Console to review your developer profile, app description, screenshots, feature graphic, maturity settings, and user feedback. - | -
| - GP-2 - | -- Download your feature graphic and screenshots and scale them down to match the display sizes on the devices and form factors you are targeting. - | -|
| - GP-4 - | -- Review all graphical assets, media, text, code libraries, and other content packaged in the app or expansion file download. - | -|
| Payments | -- GP-5 - | -- Navigate to all screens of your app and enter all in-app purchase flows. - | -
-Testing with StrictMode -
- -For performance testing, we recommend enabling StrictMode in your app and using it to catch operations on the main thread and other threads that could affect performance, network accesses, file reads/writes, and so on.
-
-You can set up a monitoring policy per thread using the ThreadPolicy builder and enable all supported monitoring in the ThreadPolicy using detectAll().
Make sure to enable visual notification of policy violations for the ThreadPolicy using penaltyFlashScreen().
App quality directly influences the long-term success of your app -— in terms of installs, user rating and reviews, engagement, and user -retention. Android users expect high quality from apps, even more so if they -puchased the apps or purchased their in-app products. At the same time, they -enjoy and value apps that put a priority on high quality and continuous -improvement.
- -Before you publish an app on Google Play, it's important to make sure that -the app meets the basic quality expectations of users, across all of the form -factors and device types that the app is targeting. The documents in this -section help you assess your app's fundamental quality and they provide -resources to help you address issues that you find.
- -- Core App Quality -
-- A set of core quality criteria that all Android apps should meet on all targeted devices. -
Learn more » -- Tablet App Quality -
-- A set recommendations for delivering the best possible experience to tablet users. -
Learn more » -- Improving App Quality -
-- Tips on continuously improving your app's quality, ratings, reviews, downloads, and engagement. -
Learn more - » -Checklist
--
-
-
- 1. Test for Core App Quality -
- 2. Optimize your layouts -
- 3. Use the extra screen area -
- 4. Use assets designed for tablets -
- 5. Adjust fonts and touch targets -
- 6. Adjust homescreen widgets -
- 7. Offer the app's full feature set -
- 8. Don’t require hardware features -
- 9. Declare tablet screen support -
- 10. Follow best practices for publishing in Google Play - -
Testing
- -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.
- -Tablets are a growing part of the Android installed base that offers new -opportunities for user engagement -and monetization. If your app is targeting tablet users, this document helps -you focus on key aspects of quality, feature set, and UI that can have a -significant impact on the app's success. Each focus area is given as checklist -item, with each one comprising several smaller tasks or best practices.
- -Although the checklist tasks below are numbered for convenience, -you can handle them in any order and address them to the extent that you feel -is right for your app. In the interest of delivering the best possible product -to your customers, follow the checklist recommendations -to the greatest extent possible.
- -As you move through the checklist, you'll find links to support resources -that can help you address the topics raised in each task.
- - -1. Test for 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. -
- -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.
- - -2. Optimize your 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 available, such as to 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 "stretched UI" with an -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.
--
-
- Provide custom layouts as needed for
largeand -xlargescreens. You can also provide layouts that are loaded based -on the screen's shortest -dimension or the minimum -available width and height.
- - At a minimum, customize dimensions such as font sizes, margins, spacing for -larger screens, to improve use of space and content legibility. -
- Adjust positioning of UI controls so that they are easily accessible to -users when holding a tablet, such as toward the sides when in -landscape orientation. -
- Padding of UI elements should normally be larger on tablets than on handsets. A -48dp rhythm (and a 16dp -grid) is recommended. -
- Adequately pad text content so that it is not aligned directly along screen edges.
-Use a minimum
16dppadding around content near screen edges.
-
In particular, make sure that your layouts do not appear "stretched" -across the screen:
- --
-
- Lines of text should not be excessively long — optimize for a maximum -100 characters per line, with best results between 50 and 75. -
- ListViews and menus should not use the full screen width. -
- Use padding to manage the widths of onscreen elements or switch to a -multi-pane UI for tablets (see next section). -
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.
-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 -is taking full advantage of extra screen area available on tablets. Here are -some suggestions:
- --
-
- Look for opportunities to include additional content or use an alternative -treatment of existing content. -
- Use multi-pane -layouts on tablet screens to combine single views into a compound view. This -lets you use the additional screen area more efficiently and makes it easier for -users to navigate your app. -
- Plan how you want the panels of your compound views to reorganize when -screen orientation changes. - - - -
- 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. -
- 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).
-
-
-Compound views combine several single views from a handset UI (above) into a richer, more efficient UI for tablets (below).
-Related resources: -
|
-
4. Use Icons and other assets that are designed for tablet screens
- -So that your app looks its best, make sure to use icons and other bitmap -assets that are created specifically for the densities used by tablet screens. -Specifically, you should create sets of alternative bitmap drawables for each -density in the range commonly supported by tablets.
- -Raw asset sizes for icon types.
| Density | -Launcher | -Action Bar | -Small/Contextual | -Notification | -
|---|---|---|---|---|
mdpi |
-48x48px | -32x32px | -16x16px | -24x24px | -
hdpi |
-72x72px | -48x48px | -24x24px | -36x36px | -
tvdpi |
-(use hdpi) | -(use hdpi) | -(use hdpi) | -(use hdpi) | -
xhdpi |
-96x96px | -64x64px | -32x32px | -48x48px | -
Other points to consider:
- --
-
- Icons in the action bar, notifications, and launcher should be designed -according to the icon design guidelines and have the same physical size on -tablets as on phones. -
- Use density-specific -resource qualifiers to ensure that the proper set of alternative resources -gets loaded. -
Related resources: -
|
-
5. Adjust font sizes and touch targets for tablet screens
- -To make sure your app is easy to use on tablets, take some time to adjust the -font sizes and touch targets in your tablet UI, for all of the screen -configurations you are 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:
--
-
- Text should not be excessively large or small on tablet screen sizes and -densities. Make sure that labels are sized appropriately for the UI elements they -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 -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. -
Related resources: -
|
-
6. Adjust sizes of home screen widgets for tablet screens
- -If your app includes a home screen widget, here are a few points to consider -to ensure a great user experience on tablet screens:
- --
-
- Make sure that the widget's default height and width are set appropriately -for tablet screens, as well as the minimum and maximum resize height and width. - -
- The widget should be resizable to 420dp or more, to span 5 or more home -screen rows (if this is a vertical or square widget) or columns (if this is a -horizontal or square widget). -
- Make sure that 9-patch images render correctly. -
- Use default system margins. -
- Set the app's
targetSdkVersionto 14 or higher, if -possible.
-
Related resources: -
|
-
7. Offer the app's full feature set to tablet users
- -Let your tablet users experience the best features of your app. Here are -some recommendations:
- --
-
- Design your app to offer at least the same set of features on tablets as it does on -handsets. -
- In exceptional cases, your app might omit or replace certain features on
-tablets if they are not supported by the hardware or use-case of most tablets.
-For example:
-
-
-
- If the handset uses telephony features but telephony is not available on the -current tablet, you can omit or replace the related functionality. -
- Many tablets have a GPS sensor, but most users would not normally carry -their tablets while running. If your phone app provides functionality to let the -user record a GPS track of their runs while carrying their phones, the app would not need to -provide that functionality on tablets because the use-case is not -compelling. -
- - If you will omit a feature or capability from your tablet UI, make sure -that it is not accessible to users or that it offers “graceful degradation” -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
- -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.
- -To ensure that you can deliver a single APK broadly across the -your full customer base, make sure that your app does not have built-in -requirements for hardware features that aren't commonly available on tablets. -
- --
-
- Your app's manifest should not include
<uses-feature>-elements for hardware features or capabilities that might not be -available on tablets, except when they are declared with the -android:required=”false”attribute. For example, your app should -not require features such as: --
-
android.hardware.telephony
-android.hardware.camera(refers to back camera), or
-android.hardware.camera.front
-
- - Similarly, your app manifest should not include any
<permission>elements that imply -feature requirements that might not be appropriate for tablets, except when -accompanied by a corresponding<uses-feature>element -declared with theandroid:required=”false”attribute.
-
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.
- -Related resources: -
|
-
9. Declare support for tablet screen configurations
- -To ensure that you can distribute your app to a broad range of tablets, -declare all the screen sizes that your app supports in its manifest:
- --
-
- Declare a
<supports-screens>element -with appropriate attributes, as needed.
- - If the app declares a
<compatible-screens>element in the -manifest, the element must 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 this element in your app.
-
Related resources: -
|
-
10. Follow best practices for publishing in Google Play
- --
-
- Publish your app as a single APK for all screen sizes (handsets
-and tablets), with a single Google Play listing:
-
-
-
- Easier for users to find your app from search, browsing, or promotions -
- Easier for users to restore your app automatically if they get a new device. -
- Your ratings and download stats are consolidated across all devices. -
- Publishing a tablet app in a second listing can dilute ratings for your brand. -
- - 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. - -
- Highlight your app’s tablet capabilities in the product details page:
-
-
-
- Add at least one screenshot taken while the app is running on a - tablet. It's recommended that you add one screenshot of landscape orientation - and one of portrait orientation, if possible. These screenshots make it clear to users - that your app is designed for tablets and highlight all the effort you've put into designing - a great tablet app experience. -
- Mention tablet support in the app description. -
- Include information about tablet support in the app's release notes and update - information. -
- In your app's promo video, add shots of your app running on a tablet. -
- - Make sure you are distributing to tablet devices. Check the app's Supported Devices -list in the Developer Console -to make sure your app is not filtered from tablet devices that you want to target. - -
- Let tablet users know about your app! Plan a marketing or advertising campaign that -highlights the use of your app on tablets. -
Related resources: -
|
-
Setting Up a Test Environment for Tablets
- -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.
- -The ideal test environment would -include a small number of actual hardware devices that represent key form -factors and hardware/software combinations currently available to consumers. -It's not necessary to test on every device that's on the market — -rather, you should focus on a small number of representative devices, even using -one or two devices per form factor. The table below provides an overview of -devices you could use for testing.
- -If you are not able to obtain actual hardware devices for testing, you should -set up emulated devices (AVDs) to represent the most common form factors and -hardware/software combinations. See the table below for suggestions on the emulator -configurations to use.
- -To go beyond basic testing, you can add more devices, more form factors, or -new hardware/software combinations to your test environment. For example, you -could include mid-size tablets, tablets with more or fewer hardware/software -features, and so on. You can also increase the number or complexity of tests -and quality criteria.
- -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 chipsets, platform versions, and hardware feature configurations.
- -| Type | -Size | -Density | -Version | -AVD Skin | -
|---|---|---|---|---|
| 7-inch tablet | -large or-sw600 |
-hdpi,tvdpi |
-Android 4.0+ | -WXGA800-7in | -
| 10-inch tablet | -xlarge or-sw800 |
-mdpi,hdpi |
-Android 3.2+ | -WXGA800 | -
Android developers, their apps, and their successes with Android and Google Play.
- - - -Developer Story: Robot Invader
-Robot Invader chose
- Android and Google Play as the launch platform for their first game,
- Wind-up
- Knight.
-
- Hear from the developers how Android helped them reach millions of users - and more than 100 device models with a single app binary, then iterate rapidly to ensure - a great user experience. -
-More and more, developers are investing in a full tablet experience -for their apps and are seeing those investments pay off big. The increased -screen area on tablets opens up a world of possibilities, allowing for more -engagement with the user — which can mean an increase in usage as well as -more monetization opportunities. And with the growing wave of Android tablets that -continue to hit the market, it’s an important piece of any developer’s mobile -offering.
- -Here are some stories from developers who are seeing real results as they -expand their offering to include Android tablets.
- - -Mint: More screen real estate = more engagement
- -About the app
- - --
-
- Mint.com Personal Finance by Intuit Inc. -
- Financial management app targeting 7- to 10-inch tablets -
Tablet Results
- --
-
- Able to offer richer UI features -
- Much higher user engagement -
- Longer sessions — more Android tablet users have sessions longer than 5 minutes -
-
-
- When Intuit was thinking about -expanding their Mint mobile offering to include a version optimized for Android -tablets, they knew that taking the layout that worked for phones and simply -showing an enlarged version wouldn’t take full advantage of the opportunities -that tablets afford.
- -“We knew we had a lot more real estate, and we wanted to provide a more -immersive experience for our users” said Ken Sun, Intuit Group Product Manager -at Mint.
- -Intuit’s Mint app, which has a 4-star rating on Google Play, brings a number -of features to Android tablets that aren’t available for phones, including a -more visual presentation of personal financial data.
- -“Whereas our app for phones is used throughout the day for quick sessions, -we’ve seen a larger percentage of our tablet usage happen in the evening, for -much longer sessions,” said Sun. “People are doing a lot more than just checking -their spending. They’re looking at historical trends, re-categorizing -transactions, analyzing the data and setting financial goals for the future -— digging much deeper and being more thoughtful. One example is how much -users are interacting with their own budgets in the tablet app. Customer budget -operations (view, edit, drill-down, etc.) are 7x higher on Android tablets than -they are on phones.”
- -Fifty percent more Android tablet users have Mint sessions of 5 minutes or -longer than they do on phones. “We’ve found that phone usage is indicative of a -customer’s regular financial check-in, while tablet usage points towards more -analysis and interaction with that customer’s personal financial data. This is -the sort of immersive engagement experience we were looking for; the tablet and -phone apps serve as great complements to each other."
-
-
- Making the most of tablet screens: Mint used the extra screen area on tablets to offer quick access to additional tools and information.
-TinyCo: Monetization opportunities abound on tablets
- -About the app
- --
-
- Tiny Village by TinyCo -
- Game targeting 7- to 10-inch tablets and phones -
Tablet Results
- --
-
- 35% higher average revenue per paying user (ARPPU) -
- Consistent increase in user retention -
- 3x increase in downloads to Android tablets in the last 6 months -
-
-
- Over a year ago, developer -TinyCo, makers of games such as Tiny Monsters, switched to a -simultaneous launch strategy for their products. They chose Android as one of their -primary launch platforms because of its large installed base and global reach. They -also knew that the growing base of Android tablet users represented a huge -opportunity.
- -Tiny Village was their first title to take advantage of the strategy, and -it proved to be a winning one — especially in terms of Android -tablets.
- -“With continued optimization of the gameplay experience and a genuine -commitment to our Android offering through our Griffin engine, all of our -metrics started to rise,” said Rajeev Nagpal, Head of Product at TinyCo. In -fact, they’ve seen Android tablet downloads more than triple in the last six -months.
- -One of the first things they noticed about usage of Tiny Village on -tablets was an increase in average revenue per paying user (ARPPU)—about 35% -higher than on smaller-screen devices such as phones. Additionally, average -revenue per user ARPU is now about 35% higher as well. “The game is just much -more immersive on tablet.”
- -In addition to an increase in monetization metrics, they’ve also seen a -consistent increase in retention over other platforms. “These are really -important metrics for games — if you can get users to both stay around -longer and spend more while they’re there, you have a recipe for success.”
-
-
- More monetization -on tablets: On Android tablets TinyCo has seen higher ARPPU and user -retention than on phones.
-Instapaper: Riding the growing wave of Android tablets
- - -About the app
--
-
- Instapaper by Mobelux -
- Content-browsing utility that targets 7- to 10-inch tablets and phones -
Tablet Results
- --
-
- Tablets are now 50% of the app's installed base. -
-
-
- Instapaper for Android is an app -for saving web content to read later. Developer Mobelux decided that creating a -great UI for Android tablet users would be an essential part of their initial launch -plan.
- -The app launched at the beginning of the summer of 2012, just in time to -take advantage of a new tide of Android tablets, including the Nexus 7 tablet. The app has since seen huge -popularity among tablet users, in particular, on Nexus 7. On the day that -pre-orders of Nexus 7 began arriving, Mobelux saw a 600% jump in downloads of -its app on Google Play.
- -“We saw a promising new set of Android tablets about to hit the market -and wanted to position ourselves to be ready for them” said Jeff Rock of -Mobelux. “It was a market that others were hesitant to explore, but the decision -to prioritize tablets has paid off very well for us.”
- -Since that initial 600% jump in downloads, Instapaper for Android has -continued to see a successful run on Android tablets. In fact, Android tablets -now represent about 50% of their installed base. “With more and more Android -tablets coming online, we’re excited to see how our investment in Android -tablets continues to pay off.”
-
-
- Popular with -tablet users: A great tablet UI and browsing convenience make Instapaper -popular with Android tablet users.
-Strategies
--
+
- Listen to Your Users
- Improve Stability and Eliminate Bugs
- Improve UI Responsiveness @@ -13,14 +13,7 @@ page.title=Improving App Quality After Launch
- Deliver the Right Set of Features
- Integrate with the System and Third-Party Apps
- Pay Attention to Details -
Strategies:
+You Should Also Read
- - +A better app can go a very long way: a higher quality app will translate to higher user ratings, generally better rankings, more downloads, and higher retention (longer install periods). High-quality apps also have a much higher likelihood of getting some unanticipated positive publicity such as being featured in Google Play or getting social media buzz.
-The upside to having a higher-quality app is obvious. However, it's not always clear how to make an app "better". This document looks at some of the key factors in app quality and ways of improving your app over time, after you've launched the app.
+The upside to having a higher-quality app is obvious. However, it's not always clear how to make an app "better". The path to improving app quality isn't always well-lit. The term "quality" — along with "polish" and "fit and finish" — aren't always well-defined. Here we'll light the path by looking at some of the key factors in app quality and ways of improving your app along these dimensions.Listen to Your Users
@@ -59,14 +52,15 @@ One sure-fire way to lose your users is to give them a slow, unresponsive UI. Re
You can improve your apps's UI responsiveness by moving long-running operations off the main thread to worker threads. Android offers built-in debugging facilities such as StrictMode for analyzing your app's performance and activities on the main thread. You can see more recommendations in Writing Zippy Android Apps, a developer session from Google I/O 2010,
+More resources
+More resources
In usability and in app design too, you should listen carefully to your users. Ask a handful of real Android device users (friends, family, etc.) to try out your app and observe them as they interact with it. Look for cases where they get confused, are unsure of how to proceed, or are surprised by certain behaviors. Minimize these cases by rethinking some of the interactions in your app, perhaps working in some of the user interface patterns the Android UI team discussed at Google I/O.
++In the same vein, two problems that can plague some Android user interfaces are small tap targets and excessively small font sizes. These are generally easy to fix and can make a big impact on usability and user satisfaction. As a general rule, optimize for ease of use and legibility, while minimizing, or at least carefully balancing, information density.
-As you are designing or evaluating your app's UI, make sure to read and become familiar with the Android Design guidelines. Included are many examples of UI patterns, styles, and building blocks, as well as tools for the design process.
+More resources
+-
+As you are designing or evaluating your app's UI, make sure to read and become familiar with the Android Design guidelines. Included are many examples of UI patterns, styles, and building blocks, as well as tools for the design process.
+
-In the same vein, two problems that can plague some Android user interfaces are small tap targets and excessively small font sizes. These are generally easy to fix and can make a big impact on usability and user satisfaction. As a general rule, optimize for ease of use and legibility, while minimizing, or at least carefully balancing, information density.
-Another way to incrementally improve usability, based on real-world data, is to implement Analytics throughout your app to log usage of particular sections. Consider demoting infrequently used sections to the overflow menu in the Action bar, or removing them altogether. For often-used sections and UI elements, make sure they're immediately obvious and easily accessible in your app's UI so that users can get to them quickly.
diff --git a/docs/html/images/distribute/instapaper.png b/docs/html/images/distribute/instapaper.png deleted file mode 100644 index ffbf052952394..0000000000000 Binary files a/docs/html/images/distribute/instapaper.png and /dev/null differ diff --git a/docs/html/images/distribute/mint.png b/docs/html/images/distribute/mint.png deleted file mode 100644 index 50d90d5bf82d5..0000000000000 Binary files a/docs/html/images/distribute/mint.png and /dev/null differ diff --git a/docs/html/images/distribute/tinyvillage.png b/docs/html/images/distribute/tinyvillage.png deleted file mode 100644 index cde77f09a66ba..0000000000000 Binary files a/docs/html/images/distribute/tinyvillage.png and /dev/null differ diff --git a/docs/html/images/ui-ex-multi-pane.png b/docs/html/images/ui-ex-multi-pane.png deleted file mode 100644 index 188bb8bc116e1..0000000000000 Binary files a/docs/html/images/ui-ex-multi-pane.png and /dev/null differ diff --git a/docs/html/images/ui-ex-single-panes.png b/docs/html/images/ui-ex-single-panes.png deleted file mode 100644 index dff24a707b928..0000000000000 Binary files a/docs/html/images/ui-ex-single-panes.png and /dev/null differ