Lines Matching full:play
2 page.metaDescription=If your app needs more than the 50MB APK max, use free APK expansion files from Google Play.
13 <li>Google Play hosts and serves the expansion files at no charge</li>
57 <li><a href="{@docRoot}google/play/licensing/index.html">Application Licensing</a></li>
58 <li><a href="{@docRoot}google/play/publishing/multiple-apks.html">Multiple
66 <p>Google Play currently requires that your APK file be no more than 50MB. For most
72 for users, Google Play allows you to attach two large expansion files that supplement your
75 <p>Google Play hosts the expansion files for your application and serves them to the device at
78 them. On most devices, Google Play downloads the expansion file(s) at the same time it
80 first time. In some cases, however, your application must download the files from Google Play
87 <p>Each time you upload an APK using the Google Play Developer Console, you have the option to
121 of resource files and subsequent patches for that set. Regardless of the file type, Google Play
153 <p>When Google Play downloads your expansion files to a device, it saves them to the system's
155 expansion files. In the event that your application must perform the download from Google Play
200 <p>Most of the time, Google Play downloads and saves your expansion files at the same time it
201 downloads the APK to the device. However, in some cases Google Play
204 itself when the main activity starts, using a URL provided by Google Play.</p>
209 <li>User selects to install your app from Google Play.</li>
210 <li>If Google Play is able to download the expansion files (which is the case for most
212 <p>If Google Play is unable to download the expansion files, it downloads the
219 <li>If no, your app must download the expansion files over HTTP from Google Play. Your app
220 must send a request to the Google Play client using the Google Play's <a
221 href="{@docRoot}google/play/licensing/index.html">Application Licensing</a> service, which
229 download the expansion files from Google Play in the event that the files are not already on the
248 href="{@docRoot}google/play/publishing/multiple-apks.html">multiple APKs</a> in which each APK
264 are on the device upon start-up. If the files are not on the device, use Google Play's <a
265 href="{@docRoot}google/play/licensing/index.html">Application Licensing</a> service to request URLs
291 <li>In order to download your expansion files from Google Play, <strong>the user must have
292 acquired your application from Google Play</strong>. Google Play will not
294 <li>When performing the download from within your application, the URL that Google Play
298 href="{@docRoot}google/play/publishing/multiple-apks.html">multiple APKs</a> for the same
303 href="{@docRoot}google/play/publishing/multiple-apks.html">multiple APKs</a> in order to
307 value and declare different <a href="{@docRoot}google/play/filters.html">filters</a> for
319 performing an update). Doing so will cause Google Play (or your app itself) to repeatedly
334 <p>In most cases, Google Play downloads and saves your expansion files to the device at the same
338 from Google Play's <a
339 href="{@docRoot}google/play/licensing/index.html">Application Licensing</a> service.</p>
351 <li>Perform a request using Google Play's <a
352 href="{@docRoot}google/play/licensing/index.html">Application Licensing</a> to get your
354 <li>Use the URLs provided by Google Play to download the expansion files and save
358 by Google Play's response.
359 <p class="note"><strong>Note:</strong> The URL that Google Play provides for your
371 href="{@docRoot}google/play/licensing/index.html">Application Licensing</a> service. It's primarily
374 use your app (he or she rightfully paid for it on Google Play). In order to facilitate the
377 on Google Play. So, even if your application is free for users, you need to include the
382 <p class="note"><strong>Note:</strong> Whether your application is free or not, Google Play
383 returns the expansion file URLs only if the user acquired your application from Google Play.</p>
415 Play URLs, you must follow the <a href="{@docRoot}google/play/licensing/index.html">Application
427 Google Play APK Expansion Library package. This library downloads your expansion files in a
456 <li><em>Google Play Licensing Library package</em></li>
457 <li><em>Google Play APK Expansion Library package</em></li>
470 <li>Specify a <em>Project Name</em> such as "Google Play License Library" and "Google Play
501 Google Play. The format that you choose for the expansion files and how you read them
524 <!-- Required to access Google Play Licensing -->
527 <!-- Required to download files from Google Play -->
581 href="{@docRoot}google/play/licensing/setting-up.html">Setting Up for Licensing</a>).</dd>
585 href="{@docRoot}google/play/licensing/adding-licensing.html#impl-Obfuscator">{@code
920 <p>If you decide to build your own downloader service instead of using the Google Play
924 Google Play License Verification Library) but includes additional handling for the APK expansion
945 href="{@docRoot}google/play/licensing/adding-licensing.html">Adding Licensing to Your App</a>,
1112 play a video with {@link android.widget.VideoView#setVideoURI VideoView.setVideoURI()}.</p></dd>
1164 <p>Before you upload your application to Google Play, you
1171 Play will save your files.
1178 match the <a href="#Filename">file name format</a> that Google Play will use.
1186 Google Play.
1196 the data to a different location). Doing so will cause Google Play (or your app itself) to
1221 href="{@docRoot}google/play/billing/billing_testing.html#draft_apps">Draft Apps
1226 <p>One of the great benefits to using expansion files on Google Play is the ability to
1227 update your application without re-downloading all of the original assets. Because Google Play
1233 the Android system nor Google Play perform actual patching between your main and patch expansion
1242 expansion file, you must still update the APK in order for Google Play to perform an update.
1256 file and one patch expansion file. During an update to a file, Google Play deletes the
