Dimillian / Dimillian/IceCubesApp
Feature request: better clustering of notifications
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 7.1k
- Forks
- 720
- PR merge metrics
- No merged PRs in 30d
Description
I love the clustering on the activity tab. But take a look at the screenshot:
one notification, then two clustered, then two separate ones, again. This is confusing in terms of UX.
Expected behavior: at least consequent notifications for the same posting should always be clustered. Even better: only one cluster per Posting on the hole list - so with every new one, the old cluster moves to the top and gets a +1 - this would result in a very clean layout.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The issue identifies the activity tab and includes a screenshot, but names no source file or test. Start by tracing notification clustering in the SwiftUI iOS client, then establish which expected behavior is in scope. Done means same-post notifications are clustered consistently according to the selected behavior and the layout matches the intended UX.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100