# Nextcloud Deck for Android: a mobile client for a self hosted board > Nextcloud Deck for Android is a GPL-3.0 Java client for the Nextcloud Deck kanban app, published on the Play Store and F-Droid, with offline work and multiple account support. It is only useful if you already run a Nextcloud server with Deck enabled, so for anyone else the server side is the starting point rather than this app. **stefan-niedermann/nextcloud-deck** — 📋 Android client for nextcloud deck app - Repository: https://github.com/stefan-niedermann/nextcloud-deck - Website: https://play.google.com/store/apps/details?id=it.niedermann.nextcloud.deck.play - Stars: 572 · Forks: 62 - Language: Java - License: GPL-3.0 - Published: 2026-10-22 · Updated: 2026-10-22 · Language: en - Canonical page: https://hysenlabs.com/projects/stefan-niedermann-nextcloud-deck ## A phone client for boards that live on your own server Nextcloud Deck for Android is a native Android application that talks to the Nextcloud Deck app running on a Nextcloud server. The repository describes it as an Android client for the Nextcloud Deck App, and the project topics place it in the kanban and scrum world, with trello and trello-like among the tags. That framing matters, because this app is not a kanban product. It is the mobile half of a self hosted one. The board, the lists, the cards, and their history live on the server, and the app is a way to read and change them from a phone. The server side project is nextcloud/deck, and the client here is stefan-niedermann/nextcloud-deck, a separate repository with its own licence and its own release channel. The primary language is Java, which tells you the app is built with the older Android toolchain rather than a cross platform framework. The repository root shows a standard Gradle project with app/, gradle/, gradlew, build.gradle, and settings.gradle, and the fastlane directory holds the store listing metadata, including the screenshot paths for the list view and card view. For the person deciding whether to install it, the first question is not about features. It is whether a Nextcloud instance already exists, because the app has no standalone mode. ## The version floors in the README are the real compatibility spec The README lists three requirements, and the last two carry version numbers that decide whether the app will work. A Nextcloud instance running is the first requirement. The second is the Nextcloud Android app installed, at version 3.9.0 or above, and the third is the Nextcloud Deck app enabled, at version 0.6.4 or above. The second requirement is the one that surprises people. Installing a Deck client on a phone is not a standalone act, because the Nextcloud Android app is what handles the account, the server connection, and the shared infrastructure such as file access. The Deck client sits on top of that foundation, which is also why the app supports multiple accounts as a listed feature. Two apps, one account, and a server you control. So an upgrade on the server has consequences on the phone. If your instance is on an old Deck release, the client will not be able to use the newer server side features, and the reverse also applies. Two version floors to track, on top of the server itself. The README is also unusually explicit about licensing for contributors, which tells you something about how the project expects outside patches to work. Contributions are considered to be licensed under the GNU General Public License 3+, and while contributors retain their copyright, the project asks that a copyright header naming the year, the name, and the email address be added to any file changed substantially. ```bash @copyright Copyright (c) , () ``` ## Getting the app without a build toolchain There are no installation commands in the README, and there does not need to be. The app is distributed as a built binary through two channels, and both are linked from the README. The first is the Google Play Store, under the package id it.niedermann.nextcloud.deck.play, with the listing URL given in the repository metadata. The second is F-Droid, under the package id it.niedermann.nextcloud.deck, which is the listing that carries the F-Droid release badge. F-Droid is the more interesting choice for self hosted users, because the point of running your own server is usually the point of not depending on a proprietary distribution channel for the client as well. The README also links a donations page, and the repository holds a PRIVACY.md and an FAQ.md at the root. A privacy statement in a project of this size is worth reading before you install, especially if your board contains work that should not leave your infrastructure. The release status deserves a note, and it is unusual. The repository has no GitHub releases at all, so the version badges in the README point to tag pages that are not populated, and the practical distribution is the store. The last push to the default branch, master, was on 2026-10-20, so the code is moving even though there is no GitHub changelog to read. ## Offline support is the feature that changes how a board behaves The feature list is short, and the entries that matter for day to day use are cards, lists, boards, tags, attachments, activities, and comments. Multiple accounts are supported, the interface has a dark mode, and the app is translated into many languages through Transifex. Works offline is the entry that changes the character of the tool. A client that can hold board state locally and reconcile later is usable on a train, in a meeting room with no signal, or on a site visit. It also changes the failure mode. When the connection drops mid edit, the question becomes whether the app queues the change and replays it or discards it, and the README does not document that reconciliation behaviour. Two other features sit between this client and a plain viewer. The activity feed and comments mean the app carries the conversation attached to a card, not only the card itself. Attachments mean the phone can reach the files a card points at, which in a Nextcloud deployment usually means going through the same server that hosts the board. The tab and card structure of the interface is visible in the fastlane metadata, which stores separate list view and card view screenshots. The repository also contains two directories whose names describe extra work beyond the app itself: tab-layout-helper and cross-tab-drag-and-drop. The second of those names points at moving cards between tabs on different boards, which is a real difference between a kanban tool and a shared todo list. ## What a Nextcloud phone client commits you to Choosing this app means choosing the whole Nextcloud Android stack, and that is the comparison worth making against a hosted board tool. A hosted service gives you a phone app, a server, an account system, file attachments, notifications, and updates in one package, with someone else carrying the operational load. Here, the board server and the phone client are separate pieces, and the phone client also depends on a third piece, the Nextcloud Android app, which you install and update yourself. The upside of that arrangement is control. Board data, attachments, and activity history stay on infrastructure you administer, and the F-Droid build removes the store dependency. The cost is that you now own the update path for three components instead of one, and the version floors in the README are where that cost shows up. It is worth being clear that the same trade applies to the server side project, nextcloud/deck, which is where the kanban data model and the API live. This repository contributes only the mobile client, so a team evaluating the platform should look at the server project and this one together. The two are also versioned independently, which is the recurring operational fact. The Deck app floor of 0.6.4 and the Nextcloud Android floor of 3.9.0 are constraints on the combination, not on this app alone. ## GPL-3.0, a translation workflow, and a single maintainer The project is licensed GPL-3.0, and the README states that all contributions to the repository are licensed under the GNU General Public License 3+. For an end user installing the app that matters little, since you are not distributing the code. For anyone who wants to modify the client and ship their own build, the copyleft terms and the request to keep a copyright header on substantially changed files are the parts to read carefully. The README asks for help in specific ways: testing the app on different devices, reporting issues in the issue tracker, picking up a good first issue, opening a pull request, increasing test coverage with unit tests, and translating on Transifex. The translation setup is backed by a .tx directory in the repository, which is the configuration the Transifex client uses. The project is not archived and the last push was on 2026-10-20, so it is being worked on. What is missing is a release trail: no GitHub releases, and therefore no published changelog and no tag to roll back to. The store listings are the de facto version record, and a rollback for a bad build means reinstalling an older store artefact. There is also a maintenance script in the repository root, clearLocalBranches.sh, which is a small sign of the day to day friction of keeping a long lived Android project tidy. The FAQ.md file at the root is where the user facing answers live, and it is the first place to look for behaviour that the short feature list leaves open. ## Conclusion Nextcloud Deck for Android fits teams that already run a Nextcloud instance with the Deck app enabled and want a phone client for the same boards, and it suits people who want their board data on their own infrastructure rather than in a hosted product. It is the wrong tool for someone without a Nextcloud server, since the client has no standalone mode and cannot create boards by itself. Before installing it, confirm that your instance runs the Nextcloud Android app at version 3.9.0 or above and that Deck is enabled at version 0.6.4 or above, as the README requires, and note that the project publishes no GitHub releases and last pushed on 2026-10-20, so the store version is what you will be running. ## FAQ ### What do I need to run Nextcloud Deck for Android? The README lists a Nextcloud instance running, the Nextcloud Android app installed at version 3.9.0 or above, and the Nextcloud Deck app enabled at version 0.6.4 or above. The app is a client, so it cannot be used on its own. ### Where can I download Nextcloud Deck for Android? It is published on the Google Play Store as it.niedermann.nextcloud.deck.play and on F-Droid as it.niedermann.nextcloud.deck. The repository itself has no GitHub releases, so the store is where the built binary is distributed. ### Does Nextcloud Deck for Android work offline? The README lists works offline among the features, alongside multiple accounts, card and board management, tags, attachments, activities, comments, and dark mode. The README does not describe how changes made offline are reconciled with the server. ## Sources - [Issues](https://github.com/stefan-niedermann/nextcloud-deck/issues) - [License: GPL-3.0](https://github.com/stefan-niedermann/nextcloud-deck/blob/master/LICENSE) - [Project website](https://play.google.com/store/apps/details?id=it.niedermann.nextcloud.deck.play) - [README](https://github.com/stefan-niedermann/nextcloud-deck/blob/master/README.md) - [stefan-niedermann/nextcloud-deck on GitHub](https://github.com/stefan-niedermann/nextcloud-deck) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/stefan-niedermann-nextcloud-deck