Skip to main content
Technology & EngineeringPerformance Optimization30 lines

Application Binary and Asset Size Audit

Compare application download and installed sizes across target variants, identify large binaries or duplicated assets, and validate runtime behavior after optimization.

Quick Summary10 lines
State the platform, release channel, architecture, locale, device configuration and size metric before measuring. Distinguish the artifact submitted to a store, compressed download for one device, installed footprint and post-install downloads. A single upload ZIP or universal package is not a device-specific result. Save the baseline revision, toolchain, build configuration and output digests.

## Key Points

- [Android APK Analyzer](https://developer.android.com/studio/debug/apk-analyzer)
- [Android bundletool and estimated sizes](https://developer.android.com/tools/bundletool)
- [Apple app size reporting and thinning](https://developer.apple.com/documentation/xcode/reducing-your-app-s-size.md)
- [Flutter app size analysis](https://docs.flutter.dev/tools/devtools/app-size)
skilldb get performance-optimization-skills/application-size-auditFull skill: 30 lines
Paste into your CLAUDE.md or agent config

Application Binary and Asset Size Audit

State the platform, release channel, architecture, locale, device configuration and size metric before measuring. Distinguish the artifact submitted to a store, compressed download for one device, installed footprint and post-install downloads. A single upload ZIP or universal package is not a device-specific result. Save the baseline revision, toolchain, build configuration and output digests.

Attribute bytes using the delivered variants

For Android, inspect the APK or app bundle with APK Analyzer and use bundletool to estimate the APK set for the intended device configuration. Record ABI, density, locale and whether dynamic features were included. For iOS, compare an app size report or corresponding App Store measurements by thinned variant. Do not substitute a debug binary, Xcode archive or upload IPA for customer download. If working on Flutter, use the size analysis tooling to identify Dart and native component contributions while keeping the platform delivery metrics separate.

List the largest categories and files. Check duplicated packages, duplicate media encodings, unnecessary locales or architectures, test assets, bundled source maps, runtime dependencies and symbols. Use content hashes to distinguish exact copies from different variants of the same asset. Explain why each category is included before removing it. Keep crash symbolication and build provenance available through the proper release-artifact path.

Confirm size changes preserve the product

Apply one focused change, such as pruning an unused asset, narrowing a resource filter or optimizing an image. Compare baseline and candidate using the same packaging and target settings. Report absolute and percentage changes and identify any shifted cost, such as deferred downloads. Verify cold launch on relevant hardware, opening affected screens offline where promised, localization, and representative media quality. Run a negative fixture that removes a required resource and ensure your smoke checks fail.

Save the per-target sizes, category deltas, retained diagnostics and observable functionality results. Mark estimates and real distribution observations distinctly. Smaller download size alone does not establish faster launch or a smaller installed footprint.

References and rights

Original SkillDB instructions under LicenseRef-SkillDB-Content. References were checked 2026-11-13 and used for technical verification.

Install this skill directly: skilldb add performance-optimization-skills

Get CLI access →