Super Productivity combines planning with measured work
Super Productivity is an 816,706-line TypeScript application for people who want tasks and time records in the same place. Projects, tags, subtasks, timeboxing, estimates, a Pomodoro timer, break reminders, notes, files, and work summaries all feed one personal workflow. Integrations can import assigned work from Jira, GitHub, GitLab, Gitea, OpenProject, Linear, ClickUp, Trello, Azure DevOps, and CalDAV. That is much broader than a simple checklist, and it can feel excessive if all you need is groceries and reminders.
The application spans 4,913 repository files and several runtimes. Electron handles desktop releases, Capacitor covers mobile builds, Angular provides the interface, and npm workspaces hold shared sync and plugin packages. Version 18.21.2 added a tracked-task browser title and Android URL actions, then fixed legacy-data migration, schedule touch behavior, iOS keyboard layout movement, repeating-task cleanup, and sync repair. The feature surface is useful, but every supported platform creates another place where timers, storage, notifications, and integrations behave differently.
Local use needs no account; multi-device sync needs a provider
A single-device user can keep data locally without registration or a hosted service. The README says Super Productivity does not collect user data, and the sync guide explicitly makes remote sync optional. Once multiple devices enter the picture, users choose 1 provider per device. Options include Dropbox, Nextcloud, WebDAV, local files, and SuperSync. Dropbox uses OAuth. Nextcloud and generic WebDAV need server details, while local-file sync depends on a folder the app can access.
The sync labels deserve attention in version 18.21.2. SuperSync is beta and receives the new operation-based work. Dropbox and Nextcloud use the older file-based path and remain supported. Generic WebDAV and local-file sync are labeled experimental, and the guide warns against placing the local sync folder inside Syncthing or Resilio for multi-device replication. Self-hosted SuperSync goes further: its server expects PostgreSQL 16, JWT and public-URL configuration, authentication infrastructure, backups, and careful handling of credentials in logs.
The web app loses native backups and background behavior
Browser use is convenient, but the official comparison names concrete losses. The web build cannot make automatic filesystem backups or use local-folder sync, and Node.js plugins are disabled. Time tracking works only while the app stays open unless the Chrome extension supplies idle detection. Browser CORS can block calendar or WebDAV requests, background tabs can be throttled, and the browser denies system tray features and global shortcuts. A 333 MiB free-space threshold triggers a low-storage warning for browser data.
The included Docker path serves the web edition on port 80, but the container does not own user persistence. The guide says data stays in browser storage, so mounting a volume does not turn the web app into a central task database. Adding WebDAV means configuring usernames, passwords, per-user directories, and the app's base URL. Docker is useful for hosting the client, yet it does not erase the web limitations or create the richer operation-based SuperSync service.
What happened when we ran it
Our sandbox installed Super Productivity in 57 seconds at commit 06be7d5. npm added 1,624 packages and occupied 1,157 MB, far larger than the 55.9 MB checkout. The production build succeeded in 295 seconds. We used a fresh unprivileged Debian container with 3 CPUs, 8 GB of RAM, no secrets, and the lab-node:22 image. npm audit reported 0 known vulnerabilities across all 4 severity levels in that installed dependency set.
The test command ran for 117 seconds and exited 1. Vitest itself reported 269 passed, 0 failed, out of 269. The supplied log tail lists cases 18 through 29 as successful, including text conversion, version codes, release-note grouping, and AI-provider environment handling. It contains no final error that explains the process status, so the honest result is mixed: the visible Vitest suite passed, while the complete command did not. Our scan also found 29 CI workflow files, a Dockerfile, workspaces, and no top-level tests directory.
Version 18.21.2 is active, with 1,342 issues open
GitHub showed 21,714 stars, release v18.21.2 on August 31, 2026, and a last push later that same day. Its combined open count was 1,454, which our API searches split into 1,342 issues and 112 pull requests. New issue and pull-request activity continued into September 1. The queue includes current work on window behavior, schedule handling, integrations, synchronization, dependency updates, and requested features, rather than one abandoned block of old reports.
That activity supports a strong community score, though the 1,342-issue backlog is a real adoption cost. Users can search a large history when something breaks, but maintainers also have a lot to triage across desktop, mobile, browsers, plugins, and sync providers. The latest release addressed privacy hardening and older-operation maintenance in SuperSync while other production backup reports remained open. Buyers should test the exact platform and provider combination they intend to depend on, especially during the beta sync transition.
Pick Super Productivity for personal time tracking, Vikunja for shared tasks
Super Productivity earns its place when one person wants daily planning, focus sessions, imported developer work, and exported time records together. Vikunja is a better fit when a server-backed task system for a team is the main job. Tasks.org is the narrower alternative for Android-centered personal lists. At 55.9 MB before its 1,624-package install, Super Productivity asks more of a contributor than either a simple list app or a hosted client would.
The best starting point is a packaged desktop build, not the 295-second source path or the reduced browser edition. Keep local backups before experimenting with sync, choose one documented provider, and verify behavior on every device involved. Self-host SuperSync only if PostgreSQL, authentication, CORS, secrets, upgrades, and backups are ordinary work for your team. The app is mature enough for serious personal use, while its beta sync layer and unexplained test-command exit still deserve a controlled trial.