Home | History | Annotate | Download | only in publishing

Lines Matching full:play

25       <li><a href="{@docRoot}distribute/googleplay/publish/preparing.html">Launch Checklist for Google Play</a></li>
42 application marketplace such as Google Play.</p>
47 Play, you should also read <a href="{@docRoot}distribute/googleplay/publish/preparing.html">Publishing
48 Checklist for Google Play</a> to be sure your release-ready application satisfies all Google Play
92 application. For example, if you are releasing your application through Google Play you may want
94 release. Similarly, to meet Google Play publishing guidelines you may have to prepare screenshots
140 elsewhere. In addition, publishing services such as Google Play display your icon to users.</p>
142 <p class="note"><strong>Note:</strong> If you are releasing your application on Google Play, you
157 For example, if you are releasing your application on Google Play you will need to prepare some
245 application on Google Play. For example, the <code>android:minSdkVersion</code> and
248 information about these and other Google Play settings, see <a
249 href="{@docRoot}google/play/filters.html">Filters on Google Play</a>.</p>
286 <h4>Implement Licensing (if you are releasing on Google Play
288 <p>If you are releasing a paid application through Google Play, consider adding support for
289 Google Play Licensing. Licensing lets you control access to your application based on whether the
290 current user has purchased it. Using Google Play Licensing is optional even if you are
291 releasing your app through Google Play.</p>
293 <p>For more information about Google Play Licensing Service and how to use it in your
294 application, see <a href="{@docRoot}google/play/licensing/index.html">Application Licensing</a>.</p>
336 href="{@docRoot}google/play/billing/index.html">in-app billing</a> in your application and you are
355 Application to Users</a>. If you are publishing your application on Google Play, see
357 for Google Play</a>.</p>