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
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 :)
Our .aab file size has exceeded 150 MB. I want to know whether we can publish the .aab file of more than 150 MB file on the Play Store.
As per the developer docs:
https://developer.android.com/guide/app-bundle/
Publishing with Android App Bundles also increases the app size limit to 150MB without having to use APK expansion files. Keep in mind, this limit applies only to the actual download size, not the publishing size. So, users can download apps as large as 150MB
According to the documentation, I understood that we can publish the .aab more than 150 MB, but when the user downloads the APK from Play Store, the APK size should be within the 150 MB limit.
Is my understanding correct here?
Read this part of docs
https://developer.android.com/guide/app-bundle/#size_restrictions
As it is stated that
Compressed download size restriction
While publishing with Android App Bundles helps your users install your app with the smallest download possible, compressed downloads are limited to 150 MB. That is, when a user downloads your app, the total size of the compressed APKs required to install your app (for example, the base APK + configuration APK(s)) must be no more than 150 MB. Any subsequent downloads, such as downloading a dynamic feature (and its configuration APK(s)) on demand, must also meet this compressed download size restriction.
When you upload your app bundle, if the Play Console finds any of the possible downloads of your app or its on demand features to be more than 150 MB, you get an error
This week, my Android App Bundle's size reached 161MB after introducing several new features. I was frightened that my aab's size exceeds the size limitation of Android App Bundles. But I tried to upload the oversize aab to the Google Play and it worked. I was confused and did many research to figure it out, here's what I got.
Can my Android App Bundle's size be over 150MB?
Yes, Android App Bundles's size can be over 150MB. As the official Android Developer Document Android App Bundles-Compressed download size restriction said, the total size of the compressed APKs required to install our app (for example, the base APK + configuration APKs) must be no more than 150 MB, rather than the Android App Bundles's size.
How to measure the size range of compressed APKs from my app bundle?
Although Android App Bundles's size can be over 150MB, we must be curious about the real size range of compressed APKs, as we wanna know the left available size for our app to use.
Fortunately, Google shared methods to estimate our app’s download size for a given device configuration. This is helpful to better understand the user experience of downloading our app and checking whether our app meets the compressed download size restriction for app bundles or enabling instant experiences.
After you build your Android App Bundle, you should test how Google Play uses it to generate APKs and how those APKs behave when deployed to a device. There are two ways you should consider testing your app bundle: locally using the bundletool command line tool and through Google Play by uploading your bundle to the Play Console and using a test track.
When bundletool generates APKs from your app bundle, it includes them in a container called an APK set archive, which uses the .apks file extension. To generate an APK set for all device configurations your app supports from your app bundle, use the bundletool build-apks command, as shown below.
bundletool build-apks --bundle=/MyApp/my_app.aab --output=/MyApp/my_app.apks
To measure the estimated download sizes of APKs in an APK set as they would be served compressed over-the-wire, use the get-size total command:
bundletool get-size total --apks=/MyApp/my_app.apks
My Android App Bundle /MyApp/my_app.aab's size is 161MB. Here's the result I got from bundletool get-size total command, which means the size range of compressed APKs from my app bundle is between 105632514 Bytes to 111835648 Bytes. 111835648 Bytes is equal to 106.65MB, which is less than 150MB. Therefore, we figure out that my Android App Bundle have 43.35MB left available size to use.
bogon:bundletool happylee$ bundletool get-size total --apks=/MyApp/my_app.apks
MIN,MAX
105632514,111835648
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 an Android App which has a size of 90 MB in total whereas the expansion file is 76 and the real app only 13 MB.
Whenever downloading the App from the Android market for the first time it gives a popup saying "Downloading a large app".
Does anyone know up from which file size the Google PlayStore is showing this popup or is this just shown by default because I am using an APK expansion file?
Best regards
tsemann
when you download the app from google play, it will also download the APK expansion pack together with the stripped APK. Thus this will make google play show popup that you are downloading a large app. Also, if you look on the app size in google play store you will see that the size is the total of APK + expansion file.