Despite the fact that we urge you to create and distribute a solitary APK that supports however many gadget designs as could reasonably be expected, doing as such is in some cases impractical. To enable you to distribute your application for whatever number gadgets as could be expected under the circumstances, Google Play enables you to distribute numerous APKs under a similar application posting. Google Play at that point supplies each APK to the appropriate gadgets in view of design support you've proclaimed in the show document of each APK.
By distributing your application with various APKs, you can:
• Support diverse OpenGL surface pressure positions with each APK.
• Support diverse screen sizes and densities with each APK.
• Support diverse gadget highlight sets with each APK.
• Support distinctive stage forms with each APK.
• Support diverse CPU designs with each APK, (for example, for ARM, x86, and MIPS, when your app utilizes the Android NDK).
Right now, these are the main gadget qualities that Google Play supports for distributing different APKs as a similar application.
Before you can distribute your application (regardless of whether distributing one or different APKs), you should "actuate" your APK(s) from the APK records tab. When you actuate an APK, it moves into the rundown of Active APKs. This rundown enables you to see which APK(s) you're going to distribute.
In the event that there are no mistakes, any "dynamic" APK will be distributed to Google Play when you tap the Publish catch (if the application is unpublished) or when you tap the Save catch (if the application is as of now distributed).
Basic mode and propelled mode
The Google Play Console gives two modes to dealing with the APKs related with your application: basic mode and propelled mode. You can switch between these by tapping the connection at the upper right corner of the APK records tab.
Basic mode is the conventional approach to distribute an application, utilizing one APK at once. In basic mode, just a single APK can be initiated at once. In the event that you transfer another APK to refresh the application, clicking "Actuate" on the new APK deactivates the right now dynamic APK (you should then snap Save to distribute the new APK).
Propelled mode enables you to enact and distribute different APKs that are each intended for a particular arrangement of gadget designs. Nonetheless, there are a few standards in view of the show assertions in each APK that decide if you're permitted to initiate each APK alongside others. When you enact an APK and it abuses one of the guidelines, you will get a mistake or cautioning message. In the event that it's a blunder, you can't distribute until the point when you settle the issue; if it's a notice, you can distribute the enacted APKs, yet there may be unintended outcomes in the matter of whether your application is accessible for various gadgets. These tenets are talked about additional beneath.
How Multiple APKs Work
The idea for utilizing numerous APKs on Google Play is that you have only one passage in Google Play for your application, yet unique gadgets may download an alternate APK. This implies:
• You keep up just a single arrangement of item subtle elements (app depiction, symbols, screenshots, and so on.). This likewise implies you can't charge an alternate cost for various APKs.
• All clients see just a single rendition of your application on Google Play, so they are not befuddled by various adaptations you may have distributed that are "for tablets" or "for phones."
• All client surveys are applied to a similar application posting, despite the fact that clients on various gadgets may have diverse APKs.
• If you distribute diverse APKs for various adaptations of Android (for various API levels), at that point when a client's gadget gets a framework refresh that qualifies them for an alternate APK you've distributed, Google Play refreshes the client's application to the APK intended for the higher rendition of Android. Any framework information related with the application is held (the same as with ordinary application refreshes when utilizing a solitary APK).
To Share Apps Via Third-Party Apps
To distribute various APKs for a similar application, you should empower Advanced mode in your application's APK documents tab (as examined in the past segment). Once in cutting edge mode, you can transfer, enact, at that point distribute different APKs for a similar application. The accompanying areas depict more about how it functions.
Supported channels Which gadgets get each APK is dictated by Google Play channels that are determined by components in the show record of each APK. Notwithstanding, Google Play enables you to distribute various APKs just when each APK utilizes channels to support a variety of the accompanying gadget attributes:
• OpenGL surface pressure groups
This depends on your show document's <supports-gl-texture> element(s).
For instance, when building up a diversion that utilizations OpenGL ES, you can give one APK to gadgets that support ATI surface pressure and a different APK for gadgets that support PowerVR pressure (among numerous others).
• Screen measure (and, alternatively, screen thickness)
This depends on your show record's <supports-screens> or <compatible-screens> component. You ought to never utilize the two components and you should utilize just <supports-screens> when conceivable.
For instance, you can give one APK that supports little and ordinary size screens and another APK that supports substantial and large screens. To take in more about creating separate APKs in light of screen size or thickness, go to Build Multiple APKs.
Comments
Post a Comment