How to share code using internal libraries
summary
Deezer describes how it shares Android/Kotlin code by extracting features into internal libraries: initially as source-code modules (which caused long rebuilds, e.g., two months to fix Android TV after breaking changes), then as compiled artifacts published to a private Nexus. An orchestrator script publishes all libraries under a single version and enforces a mono-repo automated pipeline with nightly snapshot builds and a special snapshot branch for testing bleeding changes; about 20–25 engineers touch these libs and 30–40% of code lives in them, reducing integration delay.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:40Constraints for shared code
- 9:45Source vs artifacts
- 14:28Library organization
- 21:21Monorepo adoption
- 24:13Publishing and automation
- 27:47Local development
- 32:49Documentation and releases
- 37:01Experience summary
- 46:38Q&A
related talks
30mSharing code among multiple projects: the case of internal libraries
43mLibrary Developer Confidential
22mSharing features between applications: a postmortem
26mArchitecting Your Android Library
37mAndroid Librarian's Guide: Building Robust Libraries a…
44mBuilding and Publishing Android Libraries the Missing Guide
32mWriting Android Libraries
33mTools of the Trade