Super Productivity, an advanced to-do list application designed to integrate timeboxing and time tracking, has been actively developed with a focus on enhancing user experience and expanding integration capabilities. Recent activities highlight ongoing issues with synchronization and task management stability across platforms.
Recent issues and pull requests (PRs) indicate persistent challenges with task visibility and synchronization, particularly across Windows and Ubuntu systems. Critical bugs such as app crashes when minimizing (#3428) and synchronization errors (#3377) suggest areas needing immediate attention. The development team, led by Johannes Millan, has been actively addressing these concerns through numerous commits focused on bug fixes and feature enhancements.
Timespan | Opened | Closed | Comments | Labeled | Milestones |
---|---|---|---|---|---|
7 Days | 25 | 11 | 80 | 5 | 1 |
30 Days | 55 | 57 | 173 | 11 | 1 |
90 Days | 130 | 99 | 508 | 32 | 1 |
1 Year | 346 | 199 | 1482 | 68 | 1 |
All Time | 1852 | 1663 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
Developer | Avatar | Branches | PRs | Commits | Files | Changes |
---|---|---|---|---|---|---|
Johannes Millan | 2 | 0/0/0 | 194 | 307 | 28651 | |
FabioL | 1 | 1/1/0 | 2 | 1 | 976 | |
Ramon | 1 | 1/1/0 | 1 | 19 | 562 | |
Sagy Assor | 1 | 1/1/0 | 1 | 21 | 473 | |
dependabot[bot] | 1 | 6/3/6 | 3 | 3 | 163 | |
Jiongxuan Zhang | 1 | 2/1/1 | 2 | 2 | 151 | |
Roman | 1 | 1/1/0 | 2 | 28 | 42 | |
Instinct | 1 | 2/2/0 | 4 | 2 | 12 | |
Gerrit | 1 | 1/1/0 | 1 | 1 | 4 | |
José Miguel Sarasola | 1 | 1/1/0 | 1 | 1 | 2 | |
Duncan Lock (dflock) | 0 | 1/1/0 | 0 | 0 | 0 | |
None (MiragonMx) | 0 | 2/1/0 | 0 | 0 | 0 | |
None (ZaphireLiu) | 0 | 1/0/1 | 0 | 0 | 0 | |
Dmitriy Shushlebin | 0 | 1/1/0 | 0 | 0 | 0 | |
Carsten (BanditsBacon) | 0 | 1/1/0 | 0 | 0 | 0 | |
Pawan Udassi (Udassi-Pawan) | 0 | 0/0/1 | 0 | 0 | 0 | |
Shaik Shafi Ahmed (shafiahmed12) | 0 | 1/0/0 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The recent activity on the Super Productivity GitHub repository indicates a high level of engagement, with 189 open issues, including a mix of bugs, enhancements, and feature requests. Notably, there are recurring themes surrounding task management features, synchronization issues, and user interface improvements. Several users have reported critical bugs that affect functionality, particularly around task visibility and synchronization across platforms.
A significant number of issues (e.g., #3427, #3423) relate to the application's behavior when minimizing or closing tasks, indicating potential instability in the user experience. Additionally, the presence of multiple reports regarding synchronization errors (e.g., #3377) suggests that users are experiencing challenges when using the app across different devices or platforms.
Issue #3428: App crashes when minimizing to tray on Windows 11
Issue #3427: On Ubuntu 24.04.1 LTS, SuperProductivity doesn't get minimized to tray anymore
Issue #3424: TypeError: c.$$ is undefined
Issue #3423: Crash when minimized
Issue #3422: Cannot reorder task in TODAY
Issue #3409: Today's Task in Timeline Showed up in Tomorrow
Issue #3419: UI is not optimized for tablets
Issue #3405: TypeError: Cannot read properties of undefined (reading 'entities')
Issue #3396: Auto stop timer on lock screen activity
Issue #3384: Flow Time technique aka Flowmodoro
Several themes emerge from the recent issues:
Overall, while the application has a strong user base and active development community, there are pressing concerns that need addressing to enhance stability and usability across platforms.
The analysis covers a total of 8 open pull requests (PRs) and a significant number of closed PRs for the Super Productivity project. The open PRs focus on new features, dependency updates, and improvements to existing functionality, while the closed PRs highlight ongoing community engagement and enhancements in translations, bug fixes, and feature requests.
PR #3412: feat: Add Today Remaining in the projects view
PR #3320: build(deps): bump easingthemes/ssh-deploy from 5.0.3 to 5.1.1
PR #3348: feat(integration): import github labels as tags
PR #3048: [WP] Added some more translation strings for PL
PR #3408: some translate RU
PR #3406: Update translations for Portuguese
PR #3401: feat(i18n): translate JSON content into Simplified and Traditional Chinese
PR #2695: fix: create repeat tasks if missed in the days before
PR #2659: feat: add repeat subtasks for repeating tasks
PR #2595: WIP: Change save tracked time approach. Issue #2355
PR #2388: feat: Integrate with Azure DevOps
PR #3400: feat(i18n): translate JSON content into Simplified Chinese
The pull requests reflect an active development environment with a strong emphasis on improving user experience through feature enhancements and bug fixes. The recent PRs primarily focus on integrating new functionalities such as task filtering based on time (e.g., PR #3412) and improving integration with external services like GitHub (e.g., PR #3348). This indicates a commitment to enhancing usability and functionality in response to user needs.
A notable trend is the ongoing effort to improve localization and internationalization, as seen in multiple PRs aimed at adding or refining translations across various languages (e.g., Polish, Portuguese, Chinese). This is crucial for expanding the application's reach and ensuring accessibility for non-English speaking users.
Dependency management is also a recurring theme, with several PRs dedicated to updating libraries (e.g., PR #3320, PR #3389). This suggests that the maintainers are proactive about security and performance, which is vital for maintaining application integrity over time.
However, there are several older PRs that remain unresolved or have been closed without merging, indicating potential issues with communication or alignment on feature implementations (e.g., PR #2695, PR #2659). These stalled contributions could reflect either a lack of resources or differing priorities among contributors and maintainers.
Moreover, discussions within the comments of various PRs reveal an engaged community where feedback is actively sought and provided. However, there are instances where contributors express confusion or seek clarification on implementation details (e.g., PR #3348), highlighting the need for clearer guidelines or documentation regarding contribution processes.
In summary, while the project demonstrates robust activity and community involvement, attention should be given to addressing stalled contributions and enhancing communication around feature development to ensure sustained momentum in future releases.