Lines Matching full:play
36 <li><a href="http://developer.android.com/google/play/publishing/multiple-apks.html">Multiple APK
47 <p>When developing your Android application to take advantage of multiple APKs on Google Play,
60 href="{@docRoot}google/play/publishing/multiple-apks.html#ApiLevelOptions">Using Single APK
201 <p>When a user downloads an application which uses multiple APKs through Google Play, the correct
282 <a href="{@docRoot}google/play/filters.html">Filters on Google Play</a> page of
289 <p>Fortunately, if a user is browsing Google Play from one such device, Google Play will look at the
294 from Google Play by the user, because despite the whole front-camera mishap, there was still an
299 href="{@docRoot}google/play/publishing/multiple-apks.html#VersionCodes">Version Codes</a> area of
334 <p> Before uploading to Google Play, double-check the following items. Remember that these are specifically relevant to multiple APKs, and in no way represent a complete checklist for all applications being uploaded to Google Play.</p>
346 any surprises that could hide your application on Google Play. This is actually quite simple using the
374 <p>Why? By adding the required permission SEND_SMS, the feature requirement of android.hardware.telephony was implicitly added. Since API 11 is Honeycomb (the version of Android optimized specifically for tablets), and no Honeycomb devices have telephony hardware in them, Google Play will filter out this APK in all cases, until future devices come along which are higher in API level AND possess telephony hardware.
384 <p>Once you?ve completed the pre-launch checklist, upload your APKs to Google Play. It may take a bit for the application to show up when browsing Google Play, but when it does, perform one last check. Download the application onto any test devices you may have, to make sure that the APKs are targeting the intended devices. Congratulations, you?re done!</p>
