Building libraries for the next 25 years

on YouTube ↗38m

" summary

Practical advice and concrete tradeoffs: a real-world Apollo Kotlin client shows why names should be memorable, why supporting Java vs JavaScript forces duplicate APIs, and why Builders vs data classes matters for evolving defaults and null/optional semantics. Publishing notes name Maven Central and pain points with multiple publish flows and Gradle plugins, and the recommended tooling includes binary-compatibility-validator to track ABI, careful deprecation with replaceWith, and treating alphas as usable for real feedback while avoiding breaking changes.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 3:59Naming for library identity
3. 6:03API design Java vs JavaScript
4. 9:33Kotlin features for libraries
5. 13:05Extension functions and Java interop
6. 15:56Error handling and type safety
7. 19:29Documentation and publishing
8. 25:31Breaking changes and versioning
9. 31:10API evolution and deprecation
10. 34:20Versioning schemes and pre-releases
11. 36:28Key takeaways

" related talks

• 31mTips for Library Development (from a Startup Developer)Lisa Wray · Android Makers 2018
• 29mLessons from a LibrarianZac Sweers, James Barr · Chicago Roboto 2020
• 43mLibrary Developer ConfidentialElliott Chenger · 360|AnDev 2018
• 41mBrick by Brick: Building Open Source librariesNicola Corti, Paolo Rotolo · Droidcon London 2023
• 42mEvolving your Kotlin API painlessly for clientsLeonid Startsev · KotlinConf 2023 Day 2
• 47mThe definitive guide to Android library developmentJeroen Mols · Android Makers 2022
• 37mAndroid Librarian's Guide: Building Robust Libraries a…Jaewoong · DroidKaigi 2025
• 01h 01mGuide to Destroying Codebases the Demise of Clever CodeGabor Varadi · Android Worldwide 2022