D8 now default dex compiler
Faster, smarter app compilation is always a goal for the Android tools teams. That’s why we previously announced D8, a next-generation dex compiler. D8 runs faster and produces smaller .dex files with equivalent or better runtime performance when compared to the historic compiler – DX.
We recently announced that D8 has become the default compiler in Android Studio 3.1. If you haven’t previously tried D8, we hope that you notice better, faster dex compilation as you make the switch.
D8 was first shipped in Android Studio 3.0 as an opt-in feature. In addition to our own rigorous testing, we’ve now seen it perform well in a wide variety of apps. As a result, we’re confident that D8 will work well for everyone who starts using it in 3.1. However, if you do have issues, you can always revert to DX for now via this setting in your project’s gradle.properties file:
If you do encounter something that causes you to disable D8, please let us know!
Our goal is to ensure that everyone has access to a fast, correct dex compiler. So to avoid risking regressions for any of our users, we’ll be deprecating DX in three phases
The first phase is intended to prevent prematurely deprecating DX. During this phase, DX will remain available in studio. We’ll fix critical issues in it, but there won’t be new features. This phase will last for at least six months, during which we’ll evaluate any open D8 bugs to decide if there are regressions which would prevent some users from replacing DX with D8. The first phase won’t end until the team addresses all migration blockers. We’ll be paying extra attention to the bug tracker during this window, so If you encounter any of these regressions, please file an issue.
Once we’ve seen a six month window without major regressions from DX to D8, we’ll enter the second phase. This phase will last for a year, and is intended to ensure that even complex projects have lots of time to migrate. During this phase, we’ll keep DX available, but we’ll treat it as fully deprecated; we won’t be fixing any issues.
During the third and final phase, DX will be removed from Android Studio. At this point, you’ll need to use a legacy version of the Android Gradle Plugin in order to continue to build with DX.
Gurupriyan is a Software Engineer and a technology enthusiast, he’s been working on the field for the last 6 years. Currently focusing on mobile app development and IoT.