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

Adaptive mobile Queues next-up flow #1423

New Issue
Closed
opened 2026-08-26 06:56:25 +00:00 by timmy · 0 comments
timmy commented 2026-08-26 06:56:25 +00:00
Owner
Copy Link

Problem

On phones, Queues renders 15 destinations as equally prominent 56px rows. The list alone is at least 840px before gaps, so the product’s existing priority recommendation is hidden in a long scan and empty queues compete with actionable work.

Slice

Turn Queues into an adaptive flow: one truthful Next up action, active non-zero queues in continuation order, always-visible planning destinations, and a collapsed All queues disclosure preserving every destination. Prepare Today remains the guided primary action when it is active/available.

Acceptance

  • At 320x568 the Next up action is visible without horizontal overflow and has a 44px+ target.
  • Delivery, Human Gates, and Today counts render in priority order when active, without duplicate destination identities.
  • Zero-count queues remain available in All queues but do not crowd Active now.
  • Tomorrow and Week Ahead remain visible under Plan & organize.
  • Sync-unavailable queues remain explicitly visible/retryable rather than being treated as zero.
  • Existing queue routing, Prepare Today, detours, close/back, and completion handoff remain intact.
  • Behavioral unit and rendered mobile release tests pass.

Evidence / non-duplication

Current origin/main (1e8d9a2) has a flat list in frontend/index.html and priority logic in frontend/mobile-queue-launcher.js, but only marks a recommendation after queue completion. Searches across all historical issue titles and recent commits found no active-queue grouping, hide-empty, Next up, queue organization, or recommended-queue slice. Existing #743/#755/#897/#1024/#1417 cover truthful counts, priority launch, Prepare Today, and Human Gates—not first-open queue information architecture.

## Problem On phones, Queues renders 15 destinations as equally prominent 56px rows. The list alone is at least 840px before gaps, so the product’s existing priority recommendation is hidden in a long scan and empty queues compete with actionable work. ## Slice Turn Queues into an adaptive flow: one truthful **Next up** action, active non-zero queues in continuation order, always-visible planning destinations, and a collapsed **All queues** disclosure preserving every destination. Prepare Today remains the guided primary action when it is active/available. ## Acceptance - At 320x568 the Next up action is visible without horizontal overflow and has a 44px+ target. - Delivery, Human Gates, and Today counts render in priority order when active, without duplicate destination identities. - Zero-count queues remain available in All queues but do not crowd Active now. - Tomorrow and Week Ahead remain visible under Plan & organize. - Sync-unavailable queues remain explicitly visible/retryable rather than being treated as zero. - Existing queue routing, Prepare Today, detours, close/back, and completion handoff remain intact. - Behavioral unit and rendered mobile release tests pass. ## Evidence / non-duplication Current `origin/main` (`1e8d9a2`) has a flat list in `frontend/index.html` and priority logic in `frontend/mobile-queue-launcher.js`, but only marks a recommendation after queue completion. Searches across all historical issue titles and recent commits found no active-queue grouping, hide-empty, Next up, queue organization, or recommended-queue slice. Existing #743/#755/#897/#1024/#1417 cover truthful counts, priority launch, Prepare Today, and Human Gates—not first-open queue information architecture.
timmy self-assigned this 2026-08-26 06:56:25 +00:00
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
timmy
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#1423
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?