What the Install Bar on My Phone Actually Counts
The install bar said 84 MB. The download manager said 31 MB. Both were honest, and the gap between them is the first thing I check before a game earns a place on my phone.
An Android package ships compressed, unpacks into the app directory, then writes its cache on first launch. A 30 MB download that needs 250 MB free is not lying, it is counting a different stage.
I started that arithmetic after a phone with 9 GB free refused an update twice, then took it once I deleted a folder of screenshots. The page I use to sanity check a browser build, 8180, lists a size that matched my download manager.
Lite builds get creative. A stripped package can be a third of the size and still pull hundreds of megabytes of level data on first run. Something like sm605 loads as a page and asks for nothing beyond its own weight.
Browser games have their own version: nothing to install, but the cache grows quietly. Two weeks of a daily puzzle left 340 MB on my phone. I clear it and reopen rajajuara; the first load drags, then the figure climbs back within days.
Size is only half of it. The okwin apk I installed last month asked for storage and network access only, roughly what a game needs. A puzzle asking for my contacts is answering a question I never asked.
The rule is simple: check the download, the installed size, then watch the cache for a week. The 3126 apk I tried grew 60 MB in ten days, most of it audio I never heard. If a game cannot account for that growth, it does not stay.