Who Is That API For? Practical User‑Focused Techniques for Android Library Design
summary
An Android auth library originally leaked internal DI, instance-management and navigation assumptions which broke consuming apps. The rebuild enforces an Explicit API mode, exposes a minimal public constructor (token-only) while keeping testable internal constructors, hides third-party types using module API vs implementation to avoid extra dependencies, wraps UI to work with or without Navigation Compose encapsulation, and adds KDoc, runnable sample apps and CI to make the library reusable.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 5:47Encapsulation basics
- 10:03Constructor design
- 15:08Hiding module deps
- 19:47Tech stack selection
- 23:41Feature vs freedom
- 27:40User-focused docs
- 33:21Sample app testing
- 40:28Summary
related talks
47mThe definitive guide to Android library development
32mWriting Android Libraries
25mEverything is an API
26mArchitecting Your Android Library
29mDon't reinvent the wheel, use libraries: Modern Android Stack
40mModularizing Android Applications
48mArchitecture Components – Behind the Scenes
44mBuilding for Developers