App size, low-end phones and conversion in emerging markets.
In India, a big download is a reason not to install. Google measured it, we lived it, and the fix is mostly engineering that the ASO team has to ask for.
The visitor liked your screenshots, tapped Install, saw the download size, and cancelled. Since July 2026, Play Console counts that as a success. Your revenue doesn't.
What Google measured
In its "Shrinking APKs, growing installs" analysis, Google Play reported that for every 6MB increase in an APK's size, install conversion rate fell by about 1%, across apps below 100MB. It also found smaller sizes had an even larger impact on conversion in emerging markets. The analysis dates from 2017, so treat the exact figure as directional, but the mechanism hasn't changed: storage is scarce and mobile data costs money.
What we saw in India
In the Gyan Studios portfolio, about 38% of target users ran phones with under 1GB of RAM and Android versions below 7.0, often shared between siblings. The first build was about 45MB and crashed on those phones. The rebuild compressed every asset, moved animations from frames to code, cut the build to under 22MB and set Android 6.0 as the minimum. Crash reports fell 91% and ratings recovered within ten days.
Why size is now harder to see
Since mid-2026, Play Console reports store listing CTR: taps on Install, not completed installs. A user who taps Install and cancels at the size prompt now counts as a success. Track acquisitions divided by clicks next to CTR; that completion rate is where size problems show up. See conversion rate vs CTR.
How to shrink the app
- Ship an Android App Bundle. Google Play builds optimised APKs per device, so each user downloads only the code and resources their phone needs.
- Compress images and audio. WebP for images, sensible bitrates for audio. In kids apps, media is usually most of the size.
- Replace frame animations with code-driven ones where possible.
- Move rarely used content to on-demand delivery with Play Feature Delivery or Play Asset Delivery.
- Remove unused libraries and enable code shrinking (R8).
- Test on the devices in your Android vitals report, not just recent phones.
Use size in the listing
- If the app is small, say so: "Under 25MB" is a reason to install in markets where storage is tight.
- Mention offline support where true, since data cost matters as much as storage.
- Keep an eye on per-device vitals; low-end phones are where large apps crash.
For the wider picture, see ASO for India in 2026.
Questions people ask
Does app size affect installs on Google Play?
Yes. Google Play found install conversion fell about 1% for every 6MB of extra APK size for apps under 100MB, with a larger effect in emerging markets.
How do I reduce my Android app size?
Publish an Android App Bundle, compress images and audio, use code-driven animation, move rarely used content to on-demand delivery, remove unused libraries and enable code shrinking.
Should I mention app size in my store listing?
If it is small, yes. In markets where storage and data are limited, a small download is a genuine reason to install.
Want this mapped onto your product?
See how our ASO work runs, or send your store link and a founder will reply personally.
