Tasks.org Open-Source To-Do With CalDAV Sync
Tasks.org review: how offline edits and CalDAV sync collide when two Android devices diverge—plus what survives Google Tasks round trips on Android.
App summary
- App
- Tasks.org
- Developer
- Alex Baker
- License
- GPL-3.0-only
- Version
- unknown
- Size
- unknown
- Price
- Free (optional paid features unknown)
Tasks.org Offline Edits vs CalDAV Sync: What Happens When Two Devices Diverge
Tasks.org keeps your tasks on the device first. Offline-first local task storage is listed as a key feature, not a fallback mode, which means writing a task with no signal is the normal path rather than a degraded one. Nothing about the core workflow depends on a network round trip, and no account is required to use the app locally. That design choice is the reason the app is worth a look in the first place. If you want to compare CalDAV sync with a mainstream task manager, the Any.do review covers its calendar sync behavior and where the paid tier affects the workflow. For a broader open-source productivity setup alongside Tasks.org, the Simple Mobile Tools Fork review explains how its Calendar and Notes apps fit into a privacy-focused Android workflow. If you plan to install or update Tasks.org from an open-source catalog, the F-Droid guide covers repository setup and app verification.
CalDAV synchronization is supported, and that is exactly where divergence becomes possible. Two devices, both editing the same list, both holding their own local copy. The fact data confirms CalDAV sync exists, and it also warns that sync setup can require a third-party account or configuration. In other words, the sync layer is something you assemble rather than something the app hands you pre-wired. That distinction matters more than the feature list suggests.
What the fact data does not specify is conflict resolution. There is no statement about last-write-wins behavior, field-level merging, how deletions propagate, or what happens when the same task is edited on two devices before either one syncs. That is a real gap, and it should be treated as unknown rather than assumed benign. If you plan to run Tasks.org on a phone and a tablet against one CalDAV account, test that scenario deliberately with a throwaway list before you trust it with actual work.
Privacy follows the same logic. Local use requires no account, so nothing leaves the device by default. The moment you enable CalDAV or Google Tasks sync, task data is sent to the provider you chose, and that provider’s retention and access rules apply rather than Tasks.org’s. The official privacy policy is the place to check the details, and it is worth reading before you point the app at a server you do not control.
Tasks.org + Google Tasks Sync: Which Subtasks, Tags, and Completed Tasks Survive the Round Trip
Google Tasks synchronization is supported. That is a confirmed fact, and it is genuinely useful if you already live inside Google’s ecosystem. But “supported” and “identical” are different claims, and the fact data does not claim Tasks.org is a drop-in replacement for Google Tasks with matching behavior in both directions. Treat the sync as a bridge between two different data models, not as a mirror.
Subtasks, tags, filters, and custom lists are listed as Tasks.org features. They are not listed as guaranteed Google Tasks sync fields. That wording is deliberate on the part of the fact data, and it points at a real risk: tags and filters in particular are the kind of structure that tends to be app-specific, because Google Tasks has no obvious equivalent for them. A feature can be fully functional locally and lossy across the bridge.
The exact handling of Google Tasks subtasks, notes, and completed tasks is not provided in the fact data and has to be labeled unknown. Recurring tasks fall into the same bucket. If you have seen reports of subtasks or recurring items not syncing correctly, the honest answer is that the fact data neither confirms nor denies the specific failure modes. What it does confirm is that setup can require a third-party account or configuration, which adds another place for things to go wrong.
The practical response is to separate local features from synced features in your own head before you commit. Build a small test list with a parent task, two subtasks, a tag, a due date, and one completed item. Sync it, then inspect both sides. If the hierarchy or the tag disappears, you have learned something the documentation will not tell you, and you have learned it before your real task list is involved.
Tasks.org on F-Droid vs Google Play: Update, Donation, and Feature Differences to Check Before Installing
Tasks.org is verified as available on both Google Play and F-Droid, and its source code is publicly hosted on GitHub. Those are the official channels, and they are the only places you should be getting the app from. Beyond that, the fact data is quiet on how the two builds relate to each other.
The license is GPL-3.0-only, a copyleft license that requires derivative works to remain under the same terms and keeps the source available. What that does not mean is that the Play Store build is closed-source or paid. That assumption shows up often and it is not supported by anything in the fact data. The app is listed as free, and optional paid features are unknown, which is a different statement from “the Play version costs money.”
Several things you might want to know before choosing a channel are simply not in the fact data: the exact latest version number, the APK download size, the minimum supported Android version, and the current download count. Because of that, this article will not invent an update cadence, a donation mechanism, or a feature parity difference between F-Droid and Google Play. Check both listings yourself and compare what they actually say on the day you install.
One thing you can reason about: the license and the public repository mean auditability does not depend on which channel you pick. If you want to verify what a build contains, the source on GitHub is the reference point, and that holds whether the APK came from F-Droid or from Google Play. The channel affects how you receive updates, not whether the code is inspectable.
Tasks.org Is Not a Shared Team Task Manager: Android-Only, Local-First, and Sync-Bound Limits
Tasks.org is Android-only. There is no native web or desktop client in the fact data, and that single constraint rules out a large set of use cases before any feature discussion begins. Anyone who needs a browser tab open on a work laptop, or a proper desktop app alongside a phone, is outside the supported platform here.
Local use requires no account, which is one of the app’s genuine strengths. Sync, by contrast, depends on supported services such as CalDAV and Google Tasks. That means sharing a list with another person or a family member realistically means sharing credentials to a sync account, which is account sharing rather than collaboration. The fact data does not list shared projects, assignments, comments, list permissions, or real-time collaboration, so none of those should be implied.
Name the wrong audience plainly, because it saves people time. Teams that need shared projects, assignments, and comments will not find them. Users who require a polished native web or desktop client will not find one. People expecting Todoist-style natural language input everywhere should not assume it. Users wanting built-in calendar and kanban views are looking at the wrong app. And non-technical users who are unwilling to configure a CalDAV account will find the sync setup friction genuine rather than theoretical.
Two alternatives are listed in the fact data for exactly these cases. Todoist is described as a cross-platform commercial task manager with broad integrations, which addresses the platform gap directly. Microsoft To Do is described as a free task manager integrated with Microsoft accounts and Outlook, which suits people already inside that ecosystem. Neither is a like-for-like swap, but both sit closer to the collaboration and cross-platform expectations described above.
Picking a Sync Backend: CalDAV, Google Tasks, or Staying Local
There are three broad states for a Tasks.org install: local only, CalDAV, or Google Tasks. Each has a different cost, and the fact data supports all three. Choosing deliberately is more useful than enabling everything and hoping the pieces line up.
CalDAV is a protocol, so the question “will this work with Nextcloud Tasks or with iCloud Reminders” is really a question about your server rather than about the app. The fact data confirms CalDAV support but does not enumerate which CalDAV servers have been tested or which ones handle subtasks and tags correctly. It also notes that setup can require a third-party account or configuration. If you already run a CalDAV server, this is the most self-directed option available.
Google Tasks is the lower-friction path if your tasks already live in Google’s world, but the round-trip caveats in the previous section apply in full. The fact data does not promise identical behavior, and the fields most likely to be lost are the ones that make Tasks.org interesting, such as tags and custom lists. Friction is lower; fidelity is unproven.
Staying local is a legitimate choice rather than a compromise. No account, no configuration, no task data leaving the device. The trade-off is obvious and worth stating: without sync, there is no multi-device story, and the fact data does not describe any export or backup mechanism that would substitute for one. If you only ever use one Android device, local-only is the cleanest configuration available.
Reminders and Recurring Tasks: What the Fact Data Confirms and What It Leaves Open
Setting reminders and recurring tasks is listed as a core function of the app. That much is confirmed. What is not confirmed is the mechanics behind either one, and the difference matters if reminders are the reason you are considering the app.
Location reminders are a good example of a claim to be careful with. The fact data does not mention them at all, which means any statement about whether they work reliably on Android 13 or 14, or whether they function without Google Play Services on every device, is outside what can be supported here. The common assumption that location reminders work everywhere without Play Services is exactly that: an assumption. Treat it as unknown until you verify it on your own hardware.
Recurring tasks raise a parallel question on the sync side. Recurrence rules are notoriously implementation-specific, and the fact data does not describe how they survive a CalDAV or Google Tasks round trip. If a weekly task is completed on one device and synced to another, the behavior is not documented. That does not mean it breaks; it means nobody has told you it does not.
The reasonable approach is to test the specific reminder type you depend on before you depend on it. Set a time-based reminder, set a recurring task, complete it, and watch what happens across a sync cycle. If the results match your expectations, you have your answer. If they do not, you have found the limit early.
Migrating From Todoist or TickTick: What Can and Cannot Be Carried Over
Todoist and Microsoft To Do appear in the fact data as alternatives, which makes them the natural comparison points for anyone considering a switch. TickTick is not in the fact data, though readers ask about it, and nothing here should be read as a claim about how it behaves. The migration path itself is not documented in the fact data at all.
Subtask preservation is the main risk. Subtasks are listed as a Tasks.org feature, and whether an import preserves hierarchy depends on the source format and the sync target, neither of which is described. Tags and custom lists raise the same question. A flat list of task titles will usually survive any migration; the structure around those titles is where things get lost.
The safe sequence is unglamorous but effective. Export from the old tool, import into a test list in Tasks.org, and verify hierarchy, tags, due dates, and completion state before deleting anything from the old account. If you plan to sync to Google Tasks, run the same check after sync rather than before, because the bridge is the part most likely to drop structure.
Keep the old account alive until the new one has survived a full week of real use. That advice costs nothing and it is the only reliable protection against a migration that looks fine on day one and turns out to be missing half its subtasks on day three.
The Smaller Ecosystem Problem: Integrations, Documentation, and Support Expectations
The fact data lists a smaller ecosystem than some major commercial task managers as a known drawback. That is an honest admission, and it has practical consequences that go beyond a vague sense of being less popular. Fewer integrations, fewer third-party guides, and a smaller pool of people who have already hit the same problem you are hitting.
Open source offsets some of this. The code is auditable, the repository is public, and the license guarantees that the source stays available. What auditability does not provide is support. Being able to read the code is not the same as having someone answer a question about CalDAV configuration on a Sunday afternoon, and conflating the two leads to disappointment.
The fact data names Alex Baker as the developer and does not describe team size, support commitments, or response times. That is not a criticism, just a limit on what can be said. If guaranteed support is a requirement for you, the commercial alternatives listed in the fact data are the more appropriate choice, and that is a legitimate reason to pick them.
For everyone else, the trade is straightforward. You accept a smaller ecosystem and manual sync configuration in exchange for an app that is open source, auditable, and usable without an account. Whether that trade is worth it depends entirely on how much you value the second half of that sentence.
Verdict
Tasks.org is a credible open-source, offline-first task manager for Android, and the fact data supports that judgment without embellishment. Local storage works without an account, the code is public and GPL-3.0-only, and sync is available through CalDAV and Google Tasks for people willing to configure it. Those are real advantages, and they are the reason the app has a place.
It is not a drop-in Google Tasks replacement. The fact data does not claim identical sync behavior, does not guarantee that subtasks, tags, filters, or custom lists survive the round trip, and does not describe conflict resolution when two devices diverge. Anyone who needs those guarantees should look at the commercial alternatives instead of assuming the bridge is seamless.
It is also not a shared team tool. Android-only, no native web or desktop client, no shared projects, no assignments, no comments, no list permissions, no real-time collaboration. Teams needing any of that are outside the supported scope, and the fact data names Todoist and Microsoft To Do as the alternatives for exactly those requirements.
The right reader is someone who uses one or two Android devices, wants tasks stored locally by default, is comfortable configuring a CalDAV account or accepting the Google Tasks caveats, and values an auditable codebase over a polished multi-platform ecosystem. The wrong reader is a team, a desktop-first user, someone expecting natural language input everywhere, or anyone who wants built-in calendar and kanban views. If you recognize yourself in the first group, install from tasks.org, Google Play, or F-Droid and test your sync setup before you trust it. If you recognize yourself in the second, the fact data already points you elsewhere.
Pros
- Open-source and auditable
- No account required for local use
- Flexible sync options including CalDAV and Google Tasks
Cons
- Android-only
- Sync setup can require a third-party account or configuration
- Smaller ecosystem than some major commercial task managers
The link goes straight to Alex Baker. We do not host app files.
Frequently asked questions
Is Tasks.org free?
The recorded pricing model is Free (optional paid features unknown).
What license does it use?
It is listed under GPL-3.0-only.
Where can I download the official version?
The official link points to https://tasks.org/.