The definitive guide to Android library development
summary
Walks through creating an Android library by adding a library module to an app, explains that an AAR omits transitive deps so a POM must list them, and warns that publishing to Maven Central requires PGP signing and is tedious. Demonstrates a multi‑module SDK failing at runtime due to an AGP four‑year bug that omits submodule classes, compares fixes: publish submodules, build a fat AAR via embed (fragile, bigger), or keep a single module. Covers transitive conflicts (OkHttp v3/v4, package rename workaround), resource exposure, and using Kotlin API dump/check plus consumer ProGuard rules.
AI-written summary · about
chapters (9)
- 0:00Introduction to Android libraries
- 1:04Building your first Android library
- 6:42Publishing to Maven Central
- 7:02Understanding transitive dependencies
- 10:42Modularizing your SDK
- 19:16Should you modularize your SDK?
- 20:01Transitive dependency conflicts
- 30:13Tips and tools for libraries
- 38:39Summary and closing
related talks
47mThe definitive guide to Android library development
44mBuilding and Publishing Android Libraries the Missing Guide
37mAndroid Librarian's Guide: Building Robust Libraries a…
43mLibrary Developer Confidential
34mSuccessfully publishing a tested, upgradeable and documented Open Source Library
22mBest Practices When Building Mobile SDKs
36mNasty Dependencies: Surviving and fixing bugs in 3rd-party libra…
38mBuilding libraries for the next 25 years