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

Guide mobile operators through device readiness setup #555

New Issue
Closed
opened 2026-08-11 08:20:27 +00:00 by timmy · 0 comments
timmy commented 2026-08-11 08:20:27 +00:00
Owner
Copy Link

Problem

On mobile, installation, offline private-work saving, and update notifications already exist, but all are buried inside the collapsed Queue & settings disclosure. Operators cannot discover or complete a coherent phone-readiness flow before an outage or missed update.

Vertical slice

Add a resumable, phone-first Device setup sheet that orchestrates the existing install, offline, and Web Push controls without duplicating their storage or security behavior. It must re-evaluate real capability/state on every open, require explicit taps for permission/install prompts, truthfully mark unsupported steps, and remain available from the app menu after dismissal.

Acceptance

  • At 390x844 and 320x568 the sheet has no horizontal overflow, respects safe areas, and provides 44px controls.
  • Opening setup never triggers install or notification permission automatically.
  • Install, offline saving, and notification actions delegate to the existing controls and reflect their current state.
  • Unsupported install/push capabilities are described truthfully and do not block the readiness summary.
  • Setup can be dismissed, reopened, and resumes by re-reading actual state rather than stale completion flags.
  • Back/Escape closes the sheet and restores focus to its launcher.
  • The new controller is included in the deterministic frontend bundle and service-worker shell.
  • Focused behavioral tests and the full suite pass.

Non-duplication

Current open issues #1-#5 and #11 are assigned to other humans and concern dashboard design/widgets/latency, not mobile setup. Historical issue/commit searches show separate install (#291/#292), offline work (#226-#230, #349/#350), and Web Push (#549-#554) delivery, but no unified device-readiness flow.

## Problem On mobile, installation, offline private-work saving, and update notifications already exist, but all are buried inside the collapsed **Queue & settings** disclosure. Operators cannot discover or complete a coherent phone-readiness flow before an outage or missed update. ## Vertical slice Add a resumable, phone-first **Device setup** sheet that orchestrates the existing install, offline, and Web Push controls without duplicating their storage or security behavior. It must re-evaluate real capability/state on every open, require explicit taps for permission/install prompts, truthfully mark unsupported steps, and remain available from the app menu after dismissal. ## Acceptance - At 390x844 and 320x568 the sheet has no horizontal overflow, respects safe areas, and provides 44px controls. - Opening setup never triggers install or notification permission automatically. - Install, offline saving, and notification actions delegate to the existing controls and reflect their current state. - Unsupported install/push capabilities are described truthfully and do not block the readiness summary. - Setup can be dismissed, reopened, and resumes by re-reading actual state rather than stale completion flags. - Back/Escape closes the sheet and restores focus to its launcher. - The new controller is included in the deterministic frontend bundle and service-worker shell. - Focused behavioral tests and the full suite pass. ## Non-duplication Current open issues #1-#5 and #11 are assigned to other humans and concern dashboard design/widgets/latency, not mobile setup. Historical issue/commit searches show separate install (#291/#292), offline work (#226-#230, #349/#350), and Web Push (#549-#554) delivery, but no unified device-readiness flow.
timmy self-assigned this 2026-08-11 08:20:27 +00:00
timmy closed this issue 2026-08-11 08:35:09 +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#555
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?