App Size

Definition

App Size refers to the download size of an app, a direct factor in Conversion Rate (especially in emerging markets with metered connections) and an indirect Ranking Factor. Apple's cellular download limit is 200MB; Google warns at 150MB+. Smaller apps achieve 5–15% higher conversion rates in markets with slow/expensive data (India, Southeast Asia, Africa). App Thinning (Apple) and Android App Bundle (Google) reduce download size by delivering only device-specific assets.

How It Works

Apple App Store

Download Size Limits:

• Cellular download: 200MB maximum (increased from 150MB in iOS 13)
• WiFi: No limit
• Over-the-air update: 150MB limit (users prompted to use WiFi for larger updates)
• Impact: Apps >200MB cannot be downloaded over cellular; requires WiFi warning

App Thinning:

• Automatic slicing of app binaries by architecture (ARM64, ARM64e) and screen resolution
• Device receives only necessary assets for its hardware
• Reduces download by 20–40% on average
• Example: 100MB app → 65MB download on iPhone 12 (A14 Bionic, 2x resolution)

Asset Delivery (iOS 14+):

• On-Demand: Download after install; large assets (games, media)
• Install-Time: Required for app launch; prioritized in initial download
• Fast-Follow: Downloaded within 24 hours of install
• Example: Game base 50MB + on-demand DLC 500MB → 50MB initial download

App Bundle Format:

• .ipa (binary) → iOS 14.5+ supports .zip with app clips and on-demand resources
• Smaller initial download; full app downloaded only when needed

Google Play Store

Download Size Limits:

• No hard limit; Google warns at 150MB+ ("Attention: This app is very large")
• Recommendation: Keep under 100MB for emerging markets
• Very large apps (>1GB) require Android App Bundle to reduce download

Android App Bundle (AAB, Mandatory since Aug 2021):

• Google Play auto-generates optimized APKs per device configuration
• Device receives only necessary assets (language, screen density, CPU architecture)
• Reduces download by 35–50% vs. universal APK
• Example: Universal APK 500MB → Device-specific 200MB download

Asset Delivery:

• Install-time: Downloaded with app
• Fast-follow: Downloaded within 24 hours (games, libraries)
• On-demand: User-triggered download (large assets)
• Conditional delivery: Download based on device capabilities (VR, high-end graphics)

Compression:

• Google Play auto-compresses APKs; developers don't manage compression
• WebP format for images (20–30% smaller vs. PNG/JPG)

Amazon Appstore

Download Size Limits:

• No hard limit; smaller apps preferred for emerging markets
• Android App Bundle not required; standard APK acceptable
• Similar to Google Play (100–150MB+ warning)

Formulas & Metrics

Download Size Impact on CVR:

• <50MB: Baseline CVR (100%)
• 50–100MB: CVR -5% to -10% (in emerging markets)
• 100–200MB: CVR -15% to -25% (in emerging markets, especially metered connection)
• >200MB: CVR -30% to -50% (cellular impossible on Apple; major barrier)

Typical App Sizes by Category:

• Casual games: 50–150MB
• Puzzle games: 30–80MB
• 3D games: 500MB–2GB
• Social apps: 100–200MB
• Productivity: 30–100MB
• Utilities: 10–50MB

Thinning Savings:

• Apple: 20–40% reduction (asset slicing + binary optimization)
• Google: 35–50% reduction (language + density slicing + architecture filtering)

Best Practices

Size Optimization Strategy

1. Asset Optimization:

- Use WebP for images (20–30% smaller than PNG/JPG)

- Compress video to H.265 codec (25–50% smaller than H.264)

- Preload minimal assets on install; defer non-critical content

- Remove unused assets (images, sounds, libraries)

1. Code Optimization:

- Remove unused dependencies (audit package managers)

- Use dynamic frameworks instead of static (iOS)

- Strip debug symbols from release builds

- Minify JavaScript/assets before bundling

1. On-Demand Delivery:

