Doc change: Add core quality and tablet quality docs and spotlight. (9aeb0a81) · Commits · e / os / android_frameworks_base

docs/html/distribute/distribute_toc.cs

+27 −9

Original line number	Diff line number	Diff line
		@@ -28,9 +28,7 @@
		<li><a href="<?cs var:toroot ?>distribute/googleplay/publish/preparing.html">
		<span class="en">Publishing Checklist</span>
		</a></li>
		<li><a href="<?cs var:toroot ?>distribute/googleplay/strategies/app-quality.html">
		<span class="en">App Quality</span>
		</a></li>

		</ul>
		</li>

		@@ -79,6 +77,26 @@
		</ul>
		</li>


		<li class="nav-section">
		<div class="nav-section-header"><a href="<?cs var:toroot ?>distribute/googleplay/quality/index.html">
		<span class="en">App Quality</span></a>
		</div>
		<ul>
		<li><a href="<?cs var:toroot ?>distribute/googleplay/quality/core.html">
		<span class="en">Core App Quality</span>
		</a></li>
		<li><a href="<?cs var:toroot ?>distribute/googleplay/quality/tablet.html">
		<span class="en">Tablet App Quality</span>
		</a></li>
		<li><a href="<?cs var:toroot ?>distribute/googleplay/strategies/app-quality.html">
		<span class="en">Improving App Quality</span>
		</a></li>

		</ul>
		</li>


		<!--
		<li class="nav-section">
		<div class="nav-section-header"><a href="<?cs var:toroot ?>distribute/googleplay/after.html">
		@@ -92,17 +110,17 @@
		</li>
		-->

		<!--
		<li class="nav-section">
		<div class="nav-section-header"><a href="<?cs var:toroot ?>distribute/googleplay/strategies/index.html">
		<span class="en">Strategies</span></a>
		<div class="nav-section-header"><a href="<?cs var:toroot ?>distribute/googleplay/spotlight/index.html">
		<span class="en">Spotlight</span></a>
		</div>
		<ul>
		<li><a href="<?cs var:toroot ?>distribute/googleplay/strategies/featuring.html">Featuring</a></li>
		<li><a href="<?cs var:toroot ?>distribute/googleplay/strategies/app-quality.html">App Quality</a></li>
		<li><a href="<?cs var:toroot ?>distribute/googleplay/spotlight/tablets.html">
		<span class="en">Tablet Stories</span>
		</a></li>
		</ul>
		</li>
		-->

		<li class="nav-section">
		<div class="nav-section-header empty">
		<a href="<?cs var:toroot ?>distribute/open.html">

docs/html/distribute/googleplay/about/monetizing.jd

+3 −2

Original line number	Diff line number	Diff line
		@@ -42,7 +42,7 @@ manages the application download.</p>
		<h3 id="payment-methods">Convenient payment options</h3>

		<p>Users can purchase your products on Google Play using several convenient
		payment methods—credit cards, Direct Carrier Billing, and Google Play balance.</p>
		payment methods—credit cards, Direct Carrier Billing, gift cards, and Google Play balance.</p>

		<p><span style="font-weight:500">Credit card</span> is the most common method of payment. Users can pay using any credit card
		that they’ve registered in Google Play. To make it easy for users to get started,
		@@ -52,8 +52,9 @@ registration is offered as a part of initial device setup process.</p>
		<div class="sidebox">
		<h2>Payment methods on Google Play</h2>
		<ul>
		<li>Credit Card</li>
		<li>Credit card</li>
		<li>Direct Carrier Billing</li>
		<li>Gift card</li>
		<li>Google Play balance (stored value)</li>
		</ul>
		</div>

docs/html/distribute/googleplay/publish/preparing.jd

+65 −28

