OSS Tanbou

use independently released Jetpack libraries for Android UI, architecture, data, and background work across platform versions

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
6,103
Primary language
Kotlin
License
Apache-2.0
Repository last updated
Oct 3, 2026
On this page

Overview

AndroidX is the set of androidx.* Jetpack libraries released independently from Android platform APIs. The monorepo contains libraries such as Activity, AppCompat, Compose, Lifecycle, Navigation, Room, Paging, DataStore, and WorkManager, while applications consume individual artifacts from Google Maven.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Use Jetpack libraries independently of Android platform releases

AndroidX artifacts are unbundled from platform APIs and can ship compatibility fixes and new capabilities more frequently. Applications select only the Google Maven artifacts they need.

Sources: [1][4]

Cover UI, architecture, data, and background work in one ecosystem

The source tree includes Activity, AppCompat, Compose Runtime, Lifecycle, Navigation, Paging, Room, DataStore, WorkManager, and many other library groups.

Sources: [1][2]

Build, test, and publish libraries module by module

Source developers can run Gradle tasks such as assemble, test, and publish against individual modules instead of rebuilding the entire monorepo.

Sources: [3]

Best fit

Fits Android apps that want common capabilities decoupled from OS versions

It is the standard ecosystem for compatibility layers, architecture components, UI toolkits, databases, navigation, and background work in Android applications.

Sources: [1]

Before adoption

There is no single release version for the whole repository

AndroidX libraries maintain independent stable, RC, beta, and alpha versions. Use the official version table and release notes per artifact rather than treating a repository commit as an app dependency version.

Sources: [4]

AOSP androidx-main is the source of truth and GitHub accepts only a subset of contributions

The GitHub repository is an official mirror with PR support for selected library groups. Approved changes are mirrored into AOSP Gerrit, and the contribution guide states that AOSP is the single source of truth.

Sources: [2][3]

Source development expects a large checkout and dedicated toolchain

Full AndroidX development uses Repo on androidx-main and the onboarding guide estimates about 60 GB for a clean checkout or 160 GB for a fully built checkout with history. The GitHub playground workflow also requires JDK 21 plus Android SDK/NDK, and Windows is unsupported.

Sources: [3][2]

Official sources

  1. [1]AndroidX README(2026-10-03)
  2. [2]AndroidX GitHub contribution guide(2026-10-03)
  3. [3]AndroidX onboarding(2026-10-03)
  4. [4]AndroidX versions(2026-10-03)
  5. [5]AndroidX Apache-2.0 license(2026-10-03)
Supplemental curator note

Normal Android apps should consume the required AndroidX artifacts from Google Maven rather than depending on this repository directly. For source work, remember that libraries have independent release cycles and AOSP androidx-main remains the source of truth.

Try it in 3 steps

  1. 1

    Clone the AndroidX source with a blob filter

    This path is for source contribution to supported libraries. Normal applications should consume Google Maven artifacts instead.

    git clone --filter=blob:limit=10M https://github.com/androidx/androidx.git && cd androidx
  2. 2

    Configure JDK 21 and the Android SDK

    The GitHub contribution workflow expects JDK 21, an Android SDK, and NDK/CMake where required.

    export JAVA_HOME=/path/to/jdk21 && export ANDROID_SDK_ROOT=/path/to/android-sdk
  3. 3

    Open the Room playground in Android Studio

    Room is one supported playground example; check CONTRIBUTING.md for the allowed project set and workflow.

    cd playground-projects/room-playground && ./gradlew studio
Check the official README

Growth

Growth trends · Last 30 days

6,103 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
2,109
Open PRs
60

Development activity is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • android
  • jetpack
  • library
Stars
6,103
Forks
1,387
Watchers
135
Open issues
0
Contributors
262
Owner type
Organization
Primary language
Kotlin
License
Apache-2.0
Repository last updated
Oct 3, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?