Library Developer Confidential
summary
Extracted how-to: moving reusable code into a library cuts incremental work (example slide shows a 14s all-in build split into two 7s builds where subsequent changes rebuild only the app because the library is up‑to‑date), by enabling build cache (Gradle 3.5+ / AGP support). Use Gradle composite builds instead of shipping AARs to keep sources debuggable (note: composite mode won’t accept AAR artifacts). Publish with mavenPublish to mavenLocal for CI or local testing. Avoid pinned transitive conflicts with a deferred responsibility pattern (app supplies image loader). Use manifest placeholders for content‑provider authorities and rely on resource 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
44mBuilding and Publishing Android Libraries the Missing Guide
39mThe definitive guide to Android library development
36mNasty Dependencies: Surviving and fixing bugs in 3rd-party libra…
31mTips for Library Development (from a Startup Developer)
37mAndroid Librarian's Guide: Building Robust Libraries a…
30mSharing code among multiple projects: the case of internal libraries
53mHow not to fuckup with building SDK and make clients happy