Original line number	Diff line number	Diff line
		@@ -6,20 +6,21 @@ page.title=Publishing Checklist for Google Play
		<ol>
		<li><a href="#process">1. Understand the publishing process</a></li>
		<li><a href="#policies">2. Understand Google Play policies</a></li>
		<li><a href="#rating">3. Determine your content rating</a></li>
		<li><a href="#countries">4. Determine country distribution</a></li>
		<li><a href="#size">5. Confirm the app's overall size</a></li>
		<li><a href="#compatibility">6. Confirm app compatibility ranges</a></li>
		<li><a href="#free-priced">7. Decide on free or priced</a></li>
		<li><a href="#inapp-billing">8. Consider In-app Billing</a></li>
		<li><a href="#pricing">9. Set prices for your apps</a></li>
		<li><a href="#localize">10. Start localization</a></li>
		<li><a href="#localize">11. Prepare promotional graphics</a></li>
		<li><a href="#apk">12. Build the release-ready APK</a></li>
		<li><a href="#product-page">13. Complete the product details</a></li>
		<li><a href="#badges">14. Use Google Play badges and links to your promotional campaigns</a></li>
		<li><a href="#final-checks">15. Final checks and publishing</a></li>
		<li><a href="#support">16. Support users after launch</a></li>
		<li><a href="#core-app-quality">3. Test for Core App Quality</a></li>
		<li><a href="#rating">4. Determine your content rating</a></li>
		<li><a href="#countries">5. Determine country distribution</a></li>
		<li><a href="#size">6. Confirm the app's overall size</a></li>
		<li><a href="#compatibility">7. Confirm app compatibility ranges</a></li>
		<li><a href="#free-priced">8. Decide on free or priced</a></li>
		<li><a href="#inapp-billing">9. Consider In-app Billing</a></li>
		<li><a href="#pricing">10. Set prices for your apps</a></li>
		<li><a href="#localize">11. Start localization early</a></li>
		<li><a href="#localize">12. Prepare promotional graphics</a></li>
		<li><a href="#apk">13. Build the release-ready APK</a></li>
		<li><a href="#product-page">14. Complete the product details</a></li>
		<li><a href="#badges">15. Use Google Play badges</a></li>
		<li><a href="#final-checks">16. Final checks and publishing</a></li>
		<li><a href="#support">17. Support users after launch</a></li>
		</ol>
		</div></div>

		@@ -86,7 +87,39 @@ violations, termination of your developer account. </p>
		</tr>
		</table>

		<h2 id="rating">3. Determine your app's content rating</h2>
		<h2 id="core-app-quality">3. Test for Core App Quality</h2>

		<p>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 <strong>core app quality criteria</strong>.
		For complete information, see the <a
		href="{@docRoot}distribute/googleplay/quality/core.html">Core App Quality Guidelines</a>.
		</p>

		<p>If your app is targeting tablet devices, make sure that it delivers a rich, compelling
		experience to your tablet customers. See the <a
		href="{@docRoot}distribute/googleplay/quality/tablet.html">Tablet App Quality Checklist</a>
		for recommendations on ways to optimize your app for tablets.</p>

		<table>
		<tr>
		<td><p>Related resources:</p>
		<ul style="margin-top:-.5em;">
		<li><strong><a
		href="{@docRoot}distribute/googleplay/quality/core.html">Core App Quality
		Guidelines</a></strong> — A set of core quality criteria that all Android
		apps should meet on all targeted devices.</li>
		<li><strong><a
		href="{@docRoot}distribute/googleplay/quality/tablet.html">Tablet App Quality
		Checklist</a></strong> — A set recommendations for delivering the best
		possible experience to tablet users.</li>
		</ul>
		</td>
		</tr>
		</table>

		<h2 id="rating">4. Determine your app's content rating</h2>

		<p>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
		@@ -115,7 +148,7 @@ are required in your app binary.</p>
		</tr>
		</table>

		<h2 id="countries">4. Determine country distribution</h2>
		<h2 id="countries">5. Determine country distribution</h2>

		<p>Google Play lets you control what countries and territories your app is
		distributed to. For widest reach and the largest potential customer base, you
		@@ -149,7 +182,7 @@ launch target date.</p>
		</tr>
		</table>

		<h2 id="size">5. Confirm the app's overall size</h2>
		<h2 id="size">6. Confirm the app's overall size</h2>

		<p>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
		@@ -180,7 +213,7 @@ creating your release-ready APK.</p>
		</tr>
		</table>

		<h2 id="compatibility">6. Confirm the app's platform and screen compatibility ranges</h2>
		<h2 id="compatibility">7. Confirm the app's platform and screen compatibility ranges</h2>

		<p>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
		@@ -217,7 +250,7 @@ charts.</p>
		</tr>
		</table>

		<h2 id="free-priced">7. Decide whether your app will be free or priced</h2>
		<h2 id="free-priced">8. Decide whether your app will be free or priced</h2>

		<p>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.
		@@ -249,7 +282,7 @@ you need set up a Checkout Merchant Account before you can publish.</p>
		</tr>
		</table>

		<h2 id="inapp-billing">8. Consider using In-app Billing</h2>
		<h2 id="inapp-billing">9. Consider using In-app Billing</h2>

		<p>Google Play <a href="{@docRoot}guide/google/play/billing/index.html">In-app
		Billing</a> lets you sell digital content in your applications. You can use the
		@@ -275,7 +308,7 @@ before creating your release-ready APK.</p>
		</tr>
		</table>

		<h2 id="pricing">9. Set prices for your products</h2>
		<h2 id="pricing">10. Set prices for your products</h2>

		<p>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
		@@ -308,7 +341,7 @@ in all available currencies through the Developer Console.</p>
		</tr>
		</table>

		<h2 id="localize">10. Start localization</h2>
		<h2 id="localize">11. Start localization</h2>

		<p>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
		@@ -344,7 +377,7 @@ when you upload assets and configure your product details.</p>
		</tr>
		</table>

		<h2 id="graphics">11. Prepare promotional graphics</h2>
		<h2 id="graphics">12. Prepare promotional graphics</h2>

		<p>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
		@@ -375,7 +408,7 @@ advance of your target publishing date. </p>
		</tr>
		</table>

		<h2 id="apk">12. Build and upload the release-ready APK</h2>
		<h2 id="apk">13. Build and upload the release-ready APK</h2>

		<p>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
		@@ -407,7 +440,7 @@ recent version before publishing. </p>
		</tr>
		</table>

		<h2 id="product-page">13. Complete the app's product details</h2>
		<h2 id="product-page">14. Complete the app's product details</h2>

		<p>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
		@@ -431,6 +464,10 @@ 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. </p>

		<p>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.</p>

		<table>
		<tr>
		<td><p>Related resources:</p>
		@@ -444,7 +481,7 @@ the page is complete and ready for publishing. </p>
		</tr>
		</table>

		<h2 id="badges">14. Use Google Play badges and links in your promotional
		<h2 id="badges">15. Use Google Play badges and links in your promotional
		campaigns</h2>

		<p>Google Play badges give you an officially branded way of promoting your app
		@@ -473,7 +510,7 @@ and reviews, or any other channel available.</p>
		</tr>
		</table>

		<h2 id="final-checks">15. Final checks and publishing</h2>
		<h2 id="final-checks">16. Final checks and publishing</h2>

		<p>When you think you are ready to publish, sign in to the Developer Console and take a few moments for a few
		final checks:</p>
		@@ -511,7 +548,7 @@ final checks:</p>
		</table>


		<h2 id="support">16. Support users after launch</h2>
		<h2 id="support">17. Support users after launch</h2>

		<p>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

