Episode 202: AndroidX, Gradle and Metalava

This podcast episode provides valuable insights into AndroidX and its collaboration with Gradle. It explores the impact of AndroidX on the Gradle build system, discussing configuration caching, build caching, and remote cache. The speakers discuss optimization strategies for Gradle builds and tasks, focusing on stability, continuous improvement, and collaboration with other teams. They also address the challenges faced in library development and the solutions implemented. Additionally, the episode covers the evolution of tools used in library development, including Metalava for API review and static analysis. The importance of context-specific static analysis checks is also highlighted. Overall, this episode offers a comprehensive overview of the features, challenges, and collaborative nature of AndroidX and Gradle. Takeaways • AndroidX is a "super user" of the Gradle build system, pushing it forward and making frequent requests and complaints. • Configuration caching is recommended for faster build times, and most app developers will not encounter compatibility issues with major plugins. • Local cache in Gradle allows reusing previous build results and is especially helpful when switching branches frequently or iterating on the same work. • Remote caching in Gradle requires a server component and allows storing and retrieving build results from a remote location. Google Cloud Platform buckets can be used as a backend for remote caching in AndroidX. • Optimization strategies for Gradle builds include continuous builds, fetching upstream dependencies from the CI cache, and handling remote dependencies. • The speakers emphasize stability in AndroidX and Gradle, ensuring that issues are caught and fixed before impacting users. • Collaboration with other teams is crucial for driving continuous improvement in AndroidX and Gradle, including proactive participation in testing and pushing for fixes in plugins. • Challenges in library development include conflicts with file names, Maven Central requirements, maintaining binary compatibility, and using custom Gradle code. • Metalava is a tool used for API review and static analysis, ensuring compatibility and preventing breakages in libraries. • Custom lint checks and collaboration between different tools and plugins contribute to improving the user experience and overall app performance. • The Android development ecosystem thrives on collaboration, sharing knowledge, and drawing inspiration from each other's projects and experiences.