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

Guide new mobile operators to their first task #1140

New Issue
Closed
opened 2026-08-19 17:20:48 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-19 17:20:48 +00:00
Member
Copy Link

User problem

A confirmed mobile operator with no Today plan, eligible work, active preparation, or urgent queue currently has Work jump directly to Find Work. This gives no explanation of the product loop and no equal path to create the first task, while the mobile dock hides the desktop My Work actions.

Evidence

  • frontend/mobile-work-entry.js falls through directly to find when Today and eligible counts are zero.
  • frontend/dashboard.js wires Work to that fallback while Find and New are separate dock actions.
  • Existing issues shipped device readiness, empty-queue recovery, task-first Home, and Prepare Today, but all 572 historical issue titles contain no first-run / first-task activation flow.

Scope

Add a mobile-only, account-bound Start your first task activation sheet reached from Work when the workspace is genuinely empty. It must offer:

  1. Find a task using the existing Find Work flow.
  2. Create a task using existing capture-first issue creation (and remain useful offline through Draft capture).
  3. Optional Make this phone work-ready using existing Device Setup.

Do not show it when Today, eligible work, preparation, recommended urgent queues, or a prior completed activation exists. Persist completion per confirmed account and complete automatically when work appears.

Acceptance tests

  • Work opens the activation flow only for a confirmed empty mobile account.
  • Find/Create/Device Setup hand off to their existing flows; offline state disables Find with truthful guidance but leaves Create enabled.
  • The activation is account-bound, survives reload while incomplete, and clears once Today or eligible work appears.
  • At 390x844 all actions are at least 44px, fit above safe-area insets, and the modal has accessible labelled semantics and predictable focus.
  • Existing Work routing priority and desktop behavior remain unchanged.
## User problem A confirmed mobile operator with no Today plan, eligible work, active preparation, or urgent queue currently has **Work** jump directly to Find Work. This gives no explanation of the product loop and no equal path to create the first task, while the mobile dock hides the desktop My Work actions. ## Evidence - `frontend/mobile-work-entry.js` falls through directly to `find` when Today and eligible counts are zero. - `frontend/dashboard.js` wires Work to that fallback while Find and New are separate dock actions. - Existing issues shipped device readiness, empty-queue recovery, task-first Home, and Prepare Today, but all 572 historical issue titles contain no first-run / first-task activation flow. ## Scope Add a mobile-only, account-bound **Start your first task** activation sheet reached from Work when the workspace is genuinely empty. It must offer: 1. **Find a task** using the existing Find Work flow. 2. **Create a task** using existing capture-first issue creation (and remain useful offline through Draft capture). 3. Optional **Make this phone work-ready** using existing Device Setup. Do not show it when Today, eligible work, preparation, recommended urgent queues, or a prior completed activation exists. Persist completion per confirmed account and complete automatically when work appears. ## Acceptance tests - Work opens the activation flow only for a confirmed empty mobile account. - Find/Create/Device Setup hand off to their existing flows; offline state disables Find with truthful guidance but leaves Create enabled. - The activation is account-bound, survives reload while incomplete, and clears once Today or eligible work appears. - At 390x844 all actions are at least 44px, fit above safe-area insets, and the modal has accessible labelled semantics and predictable focus. - Existing Work routing priority and desktop behavior remain unchanged.
timmy was assigned by rockachopa 2026-08-19 17:20:48 +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#1140
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?