# Money Manager Ex for Android is a companion app to a desktop database > The Android build of Money Manager Ex is not a standalone finance tracker, it is a client for the same database the desktop application uses, and the sync work that makes that possible is what the repository is mostly about. **moneymanagerex/android-money-manager-ex** — Local-first personal finance app. Encrypted, self-hosted, sync across devices. - Repository: https://github.com/moneymanagerex/android-money-manager-ex - Website: http://android.moneymanagerex.org/ - Stars: 719 · Forks: 229 - Language: Java - License: GPL-3.0 - Published: 2026-10-21 · Updated: 2026-10-21 · Language: en - Canonical page: https://hysenlabs.com/projects/moneymanagerex-android-money-manager-ex ## It is a companion, not a replacement The basic information section is short and it sets the expectations. Money Manager Ex for Android is a mobile companion to the PC and desktop personal finance applications currently available for Windows, Mac OSX and LINUX. It can be used with the same database used by MoneyManagerEx Desktop, or as an addition to GnuCash or other applications that import transactions via .qif files. That is the whole positioning, and it is a sensible one. A personal finance database has a schema, a set of accounts, a currency model and a reconciliation model, and reimplementing those for a phone is a large project with no payoff if the desktop application is the thing you actually use. So the Android app is a client for that database, and the .qif route is the escape hatch for people whose desktop tool of choice is GnuCash rather than Money Manager Ex. The repository description calls it a local-first personal finance app, encrypted, self-hosted, with sync across devices, and the topics confirm the emphasis with cipher, encryption, finance, mmex4android and moneymanagerex. ## Three distribution channels, and the F-Droid one matters The download section offers the app from F-Droid, from GitHub releases and from Google Play, and the badges track the version in each of them. That third option in the badge row is the F-Droid version for the package identifier com.money.manager.ex, and the Google Play badge points at a different identifier, com.money.manager.ex.android, which suggests the two stores carry different builds rather than the same artifact. The GitHub release badge is configured to include prereleases, so the badge follows the newest tag whether or not it is a stable release. For a user who does not want Google Play, the F-Droid listing is the one that matters, because F-Droid builds from source rather than accepting a prebuilt binary, and it is the only channel where the claim about what is in the package is verifiable by the person distributing it. The GitHub release badge also carries a total downloads count for the latest release assets, which is the number to look at if you want to gauge how actively the release artifacts are being fetched. ## The sync problem is the hard problem, and the repository admits it The top level of the repository is where the real shape of the project shows. There are several files whose names say what the work is. Sync-ToDo.md is a list of outstanding sync work. android_sync_guidelines.md and android_sync_guidelines_instruction.md describe how the sync is supposed to behave on Android, which is the awkward platform because the app can be killed at any moment and the sync has to survive that. pocketbase-sync-engine.md points at a particular engine for the self-hosted sync side. And session_analytics.tap with a session_analytics_to_send/ directory sits at the root, which is a test plan script for session analytics. Alongside those are the code directories, with money/ for the shared money logic, app/ for the Android application, metadata/ for the metadata, scripts/ for the build scripts, and MMEX_Icon_Font/ for the icon font, plus a lint.xml and a robolectric.properties file, which are the two files that tell you the project runs Robolectric tests. The documentation directories carry both current and old copies, with docs/, docs-old/ and doc-old/, which is a sign of a long-lived project whose documentation accumulates. ## Building it is a standard Android Studio project The build section recommends the current stable version of Android Studio, using the embedded JDK, which it notes is now compatible with JDK17 and later, and using the gradle wrapper rather than a local Gradle installation. That last recommendation is the one worth following, because the wrapper pins the Gradle version and a local install will produce different results depending on what you happen to have. The repository carries gradlew and gradlew.bat, a gradle/ directory, build.gradle and settings.gradle at the root, a gradle.properties file and an example.local.properties file, and the detail lives in BUILD_AND_RELEASE.md. The primary language recorded for the repository is Java, and the structure with an app/ module and a separate money/ module is consistent with a Java Android application that keeps its domain logic in a library module so it can be shared with the desktop application. There is also a script for release automation under scripts/, and the metadata/ directory is where the store listings and translations are assembled. ## The community is organised around translation and testing The contributing section lists four routes into the project, and only one of them is code. You can contribute code, translate through MMEX4Android on Crowdin, beta test through Google Play Open Testing, or donate. The Crowdin badge in the header row confirms the translation workflow is live and integrated into the build, and the crowdin.yml file at the repository root is the configuration for it. The Google Play Open Testing route is the one that is unusual and useful, since it means there is a public channel for pre-release builds where users can exercise a change before it is packaged, and the badge row tracks the Play Store version separately from the others. Support itself is partly unofficial, with the readme crediting snaggletoothlover for an unofficial Discord channel. A user manual is published at android.moneymanagerex.org/usermanual/ and the homepage at android.moneymanagerex.org is described as the place for user-oriented information, which tells you where the boundary sits between the code repository and the documentation. ## Where this is the wrong choice Three limits are worth naming. The first is that the data model is not phone-first. Every feature depends on the desktop application's database format, and if you have never used Money Manager Ex or imported .qif files, the app starts from an unfamiliar schema rather than from a clean slate. The second is that the sync story is explicitly unfinished. A file named Sync-ToDo.md at the root of the repository, plus a pair of Android sync guideline documents, plus a separate document naming the sync engine, is the shape of a project where the sync is the hard part and the work is not done. That is not a criticism so much as a warning for anyone planning to rely on multi-device sync as the main feature. The third is the thin continuous integration story, since the readme carries a TODO to add a CI test covering all the unit tests, the integration tests and the UI tests service, and the badge row still shows an AppVeyor build status. So the code moves faster than the automation around it, which is normal for a volunteer-maintained application but means you should expect a manual step somewhere in the release path. ## Conclusion Money Manager Ex for Android suits someone who already runs the desktop application on Windows, macOS or Linux and wants to record transactions from a phone against the same file, and it suits anyone who prefers a local database to a hosted service. It is the wrong tool if you want a phone-first finance app with automatic cloud backup, since the data model is the desktop one and the sync is a separate project. It is also the wrong choice if you need encryption of the file at rest to a particular standard, because the repository records cipher and encryption as topics without describing the scheme. Before installing, read the user manual, check the release history, and note that the last push was on 2026-10-20 with the current release at 5.5.13 from 2026-09-22, so the tree is active while the packaged version moves on its own schedule. ## FAQ ### What is Money Manager Ex for Android? It is a mobile companion to the Money Manager Ex personal finance applications for Windows, Mac OSX and Linux. It can be used with the same database as the desktop version, or alongside other applications that import transactions through .qif files, and it is distributed through F-Droid, GitHub releases and Google Play under the GPL-3.0 licence. ### How do I build Money Manager Ex for Android? Use the current stable version of Android Studio with the embedded JDK, which is compatible with JDK17 and later, and build with the gradle wrapper rather than a local Gradle installation. The repository carries gradlew and gradlew.bat, and the full detail is in the BUILD_AND_RELEASE.md file at the root. ### How can I contribute to Money Manager Ex for Android? There are four routes listed in the README: contribute code, translate through the MMEX4Android project on Crowdin, beta test through Google Play Open Testing, or donate. The Crowdin translation project is wired into the build through the crowdin.yml file at the repository root, and there is an unofficial Discord channel for support. ## Sources - [License: GPL-3.0](https://github.com/moneymanagerex/android-money-manager-ex/blob/master/LICENSE) - [moneymanagerex/android-money-manager-ex on GitHub](https://github.com/moneymanagerex/android-money-manager-ex) - [Project website](http://android.moneymanagerex.org/) - [README](https://github.com/moneymanagerex/android-money-manager-ex/blob/master/README.md) - [Releases](https://github.com/moneymanagerex/android-money-manager-ex/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/moneymanagerex-android-money-manager-ex