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.
Related
When I upload an app bundle aab into the Google Play console (under internal testing track at the moment), I can see the following two tabs from the App Bundle Explorer. The sizes shown under the "Downloads" tab (for the APKs) and the "Delivery" tab (for my app only the "base" module) are very different.
Which one is the actual download size for an end user? I'd assume it's the "Delivery download size", but from the Google Play Store link Google generates for the user to install the app, the app info displays the full APK size. Isn't that kind of misleading to the user since it's (much) larger than the actual download size for user's device?
As you suspect, the size that end users download is the one shown as "Download size" in the Delivery section.
Google Play does not compress artifacts in the Internal Testing track, that's why you see a discrepancy in size. If you publish your artifact to any other track (e.g. a closed track), you should start seeing the "actual" download size in the Play Store.
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 published my app on play store with expansion files (obb format). On play store it the download size is apk size + obb file size. Can I get answers for following queries?
Is there any settings on console to download apk only and then manually trigger to download apk?
If you add expansion file, is it automatically downloaded with apk?
Sometimes it does not download automatically, what is the reason for that?
I was looking to download the app first and once app is installed, manually trigger the download of the expansion files (obb) from the play store.
After testing and speaking to customer care of Google developlers Play console I got this specification :
Google play automatically downloads the expansion files while downloading the apk most of the times.
There are exceptions sometimes it does not download with the apk and need to trigger download manually. One of the problem can be limited storage on the device.Then it needs to be triggered manually.
The size of the apk reflects the size of the apk and size of the expansion file together.
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
Docs say that APK size limit in Google Play is 50MB, with option for two 2GB expansion APKs.
However, I can find apps in Google Play store that are beyond this 50MB limitation (Gears & Guts for example is 371MB). I can download this game straight from Google Play itself without need for external downloaders. Do they have some extra feature as Top Developer to upload APKs over 50MB, or does Google Play just hide the fact that it's downloading expansion files rather than the APK itself?
Expansion files act kind of weird. To the user, they look like a normal app. A 50MB app with 150MB worth of expansion files will look like a 200MB download. Google Play will download the main app first. It will then download the main expansion file and then the patch expansion file. All in seemingly one lump sum.
However, it is possible for the download to be partial. I.E., the user can finish the main app download without the expansion files. As such, you MUST implement a custom downloader in order to retrieve the remaining files on the event the initial download fails. To make things a bit more complicated, sometimes the expansion files are not included in the initial download. I don't know what causes this, but I've seen it happen on rare occasions.
UPDATE: I just downloaded my APK again and Gears and Guts and they both show as one download but if you look at the status of the download in the status bar, it'll show that it's downloading an additional file.