|
|
|
|
|
by jbverschoor
1943 days ago
|
|
328 mb more than a complete OS.
No doubt they can EASILY trim 30-60%.
Asset optimization, stripping SDK libraries and you're done. It's like graffiti.. the app is so big already, that the devs don't give a damn about optimizing.. why bother if they are just A/B-feature tests? 30mb for some unoptimized screens for example |
|
If your app is serving hundreds of cities with specific per-city customizations and all code and assets are in a single binary, life gets tough.