Hey there, let's work through your app size problem together—since your 800MB Android app is mostly made up of audio files in the Assets folder, I'll break down targeted solutions for your case first, then cover general strategies for publishing large apps on Google Play.

1. 迁移音频到Play Asset Delivery #

This is the most tailored solution for your audio-heavy app, since Google Play Asset Delivery is built specifically for large resource files like audio, video, or 3D assets. Here's how to do it:

• Split your audio into asset packs: Instead of keeping all audio in the main Assets folder, organize them into separate asset packs (e.g., "main-audio" for startup music, "level-audio" for game stage tracks, "sound-effects" for SFX).
• Choose delivery modes based on need:
  • Install-time delivery: For audio that's required as soon as the app opens (like a welcome theme)—these packs install alongside the main app.
  • Fast-follow delivery: For audio that's used frequently but not immediately (like common sound effects)—these download in the background right after the main app installs.
  • On-demand delivery: For audio that's only needed when the user triggers a specific action (like a hidden level's soundtrack)—your app can request these packs programmatically when needed.
• Configure your project:
  In your module-level build.gradle file, declare each asset pack and set its delivery mode. Example snippet:

  assetPacks = [":main-audio", ":level-audio"]
  

  For each asset pack module, set the delivery mode in its build.gradle:

  playAssetDelivery {
      deliveryType = "on-demand" // or "install-time" / "fast-follow"
  }
  

• Build and upload an Android App Bundle (AAB): Google Play will handle hosting and distributing these asset packs to users automatically.

2. Compress your audio files first #

Before even splitting assets, you can reduce the total size significantly by optimizing your audio:

• Convert uncompressed formats (like WAV) to compressed ones supported by Android: OGG is great for audio (smaller size than MP3 with similar quality), while MP3 works too for broader compatibility.
• Lower the bitrate or sample rate if quality allows: For example, if your audio is currently 320kbps MP3, dropping it to 128kbps can cut size in half without noticeable quality loss for most app use cases (like background music or sound effects).
• Trim any unused audio segments: Remove silence or unused tracks that accidentally made their way into your Assets folder.

If you need broader strategies beyond audio-specific fixes, here are the standard methods to bypass Google Play's 100MB APK limit:

1. Use Android App Bundle (AAB) instead of APK #

This is Google's recommended approach for all apps now. Unlike traditional APKs (which have a 100MB upload limit), AABs have no hard size limit. When you upload an AAB, Google Play generates optimized Split APKs for each user's device—they only download the parts they need (e.g., the correct CPU architecture, screen density resources), which drastically reduces the actual download size for end users.

2. Play Feature Delivery #

For non-core app features (like a premium content module, extra tools, or optional game modes), package them into feature modules. Users can download these modules on demand, or you can set them to install automatically after the main app. This keeps your core app size small while still offering full functionality.

3. APK Expansion Files (OBB Files) #

If you can't use AAB for some reason, this is the legacy but still supported option. You can attach up to two OBB files to your APK:

• A main OBB file (main.<package-name>.obb) for essential large resources, max 2GB.
• A patch OBB file (patch.<package-name>.obb) for updates or additional content, max 2GB.
  When users download your app, Google Play automatically installs these OBB files to a specific directory on their device. Your app will need to read from this directory instead of the Assets folder—you can use Android's StorageManager API to access them.

4. Optimize all app resources #

• Image optimization: Convert PNG/JPG files to WebP (Android supports it natively, and it's 25-35% smaller with same quality). Use Android Studio's Convert to WebP tool for this.
• Remove unused resources: Run Android Studio's Analyze > Inspect Code to find and delete unused layouts, strings, or drawables. Enable R8/ProGuard to strip unused code and shrink your app's size further.
• Dynamic resource loading: Host non-critical resources (like rare audio clips or infrequently used images) on your own server, and download them to the device's internal storage only when the user needs them.

内容的提问来源于stack exchange，提问作者Spider