Android Open-source repositories 101
summary
Recommends using Apache 2.0 license for permissive use with patent protection, automating dependency updates with Dependabot or Renovate, and running automated releases via semantic-release. Advises Jacoco test-coverage gates (block merges under a chosen threshold), SonarQube for static analysis, GitHub Actions for lint/tests, code-owners to enforce reviewers, and Fastlane for app deployment. Compose APIs must be single-purpose, expose a Modifier as the first optional parameter, and prefer small building-block composables.
AI-written summary · about
chapters (11)
- 0:00Android open-source intro
- 4:21Red vs blue ocean
- 8:14Licensing strategies
- 10:46Contribution guidelines
- 17:12Code style conventions
- 18:57Automating dependencies
- 21:09Code review & testing
- 24:45Release with semantic versioning
- 27:31Jetpack Compose best practices
- 33:36Kotlin tips for libraries
- 37:24Key open-source practices
related talks
37mAndroid Librarian's Guide: Building Robust Libraries a…
32mWriting Android Libraries
42mIngredients for a healthy codebase (en)
36mAndroid like a (reliable) Rock Star - All About Android Continuous Integration
38mCode Quality on Android - A grumpy old man's perspective
38mBuilding Android apps in 2022
30mAutoMobile
41mWrite once, ship multiple times