Android Same app bundle for multiple os versions - android

How to use the same app bundle & based on minimum SDK & target SDK versions for the old API version it would be a very lite version of the app with less Gradle dependencies & code.
The old way to implement this to have two projects with one key store signing & to upload multiple Apks.
Is there a difference while using the app bundle or I have to generate multiple app bundles & upload them on google play?
Please note the core library is not applicable here because the full project is up & running.

You have basically two options:
Use of conditional delivery which supports serving parts of your app above or below a certain API version.
Publish two separate Android App Bundles with a different minSdkVersion and different versionCodes (similarly to how you published multiple APKs).
Hope that helps.

Related

Cancel support for legacy Android SDK level for new installs

My app currently has a minSdkVersion of 15 (ICS 4.0.3).
Due to additional dependencies, I have to go up with the min SDK to 19 (Kitkat 4.4).
I already build multiple APKs for min15 and min19 productFlavors.
I'd like to provide bugfixes for my existing users of min15, but don't want new users to install min15.
How can I accomplish this?
Is it possible to unpublish the min15 for new installs, but still provide updates for existing users?
At the moment this is not possible. You can't unpublish single APKs, just the whole app.
You should publish multiple apks for your app. one with minSDK 15 and another one with minSDK 19. Play-store allows this
Multiple APK support is a feature on Google Play that allows you to
publish different APKs for your application that are each targeted to
different device configurations. Each APK is a complete and
independent version of your application, but they share the same
application listing on Google Play and must share the same package
name and be signed with the same release key. This feature is useful
for cases in which your application cannot reach all desired devices
with a single APK.
Check docs here

How to publish Project Tango and no-Tango versions in one application?

I want to publish an application with two apk versions:
for devices with Project Tango support;
for rest devices.
But when I try to publish them as is, I get Fully shadowed APK error on tango version (This APK will not be served to any users because it is completely shadowed by one or more APKs with higher version codes).
Is it possible to publish application as I want?
Assign the higher versionCode to the Tango build.

Publish Multiple APK with different android version

Is it possible Publish 2 apk for different android version?
I using cordova to build to apps and I need to use crosswalk to build when android version below v4.4.
Higher than v4.4 android just use normal build.
Yes, you can publish multiple APKs to the Play Store.
Each APK must be signed with the same key and must use a different version code. The version that supports a higher minimum SDK version must have the higher version code.
By have two different APKs with differed minSdkVersions defined, users will receive whichever version has the highest support API level.
For full documentation regarding this feature, read the Multiple APK Support documentation.

Can I upload apks for multiple architectures into the Google Play store without using the android NDK?

I need to produce 2 apks, one for x86 and one for ARM. I do this with different versions of crosswalk, which internally uses cordova. All I need to do one the two projects are created is ./cordova/build --release and then sign the APK. The Google Play store docs mention a way of uploading both into a single app listing, but they assume I'm using the Android NDK, which I'm not. Will I need to start using it or is there another way to simply upload both apks?
Google does support posting of architechture-specific APKs: http://developer.android.com/google/play/publishing/multiple-apks.html. Note however that the documentation states, in bold:
we encourage you to develop and publish a single APK
So, if you take the single APK approach:
Just compile your native code into libraries (i.e. .so files) and place them in the following locations
<Project_Root>/app/src/main/jniLibs/armeabi/
and
<Project_Root>/app/src/main/jniLibs/x86/
The build process will package these in the appropriate manner so that your APK contains libs for both architectures. Then at runtime, Android will ensure that the architecture-appropriate library is loaded.
Note that the above assumes that you are using Gradle to build your APKs. If you are using the old ant-based build process, the locations are slightly different:
<Project_Root>/libs/armeabi/
and
<Project_Root>/libs/x86/

Could I submit multiple apk file on google play for multiple target?

I'm tending to release and submit to GooglePlay two apk files of the same application. One with android sdk 7 for android version lower than 4.0, one with android sdk 14 for android 4.0 and upper. Is it possible?
Yes you can. But, it might be tricky.
http://developer.android.com/guide/google/play/publishing/multiple-apks.html
There will be some problems, when you different apks for devices, which are close to each other. But, you can get started with the above link.
It's recommended though, to have a single apk.
Note: You should generally use multiple APKs to support different device configurations only when your APK is too large (greater than 50MB).

Categories

Resources