# Habitica for Android closed its pull request intake, and that is the first fact in its README > habitica-android is the GPL-3.0 native Android client for Habitica, a Kotlin codebase with a companion wearos module, fastlane releases and a Firebase based build configuration. As of 2026-08-04 the project has paused acceptance of code contributions, and the README states a separate policy banning AI-generated code. **HabitRPG/habitica-android** — Native Android app for Habitica - Repository: https://github.com/HabitRPG/habitica-android - Stars: 1,835 · Forks: 597 - Language: Kotlin - License: GPL-3.0 - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/habitrpg-habitica-android ## The first section is a pause notice, followed by an AI code ban Most READMEs open with a project description. This one opens with two policy sections that change how anyone should approach the repository. The first states that public pull request submissions were paused as of August 4, 2026, and gives the reason: changes in the tech landscape and in how the player base interacts with Habitica on various platforms. The decision described is to pause acceptance of code based contributions, referred to as Blacksmith tiers, and the README states the codebase will remain open source and publicly visible. Details are on the project wiki. The second section bans a specific class of contribution. The repository prohibits the submission of code generated by large language models, AI coding assistants or automated generation tools, requires all code to be authored entirely by humans, and says AI assisted commits will be rejected during pull request review. Both notices sit above the project description, which tells you where this repository sits in its own lifecycle. Read in combination, they describe an actively shipped application whose code is visible but not currently a target for outside patches. The last push was on 2026-10-05 and releases continue: 4.10.2 in July 2026, 4.10.3 in August, and 4.10.5 in September. ## A Kotlin codebase with a Wear OS module sharing the build Habitica is described as an open source habit building program that treats your life like a role playing game: level up as you succeed, lose HP as you fail, earn money to buy weapons and armor. This repository holds the Android native application for it, and the app is also distributed through Google Play under com.habitrpg.android.habitica. The primary language is Kotlin, and the README states the project follows the Android Kotlin Style Guide. The repository topics list coroutines, java alongside kotlin, realm and wearos, which describes the stack in shorthand: a coroutine based Kotlin app with a Realm database and a Wear OS companion. The layout shows two applications built from one tree. Habitica/ is the phone app and wearos/ is the watch app. Above them sit common/ and shared/ directories, plus build-logic/ for Gradle convention plugins and build.gradle.kts with settings.gradle.kts, so the module structure is defined in Kotlin build scripts rather than Groovy. Detekt is configured, with detekt.yml and a detekt_baseline.xml beside it. The baseline file is the interesting part: it records the suppressions needed to make static analysis pass on an existing codebase, which is the usual arrangement when analysis is introduced after the code already exists. An .editorconfig and a .run/ directory at the root cover formatting and IDE run configurations. ## Building requires your own Firebase project and two config files The build instructions are concrete, which makes this repository genuinely reproducible for a developer, at the cost of a Firebase account and a few manual steps. Two config files are created by copying the shipped examples: habitica.properties.example becomes habitica.properties, and habitica.resources.example becomes habitica.resources. The README notes that the example properties file is the default production configuration for habitica.com, and that you must change the values if you intend to run against a local Habitica server. The next requirement is google-services.json, which does not ship with the repository. The instructions are a numbered walkthrough of the Firebase console: register or log in, create a project called Habitica, then create two apps in it, one for com.habitrpg.android.habitica and one for com.habitrpg.android.habitica.debug. Creating each app generates its own google-services.json, and you are told to download the file from the second app and place it in both the Habitica directory and the wearos directory. The two application IDs are the reason there are two apps. Android distinguishes a debug build from a release build by application ID, so a debug variant with its own Firebase registration keeps push notifications and analytics separate. Once the files are in place, Android Studio syncs the Gradle files and you run the app. The README notes you can skip the verification steps at the end of the Firebase app creation wizards. ## How releases work, and why pull requests wait The contribution section explains the release process with a candour that is rare in project documentation. Major mobile releases are organised by Milestones labelled with the release number. An issue tagged Help Wanted is one the maintainers think would be acceptable for a contributor to work on, and they commit to answering questions on those. An issue without the tag means staff will handle it when they have availability. The reason for that distinction is staffing: the mobile team consists of one developer and one designer, for both Android and iOS. They alternate between platforms, so while they work on one, the other is on hold. A pull request submitted while they are on the other platform is assigned to the next Milestone and reviewed when they return. The README acknowledges this means waits for review and for answers. For releases themselves, the project uses fastlane, with a fastlane/ directory at the root, and signingrelease.properties.template as the template for release signing configuration. store_strings.xml and a translations/ directory hold the localised store copy. version.properties is where the version number lives, and Gemfile and Gemfile.lock at the root indicate Ruby tooling alongside Gradle. Users are pointed at the releases page for changelogs, and told that watching the repository on GitHub produces an email whenever a release is published. ## What the repository tells you about ownership and scope A few files describe the boundaries of this project. The README states this repository is related to the Android Native Application, which distinguishes it from the web client and from the server. Habitica is a system with several clients, and the Android app is one of them. The licence is GPL-3.0, with the file at the repository root. For an application distributed through Google Play rather than sold as source, the practical implication is limited, but it does mean a fork must also be GPL-3.0. There is no homepage field in the repository metadata, which is consistent with a client repository rather than the project root. The A link to habitica.com in the README is the product site, and the Google Play listing is the distribution channel. The pause notice has one clause worth repeating because it is easy to misread: the codebase remains open source and publicly visible. That means it can still be read, studied and forked, and that any fork inherits the same policies stated in the README, including the prohibition on generated code. What is paused is the acceptance of outside patches, not the existence of the code. ## Conclusion habitica-android is worth using if you want the native Android and Wear OS clients for Habitica and you install from Google Play, since release notes live on the releases page and the app updates itself. It is not a repository to plan contributions against, because code based contributions are paused and the stated reason is a change in the tech landscape and in how the player base interacts with Habitica across platforms. If you need to build it yourself, copy habitica.properties.example and habitica.resources.example, register two Firebase apps, and drop the resulting google-services.json into both the Habitica and wearos directories. ## FAQ ### Are pull requests still accepted for habitica-android? No. The README states that public pull request submissions were paused as of August 4, 2026, while the codebase remains open source and publicly visible. ### How do I build the Habitica Android app locally? Copy habitica.properties.example to habitica.properties and habitica.resources.example to habitica.resources, create a Firebase project with two apps for the release and debug application IDs, then put the downloaded google-services.json into both the Habitica and wearos directories and sync the Gradle files. ### Why does the Habitica Android build need two Firebase apps? The README instructs you to create apps for com.habitrpg.android.habitica and com.habitrpg.android.habitica.debug, because Android gives a debug build its own application ID. You download the google-services.json from the second app. ### Can I contribute an issue fix to habitica-android? Not currently through code. The README says to look for the Help Wanted tag on issues, but also notes that the Help Wanted label marks issues that would be acceptable for a contributor, while the pause notice states code contributions are not being accepted. ### What is the code style for habitica-android? The project is written in Kotlin and follows the Android Kotlin Style Guide. Static analysis is handled by Detekt, with a detekt.yml and a detekt_baseline.xml in the repository root. ## Sources - [HabitRPG/habitica-android on GitHub](https://github.com/HabitRPG/habitica-android) - [Issues](https://github.com/HabitRPG/habitica-android/issues) - [License: GPL-3.0](https://github.com/HabitRPG/habitica-android/blob/main/LICENSE) - [README](https://github.com/HabitRPG/habitica-android/blob/main/README.md) - [Releases](https://github.com/HabitRPG/habitica-android/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/habitrpg-habitica-android