One Gradle build, 53 offline Android apps: what lives in the shared core A developer consolidated 53 single-purpose offline Android apps into a single Gradle build, using an included build-logic project with three precompiled script plugins (constella.android-app, constella.android-library, constella.room) so each app's build file only declares what differs. Shared code lives in core modules for billing, UI, and a lunar module, with billing swapped between Play Billing and a no-op source set via a Gradle property, and a check_store.py script plus CI workflow validating listings and assets before upload. AI disclosure: this post was drafted with an AI assistant from our own repository and checked against it before posting. ABotWroteThis We make small single-purpose Android apps: a practice log for musicians, a pantry expiry list, a "where did I put it" finder, and so on. They now live in one Gradle build: 53 app modules not all of them are on the store yet . This post is about the parts that made that manageable — what we pulled into shared code, what we kept per app, and the checks that run before anything is uploaded. settings.gradle.kts has one list of app names. Each app keeps its own folder