Is there any one familiar with this "Externally hosted private apps"? We are planning to host our Android Apk onto Managed Google Play but the apk size is around 300mb, it is way too much over the allowable size which is 100mb. We are not able to externalize the assets at the moment, so we are thinking to go for this "Externally hosted private apps", it sounds like it allows to by-pass size limit because we are hosting the apk on our premise and only the metadata is uploaded onto Managed Google Play. I can't find any doc saying the size limit though. Is there anyone is using this way and could you please share some information?
Related
I'm upload the same aab package on Test Internal Track and on Internal App Sharing. And the result is soo strange:
from the test internal app the download size is 44mb
from the internal app sharing the download size is 75mb
I would has expected the same download size.
Why are there this size difference ?
The difference comes from the compression of the APK.
When serving an APK from a testing track or the production track, Play compresses the APK on the wire. When possible, it also instead serves a patch with the difference from the previous version. This considerably reduces the size of what users have to download.
When serving an APK from internal app sharing, Play does not go through the trouble of compressing or generating patches since it's only for development / early testing purposes.
The files in the APKs should be the same whether the bundle is uploaded to internal app sharing or to a testing/production track.
The AAB contains the resources of your app in different languages, screen resolutions, ecc...
When you download an app from the Play Store, it will actually download only a part of the AAB, the part that actually is needed on your specific device (based on language, screen resolution, ecc...)
I think that this concept works on Test Internal Track, but not on the Internal App Sharing, because the Internal App Sharing is a lot more "debug oriented", (for example you can upload a debug build, you don't have to sing the bundle with your production key...) and so I think that with the Internal App Sharing you are actually downloading the entire bundle, not optimized for your specific device.
This can be the reason for the different download sizes, but this is just my opinion though :)
I've developed an app which is using a lot of resources. I've successfully installed the app, having size of 765MB. But when I run, it crashes. So, I want to know is there any limitation in android for resources or not?
My app contains various images and audios that is why its size is so large.
According to those questions:
First question
, Second Question
so one can have up to 65,535 resources of any one type
Google play store apk size is
Google will store two expansion files per application. Each which can be up to 2GB in size. so expansion files: 4GB (2*2GB)
APK file size limit to 100MB
Google Play Store APK Size Limit 100MB.
please check link.
https://stackoverflow.com/a/21331051/7344185
It's highly likely that your app is crashing due to a different reason than the size of the APK.
One of the more common reasons for crashing when developers use images is an OutOfMemoryError from loading large bitmaps: Here's a documentation about this common error: https://developer.android.com/topic/performance/graphics/load-bitmap
But that guess is mainly due to you saying your huge APK size is due to images and audio, which might happen if you're including really high quality versions of images.
There's no way to know the reason for the crash without checking your error log though.
However, the main thing to keep in mind which others have mentioned is that even though your app might work properly after the error is fixed, you still won't be able to release it on the Play Store with that large of an APK size.
So the large APK size might not be the reason for your app to crash, but it's still an issue.
Here is a documentation on how to reduce the APK size: https://developer.android.com/topic/performance/reduce-apk-size
If it's still not enough, consider using APK Expansion Files: https://developer.android.com/google/play/expansion-files
Otherwise, the only other option is to host the extra files yourself and download it into the device when needed... which might be better or worse than the APK Expansion Files depending on your needs.
But disregard all of that latter part if you don't plan to submit this app to the Google Play Store and only plan to use it through installing locally.
I doubt that your app is crashing because of its size. As long as you have enough space on your device to operate the app, it should work fine. Check your logs for the exception you're getting, that should give you a hint on why it's crashing.
If you plan to upload this apk on Playstore:
Use an expansion file. You cannot upload an APK file of more than 50MB (for API levels < 9) or 100MB (for API levels > 8) to Playstore. So, we can rule that out. Also, your users must have Playstore version 5.2 or higher to install 100 MB APKs.
App apk size around 145 MB. It Contains 9-10 gif Images around 100 MB.So,I can't upload app on google play store.
So I am trying to implement app bundle by using this link:-
https://medium.com/#AndreSand/android-app-bundle-96ac16b36875
app bundle makes successful with .aab extension but its size is not less and when I try to upload it on google play store it gives an error that some apk file size has more than 100 MB.
Google Play currently requires that your APK file be no more than 100MB. For most applications, this is plenty of space for all the application's code and assets. However, some apps need more space for high-fidelity graphics, media files, or other large assets. Previously, if your app exceeded 100MB, you had to host and download the additional resources yourself when the user opens the app. Hosting and serving the extra files can be costly, and the user experience is often less than ideal. To make this process easier for you and more pleasant for users, Google Play allows you to attach two large expansion files that supplement your APK.
Read APK Expansion Files.
FYI
The new app publishing format, the Android App Bundle, is a more efficient way to build and release your app. The Android App Bundle lets you more easily deliver a great experience in a smaller app size.
will be more better to upload low size APk otherwise user will never download app from play store. if you have large images or gifs and you don't have server then you can use firebase storege where you can easily store your files and fetch . where you can upload your file and get images paths .
I have my Android apk thats built locally. The apk size is 10.96MB.
ls -ltrh reads as 11MB. I uploaded this apk to Google Play store and tried installing the app from playstore, the progress bar reads as 1 MB/7.90 MB 10%
Why question is why am I seeing 7.9MB instead of 10.96MB. Does Google play store optimize the apk?
I don't know about google appstore but i am using another appstore that in the information page said the apk size in appstore downloaded with 75% of real size and it is like compression.and Jaswanth Manigundan's comment is good too.
i reserched this and i found that google will optimise and compress the app to save space on their servers and also make it faster to download. after downloading, the file will be decompressed and then installed, this saves time and space. also, google doesnt optimise the apk. it compresses it
I'm expecting suggestions for the concept related to APK Expansion Files in Android.
Google Play currently requires that your APK file be no more than 50MB. For most applications, this is plenty of space for all the application's code and assets. However, some apps need more space for high-fidelity graphics, media files, or other large assets. Previously, if your app exceeded 50MB, you had to host and download the additional resources yourself when the user opens the app. Hosting and serving the extra files can be costly, and the user experience is often less than ideal. To make this process easier for you and more pleasant for users, Google Play allows you to attach two large expansion files that supplement your APK.
Does apple give any support like this?
In my case I have 180MB audio file, I don't want to keep that with app resource. After installation I want this download from APPLE store.
I can able to keep this in my server and download when app opens first time, but I would like to know is there any other way to supplement for iPA.
Thanks InAdvance.
The maximum size of your ipa could be up to 2GB. For sizes upper than 50mb will be downloaded through WiFi or from iTunes. ipa less than that could also be downloaded through 3G network.
Try to make your app size as minimum as possible as users don't really like apps with larger size..
Well there's no thing here in iOS like APK Extension Files in Android.. Everything is your one single ipa which is compressed form of your binaries and resources.
Apple doesn't offer a facility for this specific use case.
You'll have to download the content when your app starts for the first time. Remember to store it in the caches directory or set the "do not backup" flag on the files. This is according to Apple's guidelines and required for app review. If you store it in the Caches directory, iOS may decide to delete the data when disk space is low, so be prepared to download it again if it doesn't exist when your app starts.
Unless you're using in-app purchases and targetting iOS 6 users only, you'll have to host it on your own servers. In-app purchases cannot be free.