docs/html/distribute/googleplay/quality/core.jd

+109 −89

Original line number	Diff line number	Diff line
		@@ -45,7 +45,7 @@ of basic quality so that you can include them in your test plans.</p>

		<p>If your app is targeting tablet devices, make sure that it delivers a rich,
		compelling experience to your tablet customers. See the <a
		href="/distribute/googleplay/quality/tablet.html">Tablet App Quality
		href="{@docRoot}distribute/googleplay/quality/tablet.html">Tablet App Quality
		Checklist</a> for recommendations on ways to optimize your app for tablets.</p>


		@@ -72,7 +72,7 @@ user experience.</p>
		Tests
		</th>
		</tr>
		<tr id="cg7">
		<tr id="UX-B1">
		<td>Standard design</td>
		<td>
		UX-B1
		@@ -92,7 +92,7 @@ user experience.</p>

		<tr>
		<td rowspan="3">Navigation</td>
		<td id="cn1">
		<td id="UX-N1">
		UX-N1
		</td>

		@@ -102,7 +102,7 @@ user experience.</p>
		<td><a href="#core">CR-3</a></td>
		</tr>
		<tr>
		<td id="cn2">
		<td id="UX-N2">
		UX-N2
		</td>
		<td>
		@@ -111,7 +111,7 @@ user experience.</p>
		<td><a href="#core">CR-3</a></td>
		</tr>

		<tr id="cn4">
		<tr id="UX-N3">
		<td>
		UX-N3
		</td>
		@@ -120,6 +120,39 @@ user experience.</p>
		</td>
		<td><a href="#core">CR-1</a></td>
		</tr>
		<tr id="UX-S1">
		<td rowspan="2">Notifications</td>
		<td>
		UX-S1
		</td>
		<td>
		<p style="margin-bottom:.5em;">Notifications follow Android Design <a href="{@docRoot}design/patterns/notifications.html">guidelines</a>. In particular:</p>
		<ol style="margin-bottom:.5em;list-style-type:lower-alpha">
		<li>Multiple notifications are stacked into a single notification object, where possible.</li>
		<li>Notifications are persistent only if related to ongoing events (such as music playback or a phone call).</li>
		<li>Notifications do not contain advertising or content unrelated to the core function of the app, unless the user has opted in.</li>
		</ol>

		</td>
		<td><a href="#core">CR-11</a></td>
		</tr>
		<tr id="UX-S2">

		<td>
		UX-S2
		</td>

		<td>

		<p style="margin-bottom:.5em;">App uses notifications only to:</p>
		<ol style="margin-bottom:.5em;list-style-type:lower-alpha">
		<li>Indicate a change in context relating to the user personally (such as an incoming message), or</li>
		<li>Expose information/controls relating to an ongoing event (such as music playback or a phone call).</li>
		</ol>
		</td>
		<td><a href="#core">CR-11</a></td>
		</tr>

		</table>

		<table>
		@@ -127,9 +160,10 @@ user experience.</p>
		<td><p>Related resources:</p>
		<ul style="margin-top:-.5em;">
		<li><strong><a href="{@docRoot}design/index.html">Android Design</a></strong> — Overview of design and user experience best practices for Android apps. </li>
		<li><strong><a href="{@docRoot}design/patterns/navigation.html">Navigation with Back and Up</a></strong> — Android Design document describing standard navigation patterns and related topics. </li>
		<li><strong><a href="{@docRoot}design/patterns/navigation.html">Navigation with Back and Up</a></strong> — Android Design document describing standard navigation patterns. </li>
		<li><strong><a href="{@docRoot}design/patterns/actionbar.html">Action Bar</a></strong> — Android Design document describing how to use the Action Bar. </li>
		<li><strong><a href="{@docRoot}design/style/iconography.html">Iconography</a></strong> — Android Design document that shows how to use various types of icons.</li>
		<li><strong><a href="{@docRoot}design/style/iconography.html">Iconography</a></strong> — Android Design describing how to use various types of icons.</li>
		<li><strong><a href="{@docRoot}design/patterns/notifications.html">Notifications</a></strong> — Android Design document describing how to design and use notifications. </li>
		</ul>
		</td>
		</tr>
		@@ -157,7 +191,7 @@ user experience.</p>
		</th>
		</tr>

		<tr>
		<tr id="FN-P1">
		<td rowspan="2">Permissions</td>
		<td>
		FN-P1
		@@ -166,15 +200,14 @@ user experience.</p>
		</td>
		<td rowspan="2"><a href="#core">CR-11</a></td>
		</tr>
		<tr>
		<tr id="FN-P2">
		<td>
		FN-P2
		</td>
		<td><p style="margin-bottom:.5em;">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.
		</td>
		</tr>

		<tr>
		<tr id="FN-L1">
		<td>Install location</td>
		<td>
		FN-L1
		@@ -188,9 +221,9 @@ user experience.</p>
		<td><a href="#SD-1">SD-1</a>
		</td>
		</tr>
		<tr>
		<tr id="FN-A1">
		<td rowspan="4">Audio</td>
		<td id="cg1">
		<td>
		FN-A1
		</td>

		@@ -199,7 +232,7 @@ user experience.</p>
		</td>
		<td><a href="#core">CR-7</a></td>
		</tr>
		<tr id="cg2">
		<tr id="FN-A2">
		<td>
		FN-A2
		</td>
		@@ -208,7 +241,7 @@ user experience.</p>
		</td>
		<td><a href="#core">CR-8</a></td>
		</tr>
		<tr id="cg3">
		<tr id="FN-A3">
		<td>
		FN-A3
		</td>
		@@ -217,7 +250,7 @@ user experience.</p>
		</td>
		<td><a href="#core">CR-1, <br />CR-2</a></td>
		</tr>
		<tr id="cg4">
		<tr id="FN-A4">
		<td>
		FN-A4
		</td>
		@@ -226,32 +259,29 @@ user experience.</p>
		</td>
		<td><a href="#core">CR-1, CR-8</a></td>
		</tr>
		<tr id="cg5">
		<tr id="FN-U1">
		<td rowspan="3">UI and Graphics</td>
		<td>
		FN-U1
		</td>

		<td>
		<p style="margin-bottom:.5em;">App supports both landscape and portrait orientations (if possible).</em></p>

		<p style="margin-bottom:.25em;">Orientations expose largely the same features and actions and preserve functional parity.
		Minor changes in content or views are acceptable.</p>
		</td>
		<td><a href="#core">CR-5</a></td>
		</tr>
		<tr id="cg5">
		<tr id="FN-U2">
		<td>
		FN-U2
		</td>

		<td>
		<p style="margin-bottom:.5em;">App uses the whole screen in both orientations and does not letterbox to account for orientation changes.</em></p>
		<p style="margin-bottom:.25em;">Minor letterboxing to compensate for small variations in screen geometry is acceptable.</p>
		</td>
		<td><a href="#core">CR-5</a></td>
		</tr>
		<tr id="cg7">
		<tr id="FN-U3">
		<td>
		FN-U3
		</td>
		@@ -261,7 +291,7 @@ user experience.</p>
		<td><a href="#core">CR-5</a></td>
		</tr>

		<tr id="cg8">
		<tr id="FN-S1">
		<td rowspan="2">User/app state</td>
		<td>
		FN-S1
		@@ -272,9 +302,7 @@ user experience.</p>
		</td>
		<td><a href="#core">CR-6</a></td>
		</tr>


		<tr id="cn3">
		<tr id="FN-S2">
		<td>
		FN-S2
		</td>
		@@ -329,8 +357,7 @@ stability, and responsiveness expected by users.</p>
		Tests
		</th>
		</tr>

		<tr id="cg9">
		<tr id="PS-S1">
		<td>Stability</td>
		<td>
		PS-S1
		@@ -341,9 +368,9 @@ stability, and responsiveness expected by users.</p>
		<td><a href="#core">CR-all</a>, <a href="#SD-1">SD-1</a>, <a href="#HA-1">HA-1</a></td>
		</tr>

		<tr>
		<tr id="PS-P1">
		<td rowspan="2">Performance</td>
		<td id="cp1">
		<td>
		PS-P1
		</td>
		<td>
		@@ -354,7 +381,7 @@ stability, and responsiveness expected by users.</p>
		<a href="#core">CR-all</a>, <a href="#SD-1">SD-1</a>
		</td>
		</tr>
		<tr id="cp2">
		<tr id="PS-P2">

		<td>
		PS-P2
		@@ -367,7 +394,7 @@ stability, and responsiveness expected by users.</p>
		<a href="#PM-1">PM-1</a>
		</td>
		</tr>
		<tr id="cp3">
		<tr id="PS-M1">
		<td>Media</td>
		<td>
		PS-M1
		@@ -379,8 +406,7 @@ stability, and responsiveness expected by users.</p>
		<a href="#core">CR-all</a>, <a href="#SD-1">SD-1</a>, <a href="#HA-1">HA-1</a>
		</td>
		</tr>

		<tr id="cp4">
		<tr id="PS-V1">
		<td rowspan="2">Visual quality</td>
		<td>
		PS-V1
		@@ -390,13 +416,12 @@ stability, and responsiveness expected by users.</p>

		<ol style="margin-bottom:.5em;list-style-type:lower-alpha">
		<li>App provides high-quality graphics for all targeted screen sizes and form factors, including for <a href="{@docRoot}distribute/googleplay/quality/tablet.html">larger-screen devices such as tablets</a>.</li>
		<li>No aliasing at the edges of menus, buttons, and other UI elements.</li>
		<li>No aliasing at the edges of menus, buttons, and other UI elements is visible.</li>
		</ol>
		</td>
		<td rowspan="2"><a href="#core">CR-all</a></td>
		</tr>

		<tr id="cp5">
		<tr id="PS-V2">
		<td>
		PS-V2
		</td>
		@@ -405,25 +430,15 @@ stability, and responsiveness expected by users.</p>

		<ol style="margin-bottom:.5em;list-style-type:lower-alpha">
		<li>Composition is acceptable in all supported form factors, including for larger-screen devices such as tablets.</li>
		<li>No cut-off letters or words.</li>
		<li>No improper word wraps within buttons or icons.</li>
		<li>No cut-off letters or words are visible.</li>
		<li>No improper word wraps within buttons or icons are visible.</li>
		<li>Sufficient spacing between text and surrounding elements.</li>
		</ol>



		</td>

		</tr>




		</table>




		<table>
		<tr>
		<td><p>Related resources:</p>
		@@ -458,7 +473,7 @@ criteria below.</p>
		Tests
		</th>
		</tr>
		<tr>
		<tr id="GP-P1">
		<td rowspan="2">Policies</td>
		<td>
		GP-P1
		@@ -471,8 +486,7 @@ criteria below.</p>
		</td>
		</tr>


		<tr>
		<tr id="GP-P2">
		<td>
		GP-P2
		</td>
		@@ -487,9 +501,7 @@ criteria below.</p>
		</td>
		</tr>


		<tr>

		<tr id="GP-D1">
		<td rowspan="3">App Details Page</td>
		<td>
		GP-D1
		@@ -510,10 +522,8 @@ criteria below.</p>
		<td>
		<a href="#gp">GP-1, GP-2</a>
		</td>


		</tr>
		<tr>
		<tr id="GP-D2">
		<td>
		GP-D2
		</td>
		@@ -522,8 +532,7 @@ criteria below.</p>
		</td>
		<td rowspan="2"><a href="#gp">GP-1</a></td>
		</tr>

		<tr>
		<tr id="GP-D3">
		<td>
		GP-D3
		</td>
		@@ -532,7 +541,7 @@ criteria below.</p>
		represent the content and experience of your app in a misleading way.
		</td>
		</tr>
		<tr>
		<tr id="GP-X1">
		<td>User Support</td>
		<td>
		GP-X1
		@@ -553,7 +562,8 @@ criteria below.</p>
		<tr>
		<td><p>Related resources:</p>
		<ul style="margin-top:-.5em;">
		<li><strong><a href="http://play.google.com/about/developer-content-policy.html">Google Play Developer Program Policies</a></strong> — Guidelines for what is acceptable conent in Google Play. Please read and understand the and understand the policies before publishing.
		<li><strong><a href="https://play.google.com/apps/publish/">Publishing Checklist</a></strong> — Recommendations on how to prepare your app for publishing, test it, and launch successfully on Google Play.</li>
		<li><strong><a href="http://play.google.com/about/developer-content-policy.html">Google Play Developer Program Policies</a></strong> — Guidelines for what is acceptable conent in Google Play. Please read and understand the and understand the policies before publishing.</p>
		<li><strong><a href="http://support.google.com/googleplay/android-developer/bin/answer.py?hl=en&answer=188189">Rating your application content for Google Play</a></strong> — Help Center document describing content ratings levels and how to choose the appropriate one for your app.</li>
		<li><strong><a href="http://support.google.com/googleplay/android-developer/bin/answer.py?hl=en&answer=1078870">Graphic Assets for your Application
		</a></strong> — Details about the graphic assets you need to upload before publishing.</li>
		@@ -591,7 +601,10 @@ increase the number or complexity of tests and quality criteria. </p>
		Test Procedures
		</h2>

		<p>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. </p>
		<p>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. </p>

		<table>
		<tr>
		@@ -606,7 +619,7 @@ increase the number or complexity of tests and quality criteria. </p>
		</th>
		</tr>
		<tr>
		<td rowspan="11" id="core">Core Suite</td>
		<td rowspan="12" id="core">Core Suite</td>
		<td>
		CR-0
		</td>
		@@ -695,6 +708,12 @@ increase the number or complexity of tests and quality criteria. </p>
		<td>
		CR-11
		</td>
		<td>Trigger and observe in the notications drawer all types of notifications that the app can display. Expand notifications where applicable (Android 4.1 and higher), and tap all actions offered.</td>
		</tr>
		<tr id="CR-12">
		<td>
		CR-12
		</td>
		<td>Examine the permissions requested by the app by going to Settings > App Info.
		</td>
		</tr>
		@@ -709,9 +728,6 @@ increase the number or complexity of tests and quality criteria. </p>
		<p style="margin-bottom:.25em;">To move the app to SD card, you can use Settings > App Info > Move to SD Card.</p>
		</td>
		</tr>



		<tr id="tg3">
		<td>Hardware acceleration</td>
		<td>
		@@ -723,7 +739,6 @@ increase the number or complexity of tests and quality criteria. </p>
		<p style="margin-bottom:.25em;">To force-enable hardware acceleration (where supported by device), add <code>hardware-accelerated="true"</code> to the <code><application></code> in the app manifest and recompile.</p>
		</td>
		</tr>

		<tr id="tg3">
		<td>Performance Monitoring</td>
		<td>
		@@ -733,8 +748,7 @@ increase the number or complexity of tests and quality criteria. </p>
		<p style="margin-bottom:.5em;">Repeat <em>Core Suite</em> with StrictMode profiling enabled <a href="#strictmode">as described below</a>. <p style="margin-bottom:.25em;">Pay close attention to garbage collection and its impact on the user experience.</p>
		</td>
		</tr>

		<tr id="tg4">
		<tr id="gp">
		<td rowspan="3">Google Play</td>
		<td>
		GP-1
		@@ -743,7 +757,7 @@ increase the number or complexity of tests and quality criteria. </p>
		Sign into the <a href="https://play.google.com/apps/publish/">Developer Console</a> to review your developer profile, app description, screenshots, feature graphic, maturity settings, and user feedback.
		</td>
		</tr>
		<tr id="tg4">
		<tr id="GP-2">
		<td>
		GP-2
		</td>
		@@ -751,18 +765,18 @@ increase the number or complexity of tests and quality criteria. </p>
		Download your feature graphic and screenshots and scale them down to match the display sizes on the devices and form factors you are targeting.
		</td>
		</tr>
		<tr id="tg4">
		<tr id="GP-3">
		<td>
		GP-4
		GP-3
		</td>
		<td>
		Review all graphical assets, media, text, code libraries, and other content packaged in the app or expansion file download.
		</td>
		</tr>
		<tr id="tg4">
		<tr id="GP-4">
		<td>Payments</td>
		<td>
		GP-5
		GP-4
		</td>
		<td>
		Navigate to all screens of your app and enter all in-app purchase flows.
		@@ -775,9 +789,15 @@ increase the number or complexity of tests and quality criteria. </p>
		Testing with StrictMode
		</h3>

		<p>For performance testing, we recommend enabling <code><a href="{@docRoot}reference/android/os/StrictMode.html">StrictMode</a></code> 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 <code><a href="{@docRoot}reference/android/os/StrictMode.ThreadPolicy.Builder.html">ThreadPolicy builder</a></code> and enable all supported monitoring in the <code>ThreadPolicy</code> using <code><a href="{@docRoot}reference/android/os/StrictMode.ThreadPolicy.Builder.html#detectAll()">detectAll()</a></code>.</p>
		<p>For performance testing, we recommend enabling
		{@link android.os.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.</p>

		<p>Make sure to enable <strong>visual notification</strong> of policy violations for the <code>ThreadPolicy</code> using <code><a href="{@docRoot}reference/android/os/StrictMode.ThreadPolicy.Builder.html#penaltyFlashScreen()">penaltyFlashScreen()</a></code>.</p>
		<p>You can set up a monitoring policy per thread using
		{@link android.os.StrictMode.ThreadPolicy.Builder} and enable all supported monitoring in the
		<code>ThreadPolicy</code> using
		{@link android.os.StrictMode.ThreadPolicy.Builder#detectAll()}.</p>

		<p>Make sure to enable <strong>visual notification</strong> of policy violations
		for the <code>ThreadPolicy</code> using {@link android.os.StrictMode.ThreadPolicy.Builder#penaltyFlashScreen() penaltyFlashScreen()}.</p>

docs/html/distribute/googleplay/quality/tablet.jd

+14 −1

File changed.

Preview size limit exceeded, changes collapsed.