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

Demand-load Today and Planning workspace on mobile #1468

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

Problem

The progressive mobile My Work path is functional after work-core, but workspace-bootstrap.js immediately downloads Today and Planning anyway. On current main those optional chunks are about 225 KiB gzip—over 80% of workspace startup JavaScript—even when the operator only opens assigned work.

User outcome

A cold mobile My Work visit remains actionable without requesting Today or Planning. The first action that needs the full workspace hydrates it once, preserves the action, and offers in-place retry without breaking Work/Queues.

Acceptance

  • Initial My Work requests work-core only; Today and Planning remain at 0 B before a dependent action.
  • Initial core + work-core JavaScript is at most 60 KiB gzip.
  • A dependent mobile action demand-loads Today and Planning exactly once and resumes that action.
  • A Today deep link hydrates immediately.
  • Optional load failure leaves progressive Work/Queues actionable and retry completes without reload or duplicate listeners.
  • Behavioral unit tests, packaged mobile browser coverage, and full suite pass.

No open/closed issue title or recent main commit describes demand-driven Today/Planning hydration; prior progressive-work issues made My Work usable early but left these downloads eager.

## Problem The progressive mobile My Work path is functional after `work-core`, but `workspace-bootstrap.js` immediately downloads Today and Planning anyway. On current main those optional chunks are about 225 KiB gzip—over 80% of workspace startup JavaScript—even when the operator only opens assigned work. ## User outcome A cold mobile My Work visit remains actionable without requesting Today or Planning. The first action that needs the full workspace hydrates it once, preserves the action, and offers in-place retry without breaking Work/Queues. ## Acceptance - [ ] Initial My Work requests `work-core` only; Today and Planning remain at 0 B before a dependent action. - [ ] Initial core + work-core JavaScript is at most 60 KiB gzip. - [ ] A dependent mobile action demand-loads Today and Planning exactly once and resumes that action. - [ ] A Today deep link hydrates immediately. - [ ] Optional load failure leaves progressive Work/Queues actionable and retry completes without reload or duplicate listeners. - [ ] Behavioral unit tests, packaged mobile browser coverage, and full suite pass. No open/closed issue title or recent main commit describes demand-driven Today/Planning hydration; prior progressive-work issues made My Work usable early but left these downloads eager.
timmy self-assigned this 2026-08-27 11:23:00 +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#1468
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?