- Games: Base game 30–50MB + optional DLC/levels on-demand

- Media Apps: Base 50MB + content packs user-selectable

- 3D/AR: Core app 100MB + high-quality assets on-demand

- Reduces install friction; improves CVR 10–20%

1. Regional Strategy:

- India/Southeast Asia: Target 30–80MB for metered connections

- Developed markets (US, EU): More lenient; 100–200MB acceptable

- China: 100MB target (mobile data metering common)

- Africa: <50MB preferred (slowest networks, most expensive data)

Monitoring & Testing

1. Size Audit Pre-Release:

- Xcode (Apple): Build + Archive → Check download size estimate

- Play Console (Google): Upload AAB → Check size estimate per device

- Target: Final download <100MB for emerging market optimization

- Test on 2G/3G networks to validate user experience

1. Post-Release Monitoring:

- Track download completion rates (% starting vs. completing download)

- Correlate download size with conversion by region

- Monitor user reviews mentioning app size ("too large," "won't fit")

- Conduct quarterly audits (trim unused assets each release)

Examples

Example 1: Casual Puzzle Game (Size Optimization)

• Initial Size: 250MB (art-heavy, all languages, high-res assets)
• Optimization:

- WebP conversion: -40MB

- Language packs on-demand: -50MB

- Remove duplicate assets: -20MB

- Compress audio: -15MB

- Final Size: 125MB

• Impact: CVR improved +8% in India (metered data users); +3% global average
• Result: 500K additional installs over 6 months from size improvement

Example 2: 3D Game (On-Demand Delivery)

• Initial Design: 1.2GB universal APK (all levels, characters, graphics)
• Restructured:

- Base game: 150MB (first 5 levels, essential assets)

- Level packs 1–10: 200MB (on-demand, user-selectable)

- High-res graphics pack: 500MB (optional, on-demand)

• Impact: Initial download 150MB → CVR +15%; Day 1 retention +5% (smaller initial commitment)
• Result: 2M Day 1 installs (up from 1.5M with 1.2GB version)

Example 3: Social App (Market-Specific Optimization)

• Global Size: 180MB (all regions, all languages)
• Optimization by Region:

- India: 45MB (lite version, compressed assets, language-specific)

- US/EU: 180MB (full version)

- Brazil: 90MB (balanced)

• Impact: India CVR +20%, Brazil CVR +12%, US/EU CVR +2%
• Revenue: India region revenue +40% (more installs offset by lower ARPU)

Dependencies

Influences

• Conversion Rate — Smaller app size boosts CVR 5–30% in emerging markets
• Ranking Factors — Small app size (freshness, user satisfaction) may boost organic ranking
• user experience — Large apps cause poor perception; smaller → better reviews

Depends On

• App Thinning (Apple) — Automatic size reduction per device
• Android App Bundle (Google) — Mandatory; auto-generates device-specific builds
• Asset Management: Quality assets required; compression must not degrade UX
• Localization: Multi-language support increases size; on-demand recommended

Platform Comparison

Related Terms

• Conversion Rate — App size directly impacts CVR, especially emerging markets
• user experience — Large apps perceived as clunky; size affects perception
• Ranking Factors — App size contributes to quality score indirectly
• Localization — Multi-language increases size; on-demand delivery mitigates
• Android App Bundle — Google's size reduction mechanism (mandatory)
• App Thinning — Apple's size reduction mechanism (automatic)

Sources & Further Reading

• Apple App Thinning Guide: https://developer.apple.com/library/archive/qa/qa1795/_index.html
• Apple Asset Delivery Guide: https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/On_Demand_Resources_Guide/
• Google Play App Bundle Guide: https://developer.android.com/guide/app-bundle
• Google Play Asset Delivery: https://developer.android.com/guide/app-bundle/asset-delivery
• "App Size Impact on CVR in Emerging Markets": Case studies from Sensor Tower, App Annie
• WebP Documentation: https://developers.google.com/speed/webp

---

Last updated: 2026-04-08