- Jetpack
- == libraries + tools + guide /
- help you
- follow best practices,
- reduce writing boilerplate code,
- simplify complex tasks
- help you
- contains
androidx.*package libraries /- unbundled | platform APIs ->
- backward compatibility
- updated MORE frequently than the Android platform
- unbundled | platform APIs ->
- see Android Jetpack landing page
- official AARs and JARs binaries -- are distributed through -- Google Maven
- == libraries + tools + guide /
- For contributions via GitHub, see the GitHub Contribution Guide.
- contributions workflow -- via -- GitHub
- experimental
- projects / accept contributions
- follow the code review etiquette.
- TODO:
- Bug fixes - needs a corresponding bug report in the Android Issue Tracker
- Each bug fix is expected to come with tests
- Fixing spelling errors
- Updating documentation
- Adding new tests to the area that is not currently covered by tests
- New features to existing libraries if the feature request bug has been approved by an AndroidX team member.
We are not currently accepting new modules.
- see onboarding docs
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
- After you run repo upload, open r.android.com
- Sign in into your account (or create one if you do not have one yet)
- Add an appropriate reviewer (use git log to find who did most modifications on the file you are fixing or check the OWNERS file in the project's directory)
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal and prebuilts/androidx/external directories in your checkout. All the dependencies in these directories are also available from google(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.