stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Combine Following changes with Updates in the app badge #1324

New Issue
Closed
opened 2026-08-23 22:21:02 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-23 22:21:02 +00:00
Member
Copy Link

Problem

The installed mobile app badge only reflects unread Updates. Following push payloads already include an authoritative following_count, but the service worker displays a transient notification without preserving that review attention on the app icon. Operators can therefore miss watched work after the notification disappears.

Scope

Create one privacy-safe review-attention badge equal to unread Updates plus unseen Following changes. Keep channel counts independent so clearing either flow cannot erase the other. Reconcile the same model in the foreground and service worker, update opt-in copy, and validate the packaged phone flow.

Acceptance criteria

  • 3 unread Updates plus 2 unseen Following changes renders badge 5.
  • Reviewing Following to zero leaves unread Updates represented; clearing Updates leaves Following represented.
  • Valid background pushes update only their own channel and preserve the other channel.
  • Invalid counts cannot alter badge state. Opt-out/private-data purge clears retained badge state.
  • Setting copy describes review attention and remains usable without horizontal overflow at phone widths.
  • Focused unit/contract tests, full suite, and packaged mobile journey pass.

Evidence / non-duplication

Current frontend/dashboard.js sends only Updates totals to mobileAppBadge.reconcile; frontend/service-worker.js receives following_count but does not reconcile it. Historical #1278/#1281 cover Updates-only badging; Following #1293-#1322 does not integrate the app badge. No open issue or PR covers combined review-attention badging.

## Problem The installed mobile app badge only reflects unread Updates. Following push payloads already include an authoritative `following_count`, but the service worker displays a transient notification without preserving that review attention on the app icon. Operators can therefore miss watched work after the notification disappears. ## Scope Create one privacy-safe review-attention badge equal to unread Updates plus unseen Following changes. Keep channel counts independent so clearing either flow cannot erase the other. Reconcile the same model in the foreground and service worker, update opt-in copy, and validate the packaged phone flow. ## Acceptance criteria - 3 unread Updates plus 2 unseen Following changes renders badge 5. - Reviewing Following to zero leaves unread Updates represented; clearing Updates leaves Following represented. - Valid background pushes update only their own channel and preserve the other channel. - Invalid counts cannot alter badge state. Opt-out/private-data purge clears retained badge state. - Setting copy describes review attention and remains usable without horizontal overflow at phone widths. - Focused unit/contract tests, full suite, and packaged mobile journey pass. ## Evidence / non-duplication Current `frontend/dashboard.js` sends only Updates totals to `mobileAppBadge.reconcile`; `frontend/service-worker.js` receives `following_count` but does not reconcile it. Historical #1278/#1281 cover Updates-only badging; Following #1293-#1322 does not integrate the app badge. No open issue or PR covers combined review-attention badging.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#1324
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?