.NET 11, CoreCLR and Google Play’s DEX Optimization: What .NET MAUI Developers Need to Know
Google Play is introducing more visibility around Android application quality, including 16 KB page-size support and DEX code optimization . For .NET MAUI developers, this raises an interesting question: Does moving to .NET 11 and CoreCLR automatically improve the DEX optimization score reported by Google Play? The short answer is: Not directly. .NET 11 brings important improvements to .NET MAUI…
Google Play is enhancing visibility of Android application quality with 16KB page-size support and DEX code optimization. This raises a question for .NET MAUI developers: does moving to .NET 11 and CoreCLR automatically improve the DEX optimization score reported by Google Play? The answer is no, it doesn't. While .NET 11 brings improvements to .NET MAUI Android applications, such as CoreCLR, ReadyToRun, and improved trimming, Google Play's DEX optimization metric is primarily related to the Android DEX pipeline and should be evaluated separately from .NET runtime optimization.
CoreCLR, ReadyToRun, and IL trimming in .NET 11 are different from Google's DEX optimization metrics. CoreCLR operates on the .NET runtime side, while R8 (also known as Code Optimizer) operates on the Android/DEX side. Therefore, upgrading a MAUI application to .NET 11 does not automatically improve the DEX optimization score reported by Google Play.
Google Play measures DEX optimization based on factors like DEX code optimization, code shrinking, and code obfuscation, with a minimum threshold of 25% optimization. This metric is separate from aspects like target SDK 64-bit support, 16KB page-size support, .NET trimming, CoreCLR, and ReadyToRun.
16KB page-size support is related to native libraries and concerns compatibility with devices using 16KB memory pages, while DEX optimization concerns classes.dex, classes2.dex, classes3.dex, etc. An application can have both 16KB page-size support and DEX optimization.
.NET 11 may potentially improve application size due to improvements in Android trimming, including more effective removal of unused code. However, application size and DEX optimization are different measurements.
To address low DEX optimization scores, MAUI developers should first understand what Google Play is measuring. If the Play Console reports low DEX Code Optimization, they can inspect the actual Android App Bundle and calculate the total DEX size.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
