f10d0e9d48
* test(e2e): raise timeouts for two CI-flaky waits Both timeouts repeatedly hit their limit on saturated scheduled runners without indicating a real product regression: - supersync.page.ts:781 — final sync-state icon waitFor went 10s → 30s. The race above it already consumed a 30s budget, so falling back to 10s here is too tight when the runner is hot (e.g. SuperSync 5/6 in run 26514574130, "Client A can migrate multiple times" failure). - repeat-task-day-change #6230 — post-midnight visibility went 30s → 60s. Even with the focus-event fallback added in46ac873570, the 1s tick + debounce + sync chain can still exceed 30s under contention. * fix(android): keep foreground services alive across task removal The focus-mode and tracking foreground services overrode onTaskRemoved to stop themselves when the app was swiped from recents, which defeats the purpose of running them as foreground services. Remove the overrides so the native countdown continues ticking and the notification persists after task removal. Refs #7818, #4513 * fix(theme): stabilize Android keyboard-height tracking Per-event commits during the Android IME open animation sampled partial keyboard amounts from `window.innerHeight - visualViewport.height` (layout-viewport adjustResize and visual-viewport resize fire at slightly different times), parking the global add-task bar mid-page. Debounce the open path 200ms so only the final value lands; commit synchronously when the value falls back to zero so the bar drops the moment the IME is gone. * fix(theme): prevent white flash on Android keyboard resize The Android WebView surface defaulted to white, so adjustResize keyboard animations briefly exposed it before the page repainted at the new size — jarring in dark theme. Paint the surface in the theme background: a values/values-night color resource provides the cold-start default, and a new NavigationBar.setWebViewBackgroundColor push keeps it in sync on live theme switches (the activity is not recreated since uiMode is in configChanges). Also promote the full-viewport gradient backdrop to its own compositor layer as a first-pass mitigation for resize choppiness, pending deeper work. Not yet verified on-device. * docs(android): plan to smooth soft-keyboard resize jank Research + multi-reviewed plan for the remaining keyboard-resize choppiness (the white-flash half is already fixed in80b08f0e96). Root cause: adjustResize resizes the WebView window per frame (WebView is excluded from Chrome 108's visual-viewport fix). Recommends a KISS core — flip only CapacitorMainActivity to adjustNothing + reuse the existing visualViewport/--keyboard-height model and scroll-into-view — gated behind a baseline trace, with VirtualKeyboard API and CSS containment kept as contingencies behind proven need. * perf(theme): dedupe Android keyboard-visibility emissions The native OnGlobalLayoutListener pushes isKeyboardShown$ on every layout pass (every frame of the IME slide), so the subscriber rewrote <body> classes and re-triggered change detection each frame. distinctUntilChanged collapses it to actual show/hide transitions. * docs(android): correct keyboard-resize plan for min-Chrome-107 Implementation review found MIN_CHROMIUM_VERSION=107, but WebView only auto-resizes the visual viewport for the IME at ~Chrome 139. So a static adjustNothing flip would leave Chrome 107-138 with no keyboard-height signal (inputs silently covered). Corrected the plan: VirtualKeyboard API is required (not optional), the switch must be runtime-gated via a native setSoftInputMode method keeping adjustResize as the fallback, and the cheap containment route is now Phase 1 (try first) with the bigger flip as Phase 2. distinctUntilChanged win shipped (f486496b7b). * style(theme): drop no-op keyboard backdrop compositing The will-change/backface-visibility on body::before was added to reduce keyboard-resize choppiness, but review showed it's a no-op: the backdrop resizes every frame so it re-rasterizes regardless of layer promotion, while the hint allocates an always-on compositor layer on every platform. The white-flash fix (WebView background color) is unaffected. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
17 KiB
An advanced todo list app with timeboxing & time tracking capabilities that supports importing tasks from your calendar, Jira, GitHub and others
🌐 Open Web App or 💻 Download
💻 Downloads & Install
For all current downloads, package links, and platform-specific notes:
check the wiki
✔️ Features
- Keep organized and focused! Plan and categorize your tasks using sub-tasks, projects and tags and color code them as needed.
- Use timeboxing and track your time. Create time sheets and work summaries in a breeze to easily export them to your company's time tracking system.
- Helps you to establish healthy & productive habits:
- A break reminder reminds you when it's time to step away.
- The anti-procrastination feature helps you gain perspective when you really need to.
- Need some extra focus? A Pomodoro timer is also always at hand.
- Collect personal metrics to see, which of your work routines need adjustments.
- Integrate with Jira, Trello, GitHub, GitLab, Gitea, OpenProject, Linear, ClickUp and Azure DevOps. Auto import tasks assigned to you, plan the details locally, automatically create work logs, and get notified immediately, when something changes.
- Basic CalDAV integration.
- Back up and synchronize your data across multiple devices with Dropbox and WebDAV support
- Attach context information to tasks and projects. Create notes, attach files or create project-level bookmarks for links, files, and even commands.
- Super Productivity respects your privacy and does NOT collect any data and there are no user accounts or registration. You decide where you store your data!
- It's free and open source and always will be.
And much more!
Note
The web version has some limitations: See the Web App vs Desktop comparison for more details.
📖 Documentation and Guides
Getting Started
- Getting started guide (article)
- Video walkthrough (YouTube)
- Eat the frog prioritizing scheme
Starting Point in Wiki:
First steps •
Reference •
How-To
Productivity Tips:
Keyboard Shortcuts •
Short Syntax
Need Help?
Visit the discussions page
See the bottom of the README for more information on the documentation.
Advanced Topics
Here are some other topics covered in the official wiki:
Development:
Run dev server •
Package the app •
Build for Android •
Run with Docker
Data Management:
User Data •
Issue Providers •
Sync Providers
Customization:
Plugins •
Themes
APIs:
Sync Server •
Plugins •
REST
Community
The development of Super Productivity is driven by a wonderful community of users and contributors. Thank you all so much for your support!
👀 Check out our awesome curated list of community-created resources about Super Productivity
♥️ Contributing
If you want to get involved, please check out the CONTRIBUTING.md
There are several ways to help.
-
Spread the word: More users mean more people testing and contributing to the app which in turn means better stability and possibly more and better features. You can vote for Super Productivity on Slant, Product Hunt, Softpedia or on AlternativeTo, you can tweet about it, share it on LinkedIn, reddit or any of your favorite social media platforms. Every little bit helps!
-
Provide a Pull Request: Here is a list of the most popular community requests and here some info on how to run the development build (wiki). Please make sure that you're following the commit message format and to also include the issue number in your commit message, if you're fixing a particular issue (e.g.:
feat: add nice feature #31). -
Answer questions: You know the answer to another user's problem? Share your knowledge!
-
Provide your opinion: Some community suggestions are controversial. Your input might be helpful and if it is just an up- or down-vote.
-
Provide a more refined UI spec for existing feature requests
-
Make a feature or improvement request: Something can be done better? Something essential missing? Let us know!
-
Translations, Icons, etc.: You don't have to be a programmer to help; learn how to contribute translations!
-
Create custom plugins or custom themes
Special Thanks to our Sponsors!!!
Recently support for Super Productivity has been growing! A big thank you to all our sponsors, especially the ones below!
-
Agentic AI Quality Engineering via:
(If you are, intend to or have been a sponsor and want to be shown here, please let me know!)
Code Signing
Windows binaries are signed. Free code signing is provided by SignPath.io, certificate by SignPath Foundation.
Documentation: Manual versus Automated
There are two wikis: the official one hosted in by GitHub autonomously generated variant using DeepWiki.com. The manually curated version is a more stable and approachable resource designed to help you understand the app from a more human-focused perspective whereas DeepWiki is optimized for explaining the code itself with little regard for context beyond that.
Official Wiki
It is preferable to maintain local documentation rather than rely on an external service. It also preferable that the documentation is updated in tandem with the code changes as demonstrated in this commit.
Changes to files within ./docs/wiki are linted in CI before being automatically
sync'd to the repository's official Wiki hosted by GitHub.
Migrating to Docusaurus is a long-term goal once the content and structure of the wiki has matured and the remaining "legacy docs" have either been reworked or removed. There are some automations in development to help reduce the difference between the published docs and the state of the code while retaining a human-in-the-loop.
DeepWiki.com
If you have very specific questions about how the code works or why a bug might be producing
a particular message it might be useful to
. It can help "cite your sources" when discussing functionality and code that you don't fully
understand as part of feature requests or bug reports.
This automated reference does come with some significant drawbacks:
- Intent: Describes what code does, not why decisions or tradeoffs were made.
- Staleness: Will *always* lag behind the code.
- Code-Focused: Does not provide guides or conceptual explanations.
- Cost: Potential future cost and higher resource usage than static docs.