Show total notification count badge on app Folders
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
This issue has not been assessed yet.
Description
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
Prerequisites
Feature request
Description
When multiple apps are grouped into a Folder, the total number of unread notifications from all contained apps should be shown as a badge in the Folder’s top-right corner.
This behavior is standard in the default Android launcher and is important for functional parity. It allows users to see pending notifications without having to open the Folder.
Expected behavior:
- The Folder icon displays a numeric badge representing the sum of all notification counts from the apps inside it.
- The badge updates dynamically as notifications are received or cleared.
Screenshot from Android's default Home launcher:
Why this is needed
Without this aggregated badge, users lose visibility into notifications for apps placed inside Folders. Implementing this feature will help Fossify Launcher fully replace the default Android launcher experience.
Why do you want this feature?
This standard feature is implemented in Android's default launcher. It must be implemented in Fossify Launcher to fully replace it.
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 703
- Forks
- 85
- Avg merge
- 4d 39m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FossifyOrg/Launcher
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FossifyOrg/Launcher#453 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FossifyOrg/Launcher#447 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FossifyOrg/Launcher#446 ·
Maintainers usually reply within 3 days
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 40/100
FossifyOrg/Launcher#461 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Launcher#456 ·
Maintainers usually reply within 3 days
All issues in FossifyOrg/Launcher
Similar issues
-
Feature:Resolution
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
intellij-elixir/intellij-elixir#4396 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
partiql/partiql-lang-kotlin#1972 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
navikt/soknadsarkiverer#293 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
FoedusProgramme/Gramophone#1048 ·
-
Cambio de urlOpenBug Domain changed
Difficulty 1/5 Under an hour Newbie friendliness 72/100
keiyoushi/extensions-source#19783 ·
Maintainers usually reply within 1 day