Tips for Library Development (from a Startup Developer)
summary
Advice centers on concrete rules and outcomes: pick a narrowly focused task that users can describe in one sentence, publish a Gradle artifact with copy-paste dependency and example and sensible defaults, prefer composition over inheritance and delegation, and run tests on CI (CircleCI Bitrise Travis) so pull requests get a green check. Expect modularity, community PRs, and occasional surprising gains like collaborations (Apollo GraphQL for Android) and also the real risk that a library dies when ownership or job changes.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:00COMMUNITY HELP AKA OTHER PEOPLE WRITE YOUR CODE FOR FREE
- 13:53FEATURE REQUESTS
- 16:51HONESTY
- 20:07TESTING
- 21:42OWNERSHIP
- 24:10COMPETITION
- 26:24DEPRECATION
related talks
43mLibrary Developer Confidential
38mBuilding libraries for the next 25 years
33mGuide for lazy developer
01h 17mDevelopment strategies: You've written a library - now what?
42mHow to Build a Library People Will Use
01h 10mDeveloping a Library for Mobile Apps
47mThe definitive guide to Android library development
01h 19mNavigating the development and evolution of a library