App size and bundle in 2026
Bigger app = fewer installs. Especially in regions with slow internet or expensive data. What to cut.
The download size is shown on every App Store and Google Play listing, and people read it. On a phone that's almost full, on a metered data plan or on a slow connection, a heavy app is easy to skip. Size also affects updates: if every update is large, users postpone it, and you end up supporting old versions longer. The good news is that most apps are bigger than they need to be for boring, fixable reasons.
Where the megabytes go
- Images and video. PNGs exported at several resolutions, uncompressed illustrations, onboarding videos bundled at a resolution far above what a phone screen needs.
- Fonts. Every weight as a separate file, full character sets for languages the app doesn't support.
- Third-party SDKs. Analytics, attribution, A/B testing, ads, chat widgets, crash reporting. Each brings its own code and sometimes its own dependencies. Apps often carry SDKs that nobody has looked at in a year.
- Native libraries. On Android, libraries compiled for several CPU architectures. In React Native and Flutter apps, the engine and native modules add to the baseline.
- Dead code and resources. Old screens, unused drawables, debug tools that slipped into release builds.
- Everything for everyone. All localizations and all device-specific assets shipped to every device.
Measure first
Don't guess. Both platforms show what users actually download:
- Android: the APK Analyzer in Android Studio shows what's inside a build, and Play Console reports download and install sizes for different device configurations.
- iOS: App Store Connect shows estimated download and install sizes per device after processing, and Xcode can export an app thinning size report for each device variant.
Keep the numbers from every release. A size regression is far easier to fix the week it appears than a year later.
What to do about it
- Use the platform delivery formats. With Android App Bundles, Google Play builds an APK for each device with only the resources, languages and architecture it needs. On iOS, App Thinning does the same for asset catalogs and architectures, so keep images in asset catalogs.
- Compress images properly. Use vector assets for icons and simple illustrations, WebP on Android, and run raster images through a proper compressor. Check whether every high-resolution illustration really has to be in the bundle.
- Move large media out of the binary. Onboarding videos, sample content and level packs can be downloaded after install from a CDN, or through Play Asset Delivery on Android and Apple's Background Assets framework on iOS. Show something useful while the download runs.
- Subset fonts to the glyphs and weights you use, or rely on the system font where the brand allows it.
- Audit SDKs. List every dependency, who owns it and which report it feeds. If two SDKs do the same job, keep one. This also helps startup time and shortens the privacy disclosures you have to maintain.
- Turn on shrinking. R8 with resource shrinking on Android, dead-code stripping and release optimization settings on iOS, tree shaking in cross-platform toolchains. Check that release builds actually use them.
- Split off rarely used features. Play Feature Delivery can install modules on demand. On any platform, rarely used admin features can live on the web instead.
Common mistakes
- Looking at the size of a universal build on a developer's machine instead of what a real device downloads.
- Optimizing images while a forgotten SDK weighs more than all the images combined.
- Streaming media without a fallback, so the first launch on a bad connection shows a blank screen.
- Treating size as a one-time cleanup. Without a check in the release process, it creeps back.
Set a size budget
There's no universal "right" size, and store thresholds for cellular downloads change over time, so check the current App Store and Google Play documentation. A practical rule: agree on a size budget for your app at the start, compare every release against it and treat a sudden jump as a bug. If your audience is in markets where mobile data is expensive, set the budget tighter.
Size problems usually build up during years of maintenance: SDKs accumulate, features get added and nothing gets removed. That's part of what we review under mobile app support, and we plan for it from the first build in Android and iOS projects.
Want us to look at why your app got so heavy? Reach us on Telegram or MAX.
Got a project on this topic? Tell us the task — we'll come back with an estimate and a schedule.
Message on Telegram → Message on MAX