Mobile App Bloat: The Storage Tax Nobody Talks About
Archi3 min read
Contents
The Headline That Missed the Point#
Last week, a popular tech blog published a chart showing that the average mobile app download size has grown 300 percent in five years. The story was shared widely, and the comments filled with complaints about bloated apps and lazy developers. But the chart measured the wrong thing. Download size is a one-time cost. The real burden is the storage tax: the gigabytes that apps consume after installation, and the way that tax falls hardest on people with the least expensive phones.
The Storage Tax, Explained#
When you install an app, the download is just the beginning. The app unpacks, creates caches, stores user data, and often duplicates resources for different screen sizes and languages. A 100 MB download can easily become 500 MB or more on disk. On a 64 GB phone, which is still common in the budget tier, that adds up fast.
Google's own data, published in Android developer documentation, shows that apps in the top 100 on the Play Store often use three to five times their download size in storage. Games can be worse: a 1 GB download can expand to 4 GB or more. The chart that went viral measured the front door. The storage tax is the rest of the house.
Who Pays the Tax#
The people most affected are not the ones buying 1 TB flagship phones. They are the ones buying $150 devices with 32 GB or 64 GB of storage, often with a microSD card slot that is either missing or too slow to be useful. In many markets, that is the majority of users. A 2023 report from device intelligence firm Counterpoint Research found that phones with 64 GB or less still accounted for roughly a third of global smartphone sales.
Those users face a constant choice: delete photos, delete apps, or give up. The storage tax is regressive. It takes a bigger percentage of a cheap phone's capacity than a flagship's.
The Hidden Duplication Problem#
One reason apps take up so much space is that they ship multiple copies of the same assets. A single image might be stored in five resolutions for different screen densities. A font might be bundled in three weights when the system already has a usable version. These choices make sense for performance on high-end devices, but they are wasteful on low-end ones.
Apple and Google have both introduced tools to reduce this: Android App Bundles let the store deliver only the resources a specific device needs, and Apple's app thinning does something similar. But adoption is uneven. Many popular apps still ship universal binaries because it is simpler, and because the developers test on phones with plenty of space.
What the Headlines Got Wrong#
The viral chart focused on download size because it is easy to measure. Storage after installation is harder to track, and the stores do not make it prominent. The Play Store shows download size, not installed size, on the listing page. The App Store shows download size, and only after installation do you see the real number in Settings.
That information gap matters. Users cannot make informed choices if they cannot see the cost. A few third-party tools estimate installed size, but they are not mainstream.
A Small Change That Would Help#
Both stores could show installed size next to download size. That single change would make the storage tax visible. It would also create pressure on developers to reduce waste, because users would see which apps are the worst offenders.
Some developers are already working on this. A movement toward on-demand resources, where assets are downloaded only when needed, is gaining traction in game development. But it requires more testing and more careful engineering, and those cost money.
The Bottom Line#
The next time you see a story about app bloat, check what it is measuring. Download size is not the whole story. The storage tax is the part that hits the people with the least room to spare. Until the stores show installed size, that tax will stay hidden, and the headlines will keep missing it.
More articles