Alright, let's break this down based on your build report and practical Unity optimization tricks for Android App Bundles (AABs). First off, looking at your stats, the massive standout is Included DLLs taking up 13.3MB (66.4% of your user assets)—that's where you'll get the biggest size reductions right off the bat. Let's walk through actionable steps, then tackle whether hitting the 10MB target is feasible.

Top Optimization Focus: Included DLLs #

This is your biggest opportunity to cut size:

• Crank up Managed Stripping: Head to Player Settings > Player > Optimization > Managed Stripping Level and set it to High or even Use micro mscorlib (if your code doesn't depend on full .NET framework features). This linker will strip out every unused class, method, and property from your DLLs. Just make sure to test thoroughly after—some reflection-heavy code might break if the linker removes classes it thinks are unused.
• Audit Third-Party DLLs: Go through every plugin DLL in your project. Are you using all features from libraries like Newtonsoft.Json, Firebase, or analytics tools? If not, swap them for lighter alternatives (e.g., use Unity's built-in JsonUtility instead of Newtonsoft if your use case is simple) or only include the specific parts you need (many plugins let you cherry-pick modules).
• Switch to IL2CPP: In Player Settings > Player > Configuration > Scripting Backend, switch from Mono to IL2CPP. This compiles your C# code to native machine code, which not only improves performance but also lets the linker strip more unused code. It also enables split APKs for different CPU architectures (ARM64, x86), so users only download the binaries their device needs.

Optimizing Other Asset Categories #

While DLLs are the main target, you can trim other assets to add up to meaningful savings:

• Textures: Your textures are only 1.4MB, but you can still squeeze more:
  • Use Android-specific compressed formats: In Texture Import Settings, set Compression to Android (ETC2) (for devices running Android 4.4+) or ASTC (for newer, high-end devices). Adjust the compression quality slider to find the sweet spot between quality and size.
  • Resize to minimum needed resolution: If a texture is used on a UI element that never goes larger than 512x512, don't import it as 1024x1024.
• Scenes & Other Assets: Your "Levels" (1.9MB) and "Other Assets" (1.8MB) are next. Use Unity's Window > Analysis > Memory Profiler to find unused prefabs, materials, or GameObjects in your scenes and project. Delete anything that isn't referenced in your final build. For scenes, use the built-in Scene Optimization tool to clean up unused components.
• Sounds: Your sounds are small (152.2KB), but convert them to OGG Vorbis format instead of WAV. In Audio Clip Import Settings, set Compression Format to Vorbis and lower the bitrate if quality allows—most users won't notice a difference for in-game sound effects or background music.
• Scripts: Delete any unused scripts in your project. Even small scripts add up, and unused ones can bloat your DLLs slightly.

AAB-Specific Tricks to Shrink Size #

Android App Bundles have built-in tools to reduce what users actually download:

• Enable Split APKs: When building, make sure Build App Bundle (Google Play) is checked in Build Settings. AABs automatically split your app into device-specific APKs—so a user with an ARM64 device won't download x86 libraries, and a device that supports ASTC textures won't get ETC2 ones. This drastically reduces the size users see in the Play Store.
• Turn on App Size Optimization: In Player Settings > Publishing Settings > Android > App Bundle Options, enable Optimize App Size. This lets Google Play apply extra optimizations, like removing unused resources and compressing assets further during the publishing process.
• Dynamic Delivery for Non-Critical Assets: If you have assets that aren't needed at launch (e.g., optional levels, cosmetic skins), use Unity's Addressables or Google Play's Dynamic Feature Modules to deliver them on demand. This keeps your initial bundle size tiny.

Can You Get Under 10MB? #

It's possible, but it depends on how much bloat you can cut:

• Your current uncompressed user assets are 20MB, and your compressed APK is 33.4MB (note the complete build size of 109MB is uncompressed). To hit a compressed AAB (or resulting split APK) under 10MB:
  • You'll need to slash the Included DLLs from 13.3MB to roughly 3-4MB. Aggressive stripping, removing unnecessary third-party libraries, and switching to IL2CPP should get you most of the way here.
  • Trim other assets to the bone: get textures under 500KB, sounds under 50KB, levels/other assets under 1MB total.
• If your app is a simple utility or minimal game without heavy SDK dependencies (like ads, analytics, or cloud services), this is achievable. If you're using large SDKs, you'll need to either replace them with lighter alternatives or remove them entirely to hit the 10MB mark.

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