Library Developer Confidential
summary
Describes concrete library practices: enabling Gradle build cache (Gradle 3.5 / AGP 3.0) to avoid rebuilding unchanged modules, using Gradle composite builds instead of committing AARs to repos, publishing artifacts with the mavenPublish flow to mavenLocal for local testing, and generating POMs so dependencies resolve. Shows runtime patterns: defer heavy dependencies via an interface (deferred responsibility), use manifest placeholders for unique content provider authorities (applicationId), and rely on resource ID overriding for app-specific branding.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:03Anatomy of an AAR
- 11:15Single Project
- 11:49Settings.gradle
- 12:25Build.gradle
- 13:12Multi-Project
- 19:38Gradle Composite Project
- 22:59Maven Dependency Naming Convention
- 27:13Local Maven Repo
- 39:20Overriding IDs
related talks
47mThe definitive guide to Android library development
26mArchitecting Your Android Library
02h 49mGradle: Give Your Build Some Love and It Will Love You Back!
44mBuilding and Publishing Android Libraries the Missing Guide
37mAndroid Librarian's Guide: Building Robust Libraries a…
40mModularizing Android Applications
32mWriting Android Libraries
01h 15mKeeping growing software projects under control with Gradle