Lines Matching full:have
39 href="http://android-developers.blogspot.com/2010/07/how-to-have-your-cupcake-and-eat-it-too.html">
40 How to have your (Cup)cake and eat it too</a></li>
65 href="http://android-developers.blogspot.com/2010/07/how-to-have-your-cupcake-and-eat-it-too.html">
76 <li>You don?t have to worry about market preference, behavior from "upgrades" from one APK to the
93 easily, and have an easy reference for later.</p>
149 likelihood of mistakes that could have been easily avoided.</p>
180 Also remember that each APK needs to have the same package name, although they don?t necessarily
181 need to share the package name with the library. If you were to have 3 APKs following the scheme
195 your application initialization in one place, so that each individual APK doesn?t have to
258 Because it is required that an APK with a higher minSdkVersion also have a
286 11. But, it turns out, not all devices that support API 11 even HAVE front-facing cameras! The
297 <p> In order to keep all your APKs on separate "tracks", it?s important to have a good version code
337 <li>All APKs must have the same package name</li>
339 <li>If the APKs overlap in platform version, the one with the higher minSdkVersion must have a higher version code</li>
342 <li>Try to test each APK on at least one device. Barring that, you have one of the most customizable device emulators in the business sitting on your development machine. Go nuts!</li>
370 <p>When you examine aapt output, be sure to check that you don?t have conflicting values for
371 supports-screens and compatible-screens, and that you don?t have unintended "uses-feature" values
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>
